authoring-skills

Author, mirror, and validate SKILL.md files across .agents and .claude skill trees.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/tomada1114/quick-reply-drill --skill authoring-skills-tomada1114
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: authoring-skills
Source: https://github.com/tomada1114/quick-reply-drill/tree/main/.agents/skills/authoring-skills
Command: npx skills add https://github.com/tomada1114/quick-reply-drill --skill authoring-skills-tomada1114

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A malformed SKILL.md can pass formatting, spell-check, and tree-sync checks yet silently never load in Claude Code or Codex CLI, and hand-edited mirror copies drift from their source. This Skill defines the authoring, mirroring, and validation workflow that keeps skills discoverable and the two skill trees byte-identical. ## Core Features & Use Cases - Single-source authoring workflow: Edit skills only under .agents/skills/, then mirror into .claude/skills/ with pnpm agents:sync, never hand-editing the generated copy. - Frontmatter contract: Enforces exactly two keys (name and description), name matching the directory, English-only text, and a length cap, validated by tests/skills-frontmatter.test.ts. - Layout and drift rules: One directory level per skill, no nested SKILL.md files, no symlinks, with pnpm agents:check and a pre-commit hook comparing both trees byte for byte. - Use Case: When adding a new skill, you write .agents/skills/<name>/SKILL.md with a two-line ownership block, run pnpm agents:sync, pnpm agents:check, and pnpm test, then commit both trees knowing the skill will actually load in both hosts. ## Quick Start Ask the AI to create a new skill named my-workflow under .agents/skills/ following the authoring rules, then sync and validate it with pnpm agents:sync, pnpm agents:check, and pnpm test.

Frequently Asked Questions about authoring-skills

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

FAQPage Schema
How do I add a new skill to a repository for Claude Code and Codex CLI?▼

Create .agents/skills/<name>/SKILL.md with frontmatter containing only name and description, where name matches the directory exactly. Run pnpm agents:sync to mirror it into .claude/skills/, then verify with pnpm agents:check and pnpm test before committing both trees.

Why is my SKILL.md not loading in Claude Code or Codex CLI?▼

Common causes are frontmatter that fails to parse, a name that disagrees with its directory, extra frontmatter keys, or a nested SKILL.md registering as a nameless skill. These pass formatting and sync checks silently; tests/skills-frontmatter.test.ts is the gate that catches them.

Can I edit files directly under .claude/skills/ instead of .agents/skills/?▼

No. The .claude/skills/ tree is generated by scripts/sync-agents.mjs and the next sync silently overwrites hand edits. Always edit the .agents/skills/ source, run pnpm agents:sync, and commit both sides together.

What frontmatter fields are allowed in a SKILL.md file?▼

Exactly two keys: name and description. Host-specific keys like paths are rejected because Codex CLI ignores unknown keys and matches only on description, which would make the same skill auto-fire on different terms per host.

When should I create a new skill versus extending an existing one?▼

Add a skill only for recurring work needing a workflow, references, or on-demand policy, not for a fact stated once. Extend an existing skill when the new material is a variant of what it already covers, and keep each rule in exactly one home to avoid drift.