Skip to content

Gentleman-Programming/gentle-shell / skills/skill-creator

gentle-ai-skill-creator

Unverified

Trigger: /skill-creation, skill creation, skill creator, create skill, new skill. Create LLM-first skills with valid frontmatter.

Activation Contract

Use this skill when creating or updating a reusable AI skill for Pi or another agent runtime.

Create a skill when:

  • a workflow or convention is reused across sessions;
  • generic agent behavior needs project-specific constraints;
  • a decision tree helps the agent choose safely;
  • examples, templates, or references would make future execution more reliable.

Do not create a skill for a one-off task, generic documentation, or rules that belong in code/tests.

Hard Rules

  • Follow docs/skill-style-guide.md as the normative source for skill structure and style.
  • A skill is an LLM runtime contract, not human-facing docs.
  • Keep SKILL.md concise: target 180–450 tokens, max 1000.
  • Use imperative instructions and concrete gates; avoid tutorials and background prose.
  • Frontmatter description must be one physical YAML-safe line and include trigger words first.
  • Do not add a Keywords section; put essential trigger words in description.
  • Put templates, schemas, and generated examples in assets/.
  • Put longer rationale or local doc links in references/.
  • After changing project skills, refresh the registry with /skill-registry:refresh when available.

Decision Gates

NeedAction
Small reusable behaviorCreate skills/{skill-name}/SKILL.md only
Templates, schemas, fixturesAdd skills/{skill-name}/assets/
Longer explanation or edge casesAdd skills/{skill-name}/references/
Existing skill covers itUpdate the existing skill instead
Skill affects delegation discoveryEnsure trigger words appear in description

Execution Steps

  1. Read docs/skill-style-guide.md before creating or updating skills.
  2. Inspect existing skills and confirm the new skill does not duplicate one.
  3. Choose a kebab-case skill name that matches the user-facing trigger.
  4. Create or update this structure:
skills/{skill-name}/
├── SKILL.md
├── assets/       # optional
└── references/   # optional
  1. Use this frontmatter shape:
---
name: {skill-name}
description: "Trigger: {phrases users or agents will say}. {What this skill does}."
license: Apache-2.0
metadata:
  author: gentleman-programming
  version: "1.0"
---
  1. Write sections in this order: Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract, References.
  2. If this is a packaged gentle-pi skill, add it to scripts/verify-package-files.mjs.
  3. Refresh or document the skill registry update path.

Output Contract

Return:

  • Files created or modified.
  • Whether this created a new skill or updated an existing one.
  • Any supporting assets/ or references/ files added.
  • Whether package verification or skill registry refresh is needed.

References

  • docs/skill-style-guide.md — normative LLM-first skill style guide.
  • skills/skill-registry/SKILL.md — registry refresh and indexing contract.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall