Add skills from GitHub to an existing workflow and update all related documentation.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionadd-new-skills-to-workflowExecute the skills CLI command in your project's root directory to begin installation:
Fetches add-new-skills-to-workflow from nicepkg/ai-workflow and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate add-new-skills-to-workflow. Access via /add-new-skills-to-workflow in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
150
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
150
stars
Add skills from GitHub to an existing workflow and update all related documentation.
Use skill-downloader to download skills from GitHub:
python .claude/skills/skill-downloader/scripts/download_from_github.py <repo-url> <skill-path> --output <workflow-path>/.claude/skills/
Parse GitHub URL:
https://github.com/user/repo/blob/main/path/to/skill → repo: https://github.com/user/repo, skill-path: path/to/skillhttps://github.com/user/repo/tree/main/.claude/skills/my-skill → repo: https://github.com/user/repo, skill-path: .claude/skills/my-skillExample:
# For URL: https://github.com/XIYO/zheon/blob/main/.claude/skills/slidev
python .claude/skills/skill-downloader/scripts/download_from_github.py https://github.com/XIYO/zheon .claude/skills/slidev --output ./workflows/talk-to-slidev-workflow/.claude/skills/
# Use --force to overwrite existing
python .claude/skills/skill-downloader/scripts/download_from_github.py <repo> <path> --output <target> --force
Read the downloaded SKILL.md to understand:
Add the new skill entry to workflows/<name>/.claude/skill-source.json:
{
"skill-name": {
"source": "https://github.com/user/repo",
"path": "path/to/skill"
}
}
Update these files (all that exist for the workflow):
| File | Updates Required |
|---|---|
workflows/<name>/.claude/skill-source.json |
Add new skill source entry |
workflows/<name>/README.md |
Skill count, skill table, pipeline |
workflows/<name>/README_cn.md |
Same as above (Chinese) |
workflows/<name>/AGENTS.md |
Available skills list, recommended sequences |
website/content/en/workflows/<name>.mdx |
Skill count, skill table, pipeline |
website/content/zh/workflows/<name>.mdx |
Same as above (Chinese) |
README.md (root) |
Skill count in workflow table |
README_cn.md (root) |
Same as above (Chinese) |
Skill Count: Update total count (e.g., "18 skills" → "20 skills")
Skill Table: Add new skill row in appropriate category
| `skill-name` | Brief description of what it does |
Pipeline: Add skill to relevant stage if applicable
Stage X: Category
├── existing-skill → Description
└── new-skill → Description
AGENTS.md: Add to available skills and update recommended sequences
Root README: Update skill count in workflow overview table
Given: Add slidev and slidev-presentations skills
Step 1: Download
python .claude/skills/skill-downloader/scripts/download_from_github.py https://github.com/XIYO/zheon .claude/skills/slidev --output ./workflows/talk-to-slidev-workflow/.claude/skills/
python .claude/skills/skill-downloader/scripts/download_from_github.py https://github.com/clearfunction/cf-devtools skills/slidev-presentations --output ./workflows/talk-to-slidev-workflow/.claude/skills/
Step 2: Read downloaded skills to understand their purpose
Step 3: Update skill-source.json with new skill entries
Step 4: Update all 8 files:
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
JuliusBrussee/caveman
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
I recommend add-new-skills-to-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
add-new-skills-to-workflow reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: add-new-skills-to-workflow is the kind of skill you can hand to a new teammate without a long onboarding doc.
add-new-skills-to-workflow has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for add-new-skills-to-workflow matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: add-new-skills-to-workflow is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for add-new-skills-to-workflow matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in add-new-skills-to-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added add-new-skills-to-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: add-new-skills-to-workflow is focused, and the summary matches what you get after install.
showing 1-10 of 35