gentle-ai-skill-improver

gentle-ai-skill-improver is a skill for Claude Code, Codex from Gentleman-Programming/gentle-pi. It costs 33 tokens per session (579 once invoked), scanned A, original, MIT.

A reviewer for existing AI-agent skills, which are instruction files that guide an agent through recurring work. It checks their structure, wording, triggers, and rules against the project’s guidance.

In plain words
What is it for?
Use it to audit or refactor SKILL.md files, preserve important behavior, and identify changes that need human review.
Why use it?
It helps find unclear, oversized, inconsistent, or incorrectly scoped skill instructions without silently changing the author’s intent.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/gentleman-programming/gentle-pi/skill-improver
Any agent
npx skills add Gentleman-Programming/gentle-pi --skill skill-improver
Clone the repo
git clone --depth 1 https://github.com/Gentleman-Programming/gentle-pi

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for gentle-ai-skill-improver

README.md
[![agentmods](https://agentmods.dev/badge/skills/gentleman-programming/gentle-pi/skill-improver.svg)](https://agentmods.dev/skills/gentleman-programming/gentle-pi/skill-improver)
Your own site
<a href="https://agentmods.dev/skills/gentleman-programming/gentle-pi/skill-improver"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentle-pi/skill-improver.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 579 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.00579
Opus 5 $0.00016 $0.00290
Sonnet 5 $0.00007 $0.00116
Haiku 4.5 $0.00003 $0.00058

Measured 5d ago against content hash 83d41f4e3f53, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gentle-ai-skill-improver scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/skill-improver/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Activation Contract

Use this skill when auditing, refactoring, normalizing, or improving existing SKILL.md files. Use gentle-ai-skill-creator when creating a brand-new skill from a reusable pattern.

Hard Rules

  • Read docs/skill-style-guide.md first and treat it as the normative style contract.
  • Treat SKILL.md as the source of truth; preserve author intent, critical rules, activation semantics, and output requirements.
  • Use .atl/skill-registry.md as an index of skill names, triggers, scopes, and exact paths when available.
  • Default to audit-only. Modify files only when the user explicitly asks to apply improvements.
  • Never delete meaningful content silently; move long explanation, examples, templates, or schemas into local references/ or assets/.
  • Do not invent triggers, policies, or domain rules. Mark ambiguous cases for human review.

Decision Gates

Situation Action
Missing or invalid frontmatter Fix name, quoted one-line description, license, and metadata
Skill reads like tutorial docs Convert to runtime instructions and move background to references/
Body exceeds budget Preserve rules, move examples/background to supporting files
Branching logic hidden in prose Convert to a compact decision table
Rules conflict or intent is unclear Report the issue; do not rewrite that rule automatically

Execution Steps

  1. Read docs/skill-style-guide.md.
  2. Read .atl/skill-registry.md; use listed paths to select skills. If missing, scan known skill directories for */SKILL.md.
  3. For each selected skill, audit metadata, trigger clarity, section order, body budget, actionability, decision gates, output contract, and local references.
  4. Return an audit report grouped by skill with severity and exact proposed changes.
  5. In apply mode, edit only safe issues, preserve content, create supporting files when needed, then refresh or request /skill-registry:refresh.

Output Contract

Read the full file on GitHub · 54 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 54 lines · 33 tokens per session scan A 83d41f4e3f53

Subscribe to this mod's changes

gentle-ai-skill-improver is a skill published in the GitHub repository Gentleman-Programming/gentle-pi (415 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 579 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens