Rsigma
timescale/rsigma
Use the rsigma CLI and MCP server: engine eval, engine daemon, rule lint, rule draft, rule tune, rule backtest, backend convert, mcp serve.
Identify and remove negative-ROI skill content — orphan files, never-read entries, duplicates, content reintroducing challenge-specific lore.
Install Skill Prune
$ npx skills add transilienceai/communitytools --skill skill-prune -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install transilienceai/communitytools skill-prune --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/transilienceai/communitytools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-prune .claude/skills/skill-prune && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "skill-prune" agent skill from https://github.com/transilienceai/communitytools/tree/main/skills/skill-prune into .claude/skills/skill-prune/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-prune", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/transilienceai/communitytools/tree/main/skills/skill-pruneType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add transilienceai/communitytools --skill skill-prune -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install transilienceai/communitytools skill-prune --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/transilienceai/communitytools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skill-prune .agents/skills/skill-prune && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-prune" agent skill from https://github.com/transilienceai/communitytools/tree/main/skills/skill-prune into .agents/skills/skill-prune/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-prune", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add transilienceai/communitytools --skill skill-prune -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install transilienceai/communitytools skill-prune --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/transilienceai/communitytools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skill-prune .cursor/skills/skill-prune && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "skill-prune" agent skill from https://github.com/transilienceai/communitytools/tree/main/skills/skill-prune into .cursor/skills/skill-prune/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-prune", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/transilienceai/communitytools.git --path skills/skill-prune--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add transilienceai/communitytools --skill skill-prune -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install transilienceai/communitytools skill-prune --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/transilienceai/communitytools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skill-prune .gemini/skills/skill-prune && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "skill-prune" agent skill from https://github.com/transilienceai/communitytools/tree/main/skills/skill-prune into .gemini/skills/skill-prune/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-prune", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install transilienceai/communitytools skill-pruneInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add transilienceai/communitytools --skill skill-prune -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/transilienceai/communitytools.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skill-prune .github/skills/skill-prune && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "skill-prune" agent skill from https://github.com/transilienceai/communitytools/tree/main/skills/skill-prune into .github/skills/skill-prune/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-prune", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add transilienceai/communitytools --skill skill-prune -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install transilienceai/communitytools skill-prune --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/transilienceai/communitytools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skill-prune .opencode/skills/skill-prune && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "skill-prune" agent skill from https://github.com/transilienceai/communitytools/tree/main/skills/skill-prune into .opencode/skills/skill-prune/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-prune", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
skill-prune- GitHub stars
- 562
- Token cost
- ~715 tokens
- SKILL.md length
- 339 words
- Files
- 1
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- MIT
At a glance
Identify and remove negative-ROI skill content — orphan files, never-read entries, duplicates, content reintroducing challenge-specific lore.
- Works in 4 steps: Orphan — not linked from any SKILL.md or… → Referenced only by failed engagements —… → Contradicted by newer content — a later… → …
- Tasks that involve Linting and formatting
- SKILL.md covers When to invoke, Prune criteria (the four…, Safety rules and Procedure, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Skill Prune is an agent skill from transilienceai/communitytools. 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.
Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Linting and formatting. The repository describes itself as: Open-source Claude Code skills, agents, and slash commands for AI-powered penetration testing, bug bounty hunting, and security research. The licence is MIT.
When your agent uses it
- Tasks that involve Linting and formatting
Example prompts
- “/skill-prune”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Orphan — not linked from any SKILL.md or other reference file in the last 60 days.
- Referenced only by failed engagements — appeared in attack-chain.md of runs that ended status=BLOCKED, never in a successful chain.
- Contradicted by newer content — a later scenario / pattern supersedes it; the older entry no longer reflects current technique.
- Redundant with newer content — same technique covered more clearly elsewhere.
What it can do on your machine
Read from SKILL.md and the folder at commit 95fdc12. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Skill Prune loads about 715 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 339 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from transilienceai/communitytools at commit 95fdc12, republished under its MIT licence (© transilienceai). 339 words, ~715 tokens.
Download SKILL.mdSave it as
.claude/skills/skill-prune/SKILL.md (or your agent's skills folder).- name
- skill-prune
- description
- 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.
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-orphansreports 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:
- Orphan — not linked from any SKILL.md or other reference file in the last 60 days.
- Referenced only by failed engagements — appeared in
attack-chain.mdof runs that endedstatus=BLOCKED, never in a successful chain. - Contradicted by newer content — a later scenario / pattern supersedes it; the older entry no longer reflects current technique.
- 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
- Run
scripts/skill_linter.py --check-orphansto surface orphans. - For each candidate file or block, evaluate the four signals.
- Build a deletion plan — show files / lines to remove with one-line rationale per item.
- Apply deletions only after the plan is approved (skill-prune does not auto-delete during invocation).
- Re-run
scripts/skill_linter.pyto 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.
© transilienceai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/skill-prune of transilienceai/communitytools.
Open the folder on GitHubat commit 95fdc12
Compare with similar skills
Skill Prune next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skill Prune this skilltransilienceai/communitytools | 562 | — | ~715 | Automated safety check: Pass | MIT | |
| Rsigmatimescale/rsigma | 162 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Golang Continuous Integrationsamber/cc-skills-golang | 3.4k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Golang Continuous Integrationcontext-labs/whip | 1.1k | — | ~3.5k | Automated safety check: Pass | MIT | |
| FixBUZZARDGTA/Session-Sniffer | 104 | — | ~2.7k | Automated safety check: Pass | GPL-3.0 | |
| Ship Releaseibuilder/massing | 122 | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
Golang Continuous Integration
samber/cc-skills-golang
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release…
Golang Continuous Integration
context-labs/whip
CI/CD with GitHub Actions for Golang — testing, linting, SAST, security scanning, coverage, Dependabot, Renovate, GoReleaser, release pipelines.
Fix
BUZZARDGTA/Session-Sniffer
Diagnose and fix Session Sniffer bugs, errors, tracebacks, logs, lint failures, static-analysis findings, test failures, and IDE-reported problems.
Ship Release
ibuilder/massing
The Massing release discipline — how to ship a verified, CI-green version-numbered release direct to main.
Lint
ethereum/execution-specs
Run and fix the repository static analysis suite. An agent skill from ethereum/execution-specs.
More from transilienceai/communitytools
All 35 skills in this repoDfir
transilienceai/communitytools
Digital forensics and incident response - Windows event log analysis, PCAP forensics, filesystem artifact analysis, AD attack detection, and timeline correlation.
GitHub Workflow
transilienceai/communitytools
GitHub workflow automation — branching, committing, pushing, pull requests, issues, and code review.
Pci Secure Software
transilienceai/communitytools
Automated PCI Secure Software Standard (SSS) v2.0 readiness gap-assessment of an application from its source code and documentation.
Protect With Password
transilienceai/communitytools
Generate ONE strong password and apply it to each referenced file (PDF, Word, Excel, PowerPoint, or any type).
Skill Update
transilienceai/communitytools
Skill creation, update and management — generates skill directory structure, validates against best practices, enforces line count limits.
Source Code Scanning
transilienceai/communitytools
Security-focused source code review and SAST. An agent skill from transilienceai/communitytools.
Related
Categories
Questions about Skill Prune
What does Skill Prune do?
Identify and remove negative-ROI skill content — orphan files, never-read entries, duplicates, content reintroducing challenge-specific lore. Skill Prune is an agent skill from transilienceai/communitytools. Identify and remove negative-ROI skill content — orphan files, never-read entries, duplicates, content reintroducing challenge-specific lore.
When should I use Skill Prune?
Skill Prune fits situations like: tasks that involve Linting and formatting.
How do I install Skill Prune in Claude Code?
Run `npx skills add transilienceai/communitytools --skill skill-prune -a claude-code`. Or copy the skill folder (skills/skill-prune in transilienceai/communitytools) into .claude/skills/skill-prune in your project. Claude Code loads it when a task matches its description.
How do I install Skill Prune in Codex?
Run `npx skills add transilienceai/communitytools --skill skill-prune -a codex`. Or copy the skill folder (skills/skill-prune in transilienceai/communitytools) into .agents/skills/skill-prune in your project. Codex loads it when a task matches its description.
Can I use Skill Prune in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add transilienceai/communitytools --skill skill-prune -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-prune, .gemini/skills/skill-prune, .github/skills/skill-prune and .opencode/skills/skill-prune in your project.
What does Skill Prune need to run?
SKILL.md names no scripts, command-line tools or credentials: Skill Prune is instructions for the agent only.
Does Skill Prune access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Skill Prune safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Skill Prune use?
Skill Prune is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Skill Prune use?
About 715 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Skill Prune?
Skills that share tags, products or a category with Skill Prune: Rsigma (timescale/rsigma, 162 stars), Golang Continuous Integration (samber/cc-skills-golang, 3.4k stars), Golang Continuous Integration (context-labs/whip, 1.1k stars) and Fix (BUZZARDGTA/Session-Sniffer, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill Prune?
transilienceai (a GitHub organization) maintains it in transilienceai/communitytools, which has 562 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on July 29, 2026.
Source: transilienceai/communitytools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.