add-skill

Scaffolds and registers new skills across three registries with mechanical parity verification.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jingtao-lbl/A2MC --skill add-skill-jingtao-lbl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-skill
Source: https://github.com/jingtao-lbl/A2MC/tree/main/.claude/skills/add-skill
Command: npx skills add https://github.com/jingtao-lbl/A2MC --skill add-skill-jingtao-lbl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating or retiring a skill in the A2MC repository requires updating three separate human-facing registries (the README skills table, the skills catalog, and the AGENTS.md capability table) in addition to writing the SKILL.md file itself, and it is easy to leave these out of sync. This skill walks through the full scaffold-and-register (or retire-and-de-register) procedure and verifies 4-way parity mechanically. ## Core Features & Use Cases - Skill scaffolding: Writes a compliant SKILL.md with validated frontmatter fields (name, description, visibility, category) and a mandatory trailing Changelog section. - Triple registry registration: Adds rows to the README "Current skills" table, docs/a2mc_reference/skills_catalog.md, and the AGENTS.md "At a glance" table, then runs tools/check_skill_registry.py to confirm disk-to-registry parity. - Symmetric retirement: Removes a skill from disk and all registries, prunes cross-references, and re-runs the drift check so no stale entries remain. - Use Case: When a recurring procedure appears across multiple dev logs, use this skill to distill it into a reusable, registered skill without leaving the registries half-updated. ## Quick Start Ask the agent to scaffold and register a new skill named for the recurring procedure you want to make reusable, then review the changes before committing.

Frequently Asked Questions about add-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new skill to the A2MC repository?▼

Write a SKILL.md under .claude/skills/<name>/ with valid frontmatter, then register it in the README skills table, docs/a2mc_reference/skills_catalog.md, and the AGENTS.md At a glance table. Run python3 tools/check_skill_registry.py to confirm 4-way parity before committing.

How do I remove or retire a skill without breaking the registry?▼

Delete the skill directory with git rm -r, remove its entries from all three registries plus the CLAUDE.md table, prune cross-references with grep, and re-run check_skill_registry.py. A DRIFT or DEAD-REF failure means a registry or citation still references the removed skill.

Why does check_skill_registry.py fail with a FRONTMATTER-YAML error?▼

The checker strict-parses each SKILL.md frontmatter with yaml.safe_load, and an unquoted colon-space inside the description line is the most common cause. Avoid using ': ' inside description values; use an em dash instead.

What naming and visibility conventions apply to new skills?▼

Skill names are kebab-case and unprefixed, matching the directory name. The visibility field must be public or private and category must be one of phase, calibration, model-dev, meta, kb-build, or authoring, as enforced by the registry checker.

When should a recurring procedure not become a skill?▼

A procedure should not become a skill if it is a one-off task, a single obvious step, or a paraphrase of existing CLAUDE.md guidance. Skills encode easy-to-get-wrong conventions and should only be proposed after a pattern repeats across at least two dev or analysis logs.