motola10motola10/claude-code-base/.claude/skills/skill-toggle/SKILL.md

skill-toggle

Skill1 starsChanged 5 months agoMITView on GitHub

Enable or disable project-level skills by moving them between .claude/skills/ and .claude/skills-disabled/

1 other project uses a version of this.

Adopted by

Most recently taken up by

tdimino/claude-code-minoantheir own version, first seen Apr 16, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
tdimino/claude-code-minoan★ 41same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- custom-standardsSkill
- agent-code-to-confirmSkill
- agent-to-confirmSkill
- claude-guideline-creationSkill
- skill-creatorSkill
- youtube-to-guidelineSkill
- youtube-transcribeSkill
- fastapi-standardsSkill
- general-standardsSkill
- go-standardsSkill
- java-standardsSkill
- nextjs-standardsSkill
- nodejs-standardsSkill
- python-standardsSkill
- react-standardsSkill
- reviewing-codebasesSkill
- rust-standardsSkill
- typescript-standardsSkill

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Run both commands to get the current state:
line 14
Distinctive:
Ask: "Which skill do you want to enable or disable?"
line 35
Distinctive:
Wait for the user's response before proceeding.
line 37
Distinctive:
Wait for confirmation before proceeding.
line 46
Distinctive:
After the move, re-run the list commands from Step 1 and display the updated state so the user can see the change took effect.
line 67
Very specific:
Only operate on .claude/skills/ and .claude/skills-disabled/ in the current project root.
line 71
Very specific:
Never touch ~/.claude/skills/ (personal/global skills).
line 72
Distinctive:
Never delete skill folders — always move, never remove.
line 73
Very specific:
If the user tries to disable skill-toggle itself, warn them: "Disabling this skill will prevent you from re-enabling skills via …
line 74

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Skill Toggle

Enable or disable project-level skills without deleting them. Disabled skills are preserved in .claude/skills-disabled/ and can be re-enabled at any time.

Step 1 — Discover and list skills

Run both commands to get the current state:

ls .claude/skills/
ls .claude/skills-disabled/ 2>/dev/null || echo "(none)"

Display the results clearly:

Enabled skills (.claude/skills/):
  - agent-code-to-confirm
  - agent-to-confirm
  - ...

Disabled skills (.claude/skills-disabled/):
  - (none)

Step 2 — Ask what to do

Ask: "Which skill do you want to enable or disable?"

Wait for the user's response before proceeding.

Step 3 — Match the skill name

Compare the user's input against the list:

Exact match — proceed directly to Step 4.
Partial / fuzzy match (e.g. user typed youtube, only youtube-transcribe matches) — show the match and ask:
"Did you mean youtube-transcribe? Type yes to confirm or provide a different name." Wait for confirmation before proceeding.
No match — tell the user no skill matched and show the full list again.
Multiple fuzzy matches — list all matches and ask the user to be more specific.

Step 4 — Execute the move

To disable a skill (move from skills/ → skills-disabled/):

mkdir -p .claude/skills-disabled
mv .claude/skills/<skill-name> .claude/skills-disabled/<skill-name>

To enable a skill (move from skills-disabled/ → skills/):

mv .claude/skills-disabled/<skill-name> .claude/skills/<skill-name>

Step 5 — Confirm the result

After the move, re-run the list commands from Step 1 and display the updated state so the user can see the change took effect.

Rules

Only operate on .claude/skills/ and .claude/skills-disabled/ in the current project root.
Never touch ~/.claude/skills/ (personal/global skills).
Never delete skill folders — always move, never remove.
If the user tries to disable skill-toggle itself, warn them: "Disabling this skill will prevent you from re-enabling skills via /skill-toggle. Proceed?" and wait for confirmation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.

Check your setup, free