remove-old-skills-from-workflow
Skill283 starsChanged 10 months agoMITView on GitHub
Guide for removing skills from an existing workflow and updating all related documentation. Use when user wants to remove skills from a workflow (e.g., "remove skill", "delete skill", "移除技能", "删除技能").
- Deletes or force-pushes
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Search for the skill name across the workflow to understand its usage:
- Distinctive: line 29
Remove the skill directory from the workflow:
- Very specific: line 37
Remove the skill entry from /path/to/workflow/.claude/skill-source.json
- Distinctive: line 41
After removing a skill, you MUST update these files:
- Distinctive: line 88
Always search for skill references before removal to understand impact
- Very specific: line 90
Leave references/skill-sources.md unchanged (it documents ecosystem skills, not workflow-specific installations)
- Distinctive: line 91
If the skill is referenced in example workflows, either remove the example or update it to use alternative skills
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 tableImportant 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
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-new-skills-to-workflowSkill
- legacy-to-ai-readySkill
- resource-scoutSkill
- skill-creatorSkill
- skill-downloaderSkill
- workflow-creatorSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

