Skill Prompter
Prompting compliance specialist for AI agent skills — rewrites SKILL.md steps with RFC 2119 wording, explicit tools, VERIFY gates, and dry-run checks; also owns skill name + frontmatter description wording (trigger-surface rules). Use only when the user asks to improve or harden a skill's prompts/steps or to name/review a skill description, and confirm with the user before running since this takes quite long time and need to run a few smoke tests with subagents to check if the skill is perfect. Structural lifecycle work goes to skill-manager.
Install
/plugin marketplace add kargnas/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add kargnas/skills --skill skill-promptergit clone --depth 1 https://github.com/kargnas/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/skill-prompter ~/.claude/skills/skill-prompterPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Skill Prompter > **ONE SENTENCE:** Rewrite any AI agent skill's step wording so every step is executed 100% — even by weaker LLMs that skip steps. --- When starting, let the user know in one line that this skill is being used. --- ## Scope and Boundaries Two skills cover the skill lifecycle. Use the right one — they are not interchangeable. | Concern | Owner | |---------|-------| | Step wording, RFC 2119 keywords, atomic decomposition, tool naming, VERIFY gates, decision tables, subagent delegation, escape hatches, dry-run compliance, skill `name` + `description` wording (trigger surface) | **skill-prompter (this skill)** | | Skill creation lifecycle, directory layout, file separation, references/scripts/assets organization, modular architecture, merge/split decisions, anti-patterns of structure | **skill-manager** | **Decision rule:** - "Steps are being skipped on weaker models" → skill-prompter - "I need a new skill from scratch" → skill-manager (then skill-prompter to harden the steps) - "Two skills should be merged" or "this skill is too big" → skill-manager - "Step instructions are vague" → skill-prompter - "Name this skill" or "write/review this skill's description" → skill-prompter (read [references/description-rules.md](references/description-rules.md)) - Both axes need work → run skill-manager first (structure), then skill-prompter (wording), then dry-run If the request is purely structural, **delegate to skill-manager** instead of proceeding here. ---
Details
- Skill name
skill-prompter- Repository
- kargnas/skills
- Path
skills/skill-prompter/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Skill Prompter skill do?
Prompting compliance specialist for AI agent skills — rewrites SKILL.md steps with RFC 2119 wording, explicit tools, VERIFY gates, and dry-run checks; also owns skill name + frontmatter description wording (trigger-surface rules). Use only when the user asks to improve or harden a skill's prompts/steps or to name/review a skill description, and confirm with the user before running since this takes quite long time and need to run a few smoke tests with subagents to check if the skill is perfect. Structural lifecycle work goes to skill-manager.
How do I install the Skill Prompter skill?
Claude Code plugin: /plugin marketplace add kargnas/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Skill Prompter popular?
It lives in kargnas/skills, which has 9 GitHub stars and 1 forks.
Related skills
AI Ready
9kargnas/skills
Use only when the user asks to make the repo AI-ready or AI-optimized (AGENTS.md migration, debugging/testing setup, docs). Do not run on your own.
Design Frontend Sangrak
9kargnas/skills
Use when starting frontend work in a project with no existing design system, when building or theming UI with shadcn/ui or Tailwind CSS, or when asked to review/audit web UI. Default design baseline for new screens, plus container-first responsive rules, URL-first routing, scoped async loading, theme/i18n defaults, and applied UX laws.
Git Lore
9kargnas/skills
Captures, queries, and configures decision context in native Git trailers. Use for non-trivial commit messages, constraints, rejected alternatives, directives, test gaps, Lore history queries, or installing Lore rules in project or global agent instructions.
Skills
9sidneyswift/skills
Install, list, update, or extend Sidney's curated collection of agent skills. Use when asked to install all of Sidney's favorite skills, bootstrap an agent from this collection, or add a skill repository to the collection. This is an installation gateway, not a skill-authoring or general skill-search workflow.
Skill Manager
9kargnas/skills
Creates, restructures, merges, and splits agent skills: directory layout, bundled guides/scripts/assets, cross-agent placement under .agents/skills, importing community skills, merging several skills into one so fewer descriptions load into every session, and a sanitization pass that checks model IDs against models.dev. Triggers on 스킬 생성, 스킬 병합, 스킬 분리, 스킬 구조 정리, 외부 스킬 가져오기, 스킬 검증, 모델 업그레이드. Step wording and name/description wording go to skill-prompter; finding published skill packages goes to skill-finder. Confirm with the user before running, with a brief explanation of what this skill will
Spec Driven Dev
10Archive228/lab-skills
Operating procedure for spec-driven development (SDD) with AI coding agents: treat code as disposable and the specification as the durable, versioned asset, then run the Constitution → Specify → Plan → Tasks → Implement loop (GitHub Spec Kit) with behavior-driven Gherkin-style specs. Trigger whenever building software meant to outlive a prototype — production features, multi-session or multi-agent work on one codebase, or legacy regeneration/migration — instead of vibe-coding straight to code.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.