Agent skill

Skill Update

by transilienceai in transilienceai/communitytools

Skill creation, update and management — generates skill directory structure, validates against best practices, enforces line count limits.

MITAuto-check passedSecurity

Install Skill Update

skills CLI

$ npx skills add transilienceai/communitytools --skill skill-update -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install transilienceai/communitytools skill-update --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/transilienceai/communitytools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-update .claude/skills/skill-update && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "skill-update" agent skill from https://github.com/transilienceai/communitytools/tree/main/skills/skill-update into .claude/skills/skill-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-update", 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

$skill-installer install https://github.com/transilienceai/communitytools/tree/main/skills/skill-update

Type 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.

skills CLI

$ npx skills add transilienceai/communitytools --skill skill-update -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install transilienceai/communitytools skill-update --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/transilienceai/communitytools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skill-update .agents/skills/skill-update && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "skill-update" agent skill from https://github.com/transilienceai/communitytools/tree/main/skills/skill-update into .agents/skills/skill-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-update", 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.

skills CLI

$ npx skills add transilienceai/communitytools --skill skill-update -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install transilienceai/communitytools skill-update --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/transilienceai/communitytools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skill-update .cursor/skills/skill-update && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "skill-update" agent skill from https://github.com/transilienceai/communitytools/tree/main/skills/skill-update into .cursor/skills/skill-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-update", 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

$ gemini skills install https://github.com/transilienceai/communitytools.git --path skills/skill-update

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add transilienceai/communitytools --skill skill-update -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install transilienceai/communitytools skill-update --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/transilienceai/communitytools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skill-update .gemini/skills/skill-update && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "skill-update" agent skill from https://github.com/transilienceai/communitytools/tree/main/skills/skill-update into .gemini/skills/skill-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-update", 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.

GitHub CLI

$ gh skill install transilienceai/communitytools skill-update

Installs 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).

skills CLI

$ npx skills add transilienceai/communitytools --skill skill-update -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/transilienceai/communitytools.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skill-update .github/skills/skill-update && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "skill-update" agent skill from https://github.com/transilienceai/communitytools/tree/main/skills/skill-update into .github/skills/skill-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-update", 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.

skills CLI

$ npx skills add transilienceai/communitytools --skill skill-update -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install transilienceai/communitytools skill-update --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/transilienceai/communitytools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skill-update .opencode/skills/skill-update && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "skill-update" agent skill from https://github.com/transilienceai/communitytools/tree/main/skills/skill-update into .opencode/skills/skill-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-update", 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-update
GitHub stars: 562
Token cost: ~1.2k tokens
SKILL.md length: 421 words
Files: 5
Skills in repo: 35
Repo updated: Jul 29, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Skill creation, update and management — generates skill directory structure, validates against best practices, enforces line count limits.

Works in 4 steps: Generalizable. Reusable pattern, not… → Material improvement. Adds coverage,… → Not already captured elsewhere in the… → …
Improving skills
SKILL.md covers Hard caps (enforced by…, Principles, File structure and SKILL.md template, plus 6 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Skill Update is an agent skill from transilienceai/communitytools. Skill creation, update and management — generates skill directory structure, validates against best practices, enforces line count limits. Use when creating, updating, or improving skills.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `reference/CONTENT.md`, `reference/FRONTMATTER.md` and `reference/ROUTING.md`).

It sits in Security. 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

Improving skills

Example prompts

“/skill-update”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Generalizable. Reusable pattern, not target-specific lore. No machine names, lab IDs, target IPs, preserved flags, writeup attributions.
Material improvement. Adds coverage, efficiency, or decision-quality for future engagements.
Not already captured elsewhere in the skill base. (scripts/skill_linter.py flags duplicates.)
Minimal footprint. Prefer extending an existing entry over adding a new file. Keep the base lean and high-signal.

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 (its code samples are yaml).
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 Update loads about 1.2k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 421 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~50
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

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). 421 words, ~1,196 tokens.

Download SKILL.mdSave it as .claude/skills/skill-update/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: skill-update
description: Skill creation, update and management — generates skill directory structure, validates against best practices, enforces line count limits. Use when creating, updating, or improving skills.
model: opus

Skill Update

Generate or refine Claude Code skills following Anthropic best practices.

Hard caps (enforced by `scripts/skill_linter.py`)

