How do I install the Gentle AI Skill Improver skill?

Run npx skillmds@latest add gentleman-programming/gentle-ai-skill-improver in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gentle AI Skill Improver safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gentle AI Skill Improver?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gentle AI Skill Improver free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Gentle AI Skill Improver?

Gentleman-Programming (@gentleman-programming) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gentle AI Skill Improver by gentleman-programming

Name: Gentle AI Skill Improver
Author: Gentleman-Programming

File contents

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

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

Output Contract

Return:

Skills audited and paths used.
Issues found, grouped by severity.
Files changed, if apply mode was requested.
Registry refresh recommendation when skill metadata or paths changed.
Ambiguities that need human review.

References

docs/skill-style-guide.md — normative LLM-first skill style guide.
skills/skill-registry/SKILL.md — registry refresh and indexing contract.

---name: gentle-ai-skill-improverdescription: Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.license: Apache-2.0---## Activation ContractUse 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 Steps1. 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 ContractReturn:- Skills audited and paths used.- Issues found, grouped by severity.- Files changed, if apply mode was requested.- Registry refresh recommendation when skill metadata or paths changed.- Ambiguities that need human review.## References- `docs/skill-style-guide.md` — normative LLM-first skill style guide.- `skills/skill-registry/SKILL.md` — registry refresh and indexing contract.

Frequently asked questions

Gentle AI Skill Improver