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", "移除技能", "删除技能").
npx skills add https://github.com/nicepkg/ai-workflow --skill remove-old-skills-from-workflow
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)Complete development kit for Microsoft 365 Copilot declarative agents with three comprehensive workflows (basic, advanced, validation), TypeSpec support, and Microsoft 365 Agents Toolkit integration
Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and release gates—not for clinical decision-making.
> provider/change budget/修改卖家/修改预算/draft/草稿/我的任务/my tasks/what am I working on/关闭/取消任务/决策列表/decision list/指定服务商/browse (sender.role = COUNTERPARTY, not you); (3) literal "Read the okx-ai skill" (or legacy "Read the okx-agent-task skill") in the envelope.
Automate payer review of prior authorization (PA) requests. This skill should be used when users say "Review this PA request", "Process prior authorization for [procedure]", "Assess medical necessity", "Generate PA decision", or when processing clinical documentation for coverage policy validation and authorization decisions.
Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration.
Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability.
Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order.
Structured persuasion for tech leads, PMs, and founders—not activity logs. Five scenarios (kickoff, status update, wrap-up, investor pitch, solution selling) on one 5-part framework (Hook→Context→Proposal→Evidence→Ask). AI prompts for missing materials and audience context; pre-submit checklist. Claude Code plugin; Cursor, Codex, and chat via prompts.
Take nicepkg/remove-old-skills-from-workflow from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.