SKILL.md ≤ 150 lines
reference/*.md ≤ 200 lines (reference/scenarios/*.md ≤ 400 lines)
README.md ≤ 100 lines
Every SKILL.md has YAML frontmatter with name + description
No DO NOT / MUST NOT / NEVER outside an ## Anti-Patterns section
No challenge-specific identifiers (machine names, lab IDs, lab IPs, preserved flags)
Every Markdown link resolves to an existing file
Every reference file is linked from at least one other file (no orphans)

Principles

Brevity first. Every file short, simple, human-readable. Challenge every token.
Progressive disclosure. SKILL.md navigates; reference/ holds detail; reference/scenarios/ holds concrete exploit flows.
Separation of concern. SKILL.md = WHAT + when. reference/role-*.md = HOW agents behave when spawned.
Single canonical home for any cross-cutting rule (output discipline, credential loading, brute-force, etc.). Other files reference, never restate.

File structure

skills/<skill-name>/
├── SKILL.md           # ≤150 lines, YAML + navigation
├── reference/
│   ├── *-principles.md  # ≤150 lines (decision tree)
│   ├── INDEX.md
│   ├── *.md             # patterns, ≤200 lines
│   └── scenarios/
│       └── <category>/
│           └── *.md     # ≤400 lines, self-contained
└── README.md          # optional, ≤100 lines

SKILL.md template

yaml

---
name: <skill-name>
description: What it does AND when to use. Include trigger phrases.
---

# <Skill Name>

<one-paragraph scope>

## When to use

- <bullet>

## Workflow / Quick start

<≤30 lines>

## References

- [reference/...](reference/...)

## Anti-Patterns

- <when negative framing is genuinely needed, put it here>

Run it

The procedure is a workflow — every step is code-enforced, so none can be skipped.

Workflow('skill-update', { output_dir: 'projects/<engagement>' })   // harvest an engagement
Workflow('skill-update', { learnings: [{ text, technique_type }] }) // judge a known set
Workflow('skill-update', { mode: 'audit' })                         // read-only, writes nothing

Add dryRun: true to see the write plan without writing. Parent-orchestrator only.

Phases. Intake (baseline skill_linter.py --json) → Harvest (reframe learnings) → Judge (four gates + blind refuters) → Route (author the block) → Write (persist verbatim) → Sweep (confidentiality guard) → Verify (linter delta, not an absolute clean tree — the base carries pre-existing violations).

Every promote/reject/write decision is pure JS in .claude/workflows/lib/wf-helpers.mjs (promotionGate, capBudget, writeGate, lintDelta, skillUpdateGate). No agent decides whether a learning is promoted or a write is allowed.

Show full SKILL.md (195 more words)Show less

The four-gate promotion test

Process the techniques and failure modes from completed engagements. Promote a learning to the skill base only if all four hold:

Generalizable. Reusable pattern, not target-specific lore. No machine names, lab IDs, target IPs, preserved flags, writeup attributions.
Material improvement. Adds coverage, efficiency, or decision-quality for future engagements.
Not already captured elsewhere in the skill base. (scripts/skill_linter.py flags duplicates.)
Minimal footprint. Prefer extending an existing entry over adding a new file. Keep the base lean and high-signal.

Reframing recipe

Always frame as a reusable pattern: "when encountering X condition, try Y approach" — never "on box-N, Y worked". Use <TARGET_IP>, <DC_FQDN>, <DOMAIN> placeholders in tool examples.

Output

Three buckets, built in code so a run cannot claim an edit it did not make: Updated. / Skipped. (with the gate that failed) / No changes.

Reference

STRUCTURE.md — directory layout requirements.
FRONTMATTER.md — YAML rules.
CONTENT.md — writing guidelines.
ROUTING.md — technique type → target file.

Anti-Patterns

Creating CHANGELOG.md / SUMMARY.md / VERIFICATION.md auxiliary files.
Meta-documentation about the creation process inside the skill itself.
Verbose inline templates and examples (link to reference/ instead).
Re-introducing duplicate rule prose (brute-force, output-dir, env-reader).
Files past their cap — split into reference/ immediately.

Files

SKILL.md and 4 other files in skills/skill-update of transilienceai/communitytools.

SKILL.md
reference/CONTENT.md
reference/FRONTMATTER.md
reference/ROUTING.md
reference/STRUCTURE.md

Open the folder on GitHubat commit 95fdc12

Compare with similar skills

Skill Update 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 Update compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Skill Update this skilltransilienceai/communitytools	562	—	~1.2k	Automated safety check: Pass	MIT	2 mo ago
Fla Ascend Performancefla-org/flash-linear-attention	5.8k	—	~6.3k	Automated safety check: Pass	MIT	yesterday
Deepsec Documentation Guidevercel-labs/deepsec	8.1k	—	~956	Automated safety check: Pass	Apache-2.0	10 days ago
Skill Scannergetsentry/skills	1k	4 repos	~2.5k	Automated safety check: Warn	Apache-2.0	7 days ago
Serenity Aleabitoreddityan-labs/serenity-aleabitoreddit	481	1 repos	~3.3k	Automated safety check: Pass	None	8 days ago
Security Alert Triageelastic/agent-skills	592	1 repos	~3.5k	Automated safety check: Notes	Apache-2.0	2 days ago

Similar skills

Fla Ascend Performance
fla-org/flash-linear-attention
Guidelines for Ascend NPU kernel / Triton-Ascend backend performance work in the FLA repo.
5.8k GitHub stars~6.3k tokensUpdated yesterday
SecurityAuto-check passed
Deepsec Documentation Guide
vercel-labs/deepsec
Official
Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.
8.1k GitHub stars~956 tokensUpdated 10 days ago
SecurityAuto-check passed
Skill Scanner
getsentry/skills
Official
Scan agent skills for security issues. An agent skill from getsentry/skills.
1k GitHub starsUsed in 4 repos~2.5k tokens
SecurityAuto-check: warnings
Serenity Aleabitoreddit
yan-labs/serenity-aleabitoreddit
Apply trader Serenity's (@aleabitoreddit) AI/semiconductor supply-chain analytical lens to US-stock ideas and market judgment.
481 GitHub starsUsed in 1 repo~3.3k tokens
SecurityAuto-check passed
Security Alert Triage
elastic/agent-skills
Official
Triage Elastic Security alerts — gather context, classify threats, create cases, and acknowledge.
592 GitHub starsUsed in 1 repo~3.5k tokens
SecurityAuto-check: notes
Shiro Attack CLI
SummerSec/ShiroAttack2
当用户要求利用、检测或测试 Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 时使用。触发词包括 "Shiro"、"rememberMe"、"shiro attack"、"CVE-2016-4437"、"Shiro-550"、"爆破 Shiro key"、"利用 Shiro"、"Shiro…
2.6k GitHub stars~945 tokensUpdated 4 mo ago
SecurityAuto-check passed

Questions about Skill Update

What does Skill Update do?

Skill creation, update and management — generates skill directory structure, validates against best practices, enforces line count limits. Skill Update is an agent skill from transilienceai/communitytools. Skill creation, update and management — generates skill directory structure, validates against best practices, enforces line count limits.

When should I use Skill Update?

Skill Update fits situations like: improving skills.

How do I install Skill Update in Claude Code?

Run `npx skills add transilienceai/communitytools --skill skill-update -a claude-code`. Or copy the skill folder (skills/skill-update in transilienceai/communitytools) into .claude/skills/skill-update in your project. Claude Code loads it when a task matches its description.

How do I install Skill Update in Codex?

Run `npx skills add transilienceai/communitytools --skill skill-update -a codex`. Or copy the skill folder (skills/skill-update in transilienceai/communitytools) into .agents/skills/skill-update in your project. Codex loads it when a task matches its description.

Can I use Skill Update 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-update -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-update, .gemini/skills/skill-update, .github/skills/skill-update and .opencode/skills/skill-update in your project.

What does Skill Update need to run?

SKILL.md names no scripts, command-line tools or credentials: Skill Update is instructions for the agent only.

Does Skill Update 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 Update 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 Update use?

Skill Update 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 Update use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 Update?

Skills that share tags, products or a category with Skill Update: Fla Ascend Performance (fla-org/flash-linear-attention, 5.8k stars), Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Skill Scanner (getsentry/skills, 1k stars) and Serenity Aleabitoreddit (yan-labs/serenity-aleabitoreddit, 481 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Skill Update?

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.

Install Skill Update

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Skill Update

Hard caps (enforced by scripts/skill_linter.py)

Principles

File structure

SKILL.md template

Run it

The four-gate promotion test

Reframing recipe

Output

Reference

Anti-Patterns

Files

Compare with similar skills

Similar skills

More from transilienceai/communitytools

Related

Questions about Skill Update

Hard caps (enforced by `scripts/skill_linter.py`)