authoring-skills

Author and refactor Agent Skills with structured frontmatter, references, and validation workflows.

1|Updated Sep 3, 2017
One-click install
npx skills add https://github.com/mmgeorge/config --skill authoring-skills-mmgeorge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: authoring-skills
Source: https://github.com/mmgeorge/config/tree/main/rulesync-global/.rulesync/skills/authoring-skills
Command: npx skills add https://github.com/mmgeorge/config --skill authoring-skills-mmgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Writing an effective Agent Skill is hard: vague descriptions cause poor discovery, bloated SKILL.md files waste context tokens, and unvalidated instructions fail in production. This Skill provides a structured methodology for creating, restructuring, and evaluating Agent Skills so they trigger reliably and execute deterministically. ## Core Features & Use Cases - Five-Step Authoring Workflow: Identify baseline gaps, draft minimal SKILL.md files, apply progressive disclosure, validate execution, and iterate on real workflows. - Progressive Disclosure Guidance: Rules for when to split content into references/, scripts/, and assets/ versus keeping it unified in SKILL.md. - Evaluation Framework: Multi-phase validation covering trigger accuracy, deterministic logic, and edge cases, with a JSON evaluation schema template. - Use Case: You notice an agent repeatedly fails at a domain task. Use this Skill to record the baseline failures, draft a targeted SKILL.md with precise frontmatter triggers, bundle reference docs and templates, and validate discovery accuracy before deployment. ## Quick Start Help me author a new Agent Skill for processing PDF forms, including the SKILL.md frontmatter, reference structure, and evaluation test cases.

Frequently Asked Questions about authoring-skills

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

FAQPage Schema
How do I write a good SKILL.md description for skill discovery?▼

Open with an imperative or infinitive verb phrase in third person, state what the skill does, and add a 'Use when...' clause with concrete keywords, file extensions, and trigger conditions. Avoid vague phrasing like 'helps with documents' and second-person directives.

When should I split content into references files?▼

Extract content into references/ only when an agent can execute a distinct subset of tasks without loading the other parts, such as specialized schemas or rare error codes. Keep universally required baseline rules unified in SKILL.md to avoid fragmentation.

What is the recommended structure for an Agent Skill directory?▼

A skill directory contains SKILL.md at the root, with optional references/ for on-demand documentation, scripts/ for deterministic executables, and assets/ for output templates. The directory name must match the frontmatter name, and subdirectories stay one level deep.

How do I validate that a skill triggers correctly?▼

Run Phase 1 validation by providing only the name and description, then test three queries that must trigger the skill and three similar queries that must not. Refine the description until trigger accuracy reaches 100%.

How long should a SKILL.md file be?▼

Keep the SKILL.md body under 500 lines as a navigable structural overview. Move extended schemas, templates, and detailed references into references/ or assets/ files, each linked directly from SKILL.md.

When should I not create a new Agent Skill?▼

Do not create a skill if baseline execution of representative tasks succeeds consistently without guidance. Skills should only address recorded functional gaps, unverified assumptions, or domain context that required manual intervention.