Guide for removing skills from an existing workflow and updating all related documentation.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionremove-old-skills-from-workflowExecute the skills CLI command in your project's root directory to begin installation:
Fetches remove-old-skills-from-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 remove-old-skills-from-workflow. Access via /remove-old-skills-from-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
151
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
151
stars
Guide for removing skills from an existing workflow and updating all related documentation.
Search for the skill name across the workflow to understand its usage:
# Find all references to the skill
grep -r "skill-name" /path/to/workflow/
Remove the skill directory from the workflow:
rm -rf /path/to/workflow/.claude/skills/skill-name/
Remove the skill entry from /path/to/workflow/.claude/skill-source.json
After removing a skill, you MUST update these files:
| File | What to Update |
|---|---|
workflows/<workflow-name>/README.md |
Skill count, skill table, pipeline stages, skill combinations |
workflows/<workflow-name>/README_cn.md |
Same as above (Chinese version) |
workflows/<workflow-name>/AGENTS.md |
Available skills list, recommended sequences |
website/content/en/workflows/<workflow>.mdx |
Skill count, skill table, pipeline, skill combinations |
website/content/zh/workflows/<workflow>.mdx |
Same as above (Chinese version) |
README.md (root) |
Workflow table skill count |
README_cn.md (root) |
Workflow table skill count (Chinese version) |
For each documentation file, update:
Removing ppt-creator skill from talk-to-slidev-workflow:
# 1. Search for references
grep -r "ppt-creator" workflows/talk-to-slidev-workflow/
# 2. Delete skill folder
rm -rf workflows/talk-to-slidev-workflow/.claude/skills/ppt-creator/
# 3. Update skill-source.json
# Remove the ppt-creator entry
# 4. Update documentation files
# - Update skill count from 20 to 19
# - Remove ppt-creator from skill tables
# - Remove from pipeline Stage 6
# - Remove from skill combinations table
references/skill-sources.md unchanged (it documents ecosystem skills, not workflow-specific installations)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
Useful defaults in remove-old-skills-from-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend remove-old-skills-from-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: remove-old-skills-from-workflow is focused, and the summary matches what you get after install.
We added remove-old-skills-from-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: remove-old-skills-from-workflow is the kind of skill you can hand to a new teammate without a long onboarding doc.
remove-old-skills-from-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
remove-old-skills-from-workflow reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for remove-old-skills-from-workflow matched our evaluation — installs cleanly and behaves as described in the markdown.
remove-old-skills-from-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: remove-old-skills-from-workflow is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 72