Generate production-ready SKILL.md and MOAT asset files from a skill design. Enforces MOAT quality dimensions (>=7 on all 6), 500-line body limit, progressive disclosure. Trigger: spec skill, generate skill spec, write SKILL.md, create skill specification, produce skill MOAT.
From plugin-qanpx claudepluginhub javimontano/mao-plugin-qaThis skill is limited to using the following tools:
examples/sample-skill-spec.mdprompts/spec-generation-prompts.mdreferences/frontmatter-field-catalog.mdreferences/moat-structure-spec.mdSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides agent creation for Claude Code plugins with file templates, frontmatter specs (name, description, model), triggering examples, system prompts, and best practices.
"A skill without structure is a prompt with delusions of grandeur."
Generates production-ready SKILL.md files and all associated MOAT asset files (references/, examples/, prompts/) from a skill design document. Every output is scored against the MOAT 6-dimension rubric and revised until all dimensions reach >=7/10.
argument-hint. [Read]name: kebab-case skill identifier.author: from design or default to plugin author.description: 1-3 sentence description ending with trigger phrases prefixed by "Trigger:".argument-hint: from design.allowed-tools: list of tools the skill procedure references.disable-model-invocation, user-invocable, model, context, agent, hooks.references/frontmatter-field-catalog.md for the complete field catalog.Write each section in order:
[Read], [Glob], [Bash].references/ files. Replace with a cross-reference line: > See references/{filename} for details.Based on the design's MOAT strategy:
Evaluate the complete spec package against each dimension (1-10 scale):
| Dimension | Question |
|---|---|
| Trigger Accuracy | Will the description + triggers reliably activate this skill and not false-positive? |
| Completeness | Are all required sections present with minimum counts met? |
| Clarity | Can an LLM follow the procedure without ambiguity? |
| Robustness | Do anti-patterns and edge cases cover realistic failure modes? |
| Efficiency | Is the SKILL.md <=500 lines with progressive disclosure applied? |
| Value Density | Does every line contribute? No filler, no redundancy, no vague statements? |
See references/moat-structure-spec.md for the full rubric with scoring anchors.
[ToolName] notation.design-skill's responsibility.audit-content-quality for independent scoring.Bad spec output:
# My Skill
Do the validation thing. Check stuff. Report results.
Missing: no frontmatter, no guiding principle, no structured procedure, no quality criteria, no anti-patterns, no edge cases, no MOAT assets.
Good spec output:
---
name: validate-config
description: >
Validates plugin configuration files for schema compliance.
Trigger: validate config, check config, config audit.
allowed-tools:
- Read
- Glob
- Grep
---
# Validate Config
> "Configuration is the silent contract between author and runtime."
## Procedure
### Step 1 -- Locate Config Files
- Glob for `*.json` in plugin root. `[Glob]`
...
## Quality Criteria
- [ ] Every config file is validated; none silently skipped.
## Anti-Patterns
1. Accepting trailing commas in JSON without flagging...
## Edge Cases
1. Plugin with zero config files -- report INFO...
MOAT Scores: Trigger=8, Completeness=9, Clarity=8, Robustness=7, Efficiency=9, Value=8
Includes: complete frontmatter, all 7 body sections, MOAT dimension scores.
[Read], [Glob], etc. to know which tools to invoke.