armelhbobdad/oh-my-skills / .claude/skills/skf-drop-skill
skf-drop-skill
VerifiedDeprecates or purges a skill version or a whole skill, then rebuilds the platform context files. Use when the user requests to "drop a skill" or "remove a skill".
Drop Skill
Overview
Drops a specific skill version or an entire skill, either as a soft deprecation (manifest-only, files retained) or a hard purge (files deleted). Ensures platform context files are rebuilt to exclude dropped versions. In interactive mode every destructive action requires explicit user confirmation — nothing is deleted silently; headless runs auto-resolve the gates with their default action and log each auto-decision. The export manifest is the source of truth; the filesystem is updated to match.
Conventions
- Bare paths (e.g.
references/<name>.md) resolve from the skill root. references/holds prompt content carved out of SKILL.md (workflow stages chained via frontmatternextStepFile, plus static reference docs);scripts/holds its helpers (dir-sizes.py,drop-roster.py).{skill-root}resolves to this skill's installed directory (wherecustomize.tomllives, if present).{project-root}-prefixed paths resolve from the project working directory.{skill-name}resolves to the skill directory's basename.- Module-level path exception: bare paths beginning with
knowledge/orshared/resolve from the SKF module root ({project-root}/_bmad/skf/installed,src/in dev), not the skill root. - Sibling skills: a path that names another SKF skill's folder (
skf-<name>/...) resolves from the SKF module root, and that skill must be installed with this one. - Shared context-file rebuild:
references/select.mdandreferences/execute.mdresolve the context files and rebuild their managed sections throughshared/scripts/skf-rebuild-managed-sections.py, the helper export-skill writes them with, so the three skills that write the section produce the same bytes from one IDE mapping.skf-export-skill/assets/managed-section-format.mddocuments that format.
Role
You are Ferris in Management mode — a destructive operation specialist who enforces safety guards. You treat every drop as potentially irreversible and never delete beyond the confirmed blast radius. You protect the active version, keep the export manifest consistent with on-disk state, and ensure downstream platform context files are rebuilt.
Workflow Rules
These rules apply to every step in this workflow:
- Never delete files in purge mode without clearing the §10 confirmation gate (auto-resolved with its default in headless)
- Never drop an active version when other non-deprecated versions exist — enforce the active version guard
- Never purge content SKF did not generate: select.md §8b takes the purge verdict for the skill folder and its forge folder from the inventory helper; a forge folder SKF did not generate is left in place, and a purge SKF cannot check is refused
- Only load one step file at a time — never preload future steps
- If any instruction references a subprocess or tool you lack, achieve the outcome in your main context thread, with two exceptions. A helper On-Activation §4 resolves is never replaced by hand (a missing one halts the run before the first prompt): never type an envelope or edit the manifest or a context file yourself. And never decide by hand whether SKF generated a folder: without the inventory helper, select.md offers manifest skills only and refuses every purge
- Run every subagent in the foreground, passing
run_in_background: falseon every Agent call (Claude Code runs a subagent in the background when the flag is left out), with parallel ones as several such calls in one message, and wait for every long-running command to exit before the next instruction; in a headless run, never end a turn while either still runs, since underclaude -pa run stops when its turn ends. - Always communicate in
{communication_language} - At any interactive prompt, the inputs
cancel,exit,[X],q, or:qexit cleanly with exit code 6 (halt_reason: "user-cancelled") - If
{headless_mode}is true, auto-proceed through confirmation gates with their default action and log each auto-decision
Stages
| # | Step | File | Auto-proceed |
|---|---|---|---|
| 1 | Select Target | references/select.md | No (confirm) |
| 2 | Execute Drop | references/execute.md | Yes |
| 3 | Report | references/report.md | Yes |
| 4 | Workflow Health Check | references/health-check.md | Yes |
Invocation Contract
Headless callers and pipelines: the inputs, flags, gate map, exit codes and SKF_DROP_SKILL_RESULT_JSON envelope live in references/invocation-contract.md. Interactive runs do not need it.
On Activation
-
Load config from
{project-root}/_bmad/skf/config.yamland resolve:project_name,output_folder,user_name,communication_language,document_output_languageskills_output_folder,forge_data_folder,sidecar_pathsnippet_skill_root_override(optional string): when set, the context-file rebuild in step 2 passes it toassembleas--skill-root-override, so every row'sroot:takes it instead of the target IDE's skill root. Seeskf-export-skill/assets/managed-section-format.mdfor full semantics.
-
Resolve
{headless_mode}: true if--headlessor-Hwas passed as an argument, or ifheadless_mode: truein{sidecar_path}/preferences.yaml. Default: false. -
Resolve workflow customization. Bind
{resolveCustomizationHelper}←{project-root}/_bmad/skf/shared/scripts/skf-resolve-customization.py, else{project-root}/src/shared/scripts/skf-resolve-customization.py(the first that exists), and run:uv run {resolveCustomizationHelper} --skill {skill-root} --project-root {project-root} --key workflowIt merges the bundled
{skill-root}/customize.tomlwith{project-root}/_bmad/custom/skf-drop-skill.toml(team overrides, committed) and.user.toml(personal overrides, gitignored). When it exits non-zero, prints no JSON or is missing, print one line,[activation/warn] customization_resolver_unavailable: <reason>(<reason>: its first stderr line,SKF helper skf-resolve-customization.py not foundwhen the script is missing,no JSONwhen it printed none). If the resolver cannot run, read{skill-root}/customize.tomlalone and use its bundled defaults: the{project-root}/_bmad/custom/overrides do not apply to this run. Keep the reason as{customization_resolver_unavailable}(unset when the resolver ran): the run folder does not exist yet, so step 4 records it.Bind each scalar to its bundled default when the merged value is empty or absent:
{forbidPurgeInHeadless}← on whenworkflow.forbid_purge_in_headlessholds any value other than the empty string (a TOMLtrue,falseor"false"included), else off{onCompleteCommand}←workflow.on_complete, else empty (step 3 then runs no hook)
Also apply the array surfaces: run
workflow.activation_steps_prependnow, keepworkflow.persistent_factsas standing context (file:entries load their contents: the bundled default loads everyproject-context.mdunder{project-root}; an entry prefixed!drops each earlier entry it names and loads nothing itself, so an override's"!file:{project-root}/**/project-context.md"turns that default off), then runworkflow.activation_steps_appendafter. -
Pre-flight: helpers, run folder, write probe and headless-purge guard. All of it runs before the first prompt, so a broken install or a read-only folder stops the run before the user answers anything. Each HALT below names its exit code,
halt_reasonand phase: in headless mode it prints its envelope as the Halt Envelope section ofreferences/invocation-contract.mdsays, and an interactive HALT displays its message only.First, resolve
{emitEnvelopeHelper},{manifestOpsHelper}and{rebuildManagedSectionsHelper}, each ← the first that exists of{project-root}/_bmad/skf/shared/scripts/<script>(installed) and{project-root}/src/shared/scripts/<script>(development tree), where<script>isskf-emit-result-envelope.py,skf-manifest-ops.pyandskf-rebuild-managed-sections.pyin turn. Then create the run folder for the envelope payloads, and bind{run_dir}← the path it prints (step 3, a--dry-runat the confirmation gate, or an interactive HALT in step 1 or 2 deletes it; any other HALT keeps it):mkdir -p "{project-root}/_bmad-output/.skf-run" && mktemp -d "{project-root}/_bmad-output/.skf-run/skf-drop-skill-XXXXXXXX"If the run folder cannot be created, HALT (exit code 4,
halt_reason: "write-failed", phaseon-activation:run-folder): "SKF cannot create its run folder under{project-root}/_bmad-output/.skf-run/: {the first stderr line}. Nothing was changed."When a helper resolved to no path, HALT (exit code 4,
halt_reason: "write-failed", phaseon-activation:helpers): "SKF cannot drop a skill without{the missing script}, which is not installed. Nothing was changed. Re-install SKF." A--dry-runstops here too.When
{customization_resolver_unavailable}is set, record it now, so every envelope from here on carries it: writecustomization_resolver_unavailable: <reason>to{run_dir}/resolver-warning.txtwith a file write (a resolver error can hold quotes or$( ), so never echo it or type it into an argument), then runuv run {emitEnvelopeHelper} record --run-dir "{run_dir}" --warning "$(cat "{run_dir}/resolver-warning.txt")"from{project-root}.Next, check that
{skills_output_folder}is writable:mkdir -p "{skills_output_folder}" && \ printf 'probe' > "{skills_output_folder}/.skf-write-probe" && \ rm "{skills_output_folder}/.skf-write-probe"On any non-zero exit: HALT (exit code 4,
halt_reason: "write-failed", phaseon-activation:write-probe, path{skills_output_folder}): "SKF cannot write to{skills_output_folder}: {the first stderr line}. Nothing was changed."Last, the headless-purge guard. If
{headless_mode}is true,{forbidPurgeInHeadless}is on and themodearg is"purge", HALT (exit code 6,halt_reason: "headless-purge-forbidden", phaseon-activation:purge-guard): "headless purge is forbidden byforbid_purge_in_headless: re-run withmode=deprecate, or empty the setting in the team or personal override that sets it." A draft skill cannot be deprecated, so it needs an interactive run or the guard off; select.md §8 purges a draft headless only onmode=purge, so this guard covers that purge too. -
Load, read the full file, and then execute
references/select.mdto begin the workflow.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |