Skill Prune logo

Skill Prune

Organization
transilienceai
skill-prune

Identify and remove negative-ROI skill content — orphan files, never-read entries, duplicates, content reintroducing challenge-specific lore. Inverse of /skill-update. Use during quarterly maintenance or after the linter flags issues.

Overview

Publishertransilienceai
Repositorycommunitytools
Skill nameskill-prune
Stars
565
Forks
81
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by transilienceai on GitHub. Read the source before you install it.

Installation

Install the Skill Prune AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/transilienceai/communitytools/tree/main/skills/skill-prune
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/transilienceai/communitytools.git /tmp/communitytools
mkdir -p .claude/skills
cp -r /tmp/communitytools/skills/skill-prune .claude/skills/skill-prune
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Skill Prune in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Skill Prune on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Skill Prune is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Skill Prune

Inverse of /skill-update. Removes content rather than adding it. Run during quarterly maintenance, after engagements, or when scripts/skill_linter.py reports orphans / duplicates.

When to invoke

  • Quarterly cadence.
  • After scripts/skill_linter.py --check-orphans reports orphan reference files.
  • After a SKILL.md or reference file grows past its cap and needs trimming.
  • After a de-specialization sweep, to drop content tied to retired challenges.

Prune criteria (the four signals — same shape as /skill-update, inverted)

A reference / scenario / line is a prune candidate when it satisfies any of:

  1. Orphan — not linked from any SKILL.md or other reference file in the last 60 days.
  2. Referenced only by failed engagements — appeared in attack-chain.md of runs that ended status=BLOCKED, never in a successful chain.
  3. Contradicted by newer content — a later scenario / pattern supersedes it; the older entry no longer reflects current technique.
  4. Redundant with newer content — same technique covered more clearly elsewhere.

Removing content fails any of these → keep it.

Safety rules

  • Never prune a file with <!-- KEEP: <reason> --> annotation.
  • Never prune content cited in a still-open engagement's OUTPUT_DIR/attack-chain.md.
  • Never prune the canonical-home file for a single-owner rule (brute-force, output-discipline, env-reader, skill-update).
  • Bias toward keeping technique-rich content over operational lore.

Procedure

  1. Run scripts/skill_linter.py --check-orphans to surface orphans.
  2. For each candidate file or block, evaluate the four signals.
  3. Build a deletion plan — show files / lines to remove with one-line rationale per item.
  4. Apply deletions only after the plan is approved (skill-prune does not auto-delete during invocation).
  5. Re-run scripts/skill_linter.py to confirm the change broke no other links and didn't reintroduce duplicates.

Output

Concise change report:

  • Removed. File or block + one-line rationale per item.
  • Kept (flagged for follow-up). Items that failed all four signals but are worth revisiting next quarter.
  • No prunes. State explicitly when nothing warranted removal.

Anti-Patterns

  • Pruning content because it's old — age alone is not a signal; relevance is.
  • Pruning a reference because its parent SKILL.md is bloated — fix the SKILL.md instead.
  • Removing a single-owner canonical file (brute-force / output-discipline / env-reader).
  • Pruning during an active engagement that may still cite the content.

Frequently asked questions

What does the Skill Prune AI skill do?

Identify and remove negative-ROI skill content — orphan files, never-read entries, duplicates, content reintroducing challenge-specific lore. Inverse of /skill-update. Use during quarterly maintenance or after the linter flags issues.

Why use Skill Prune on TypingMind?

Because you install it once and use it with any model. Skill Prune is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Skill Prune in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/transilienceai/communitytools/tree/main/skills/skill-prune. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Skill Prune?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Skill Prune?

As many as you like. As long as a model supports skills, you can use Skill Prune with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Skill Prune AI skill free?

Yes. It is published on GitHub by transilienceai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