remove-old-skills-from-workflow▌
nicepkg/ai-workflow · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Guide for removing skills from an existing workflow and updating all related documentation.
Remove Skills from Workflow
Guide for removing skills from an existing workflow and updating all related documentation.
When to Use
- User wants to remove a skill from a workflow
- User says "remove skill", "delete skill", "移除技能", "删除技能"
- Cleaning up unused or deprecated skills from a workflow
Removal Workflow
Step 1: Identify the Skill
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/
Step 2: Delete Skill Folder
Remove the skill directory from the workflow:
rm -rf /path/to/workflow/.claude/skills/skill-name/
Step 3: Update skill-source.json (if exists)
Remove the skill entry from /path/to/workflow/.claude/skill-source.json
Step 4: Update All Related Documentation
After removing a skill, you MUST update these files:
Files to Update (7 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) |
Documentation Update Checklist
For each documentation file, update:
- Skill count: Decrease the total skill count (e.g., "20 skills" → "19 skills")
- Skill tables: Remove the skill row from any skill listing tables
- Pipeline/stages: Remove skill references from pipeline diagrams or stage descriptions
- Skill combinations: Remove any skill chains that include the removed skill
- Example workflows: Remove or update examples that reference the skill
Example
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
Important Notes
- Always search for skill references before removal to understand impact
- The root READMEs only need skill count updates in the workflow table
- Leave
references/skill-sources.mdunchanged (it documents ecosystem skills, not workflow-specific installations) - If the skill is referenced in example workflows, either remove the example or update it to use alternative skills
How to use remove-old-skills-from-workflow on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add remove-old-skills-from-workflow
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches remove-old-skills-from-workflow from GitHub repository nicepkg/ai-workflow and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate remove-old-skills-from-workflow. Access the skill through slash commands (e.g., /remove-old-skills-from-workflow) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★72 reviews- ★★★★★Shikha Mishra· Dec 28, 2024
Useful defaults in remove-old-skills-from-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Dev Abbas· Dec 28, 2024
I recommend remove-old-skills-from-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Isabella Agarwal· Dec 24, 2024
Solid pick for teams standardizing on skills: remove-old-skills-from-workflow is focused, and the summary matches what you get after install.
- ★★★★★Hana Desai· Dec 16, 2024
We added remove-old-skills-from-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Jin Gill· Nov 23, 2024
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.
- ★★★★★Omar Taylor· Nov 15, 2024
remove-old-skills-from-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Hana Khanna· Nov 7, 2024
remove-old-skills-from-workflow reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Zara Mehta· Oct 26, 2024
Registry listing for remove-old-skills-from-workflow matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★James Patel· Oct 14, 2024
remove-old-skills-from-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Jin Haddad· Oct 6, 2024
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