skill-authoring

Defines patterns for creating, reviewing, and maintaining SKILL.md skill units.

Updated Jan 28, 2024
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/KrockSide --skill skill-authoring-thiago-cruz-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-authoring
Source: https://github.com/Thiago-Cruz-eng/KrockSide/tree/main/.agents/skills/skill-authoring
Command: npx skills add https://github.com/Thiago-Cruz-eng/KrockSide --skill skill-authoring-thiago-cruz-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Writing skills that agents actually trigger and load correctly is hard: vague descriptions never match, bloated bodies waste context, and duplicated scopes drift apart. This Skill provides the authoritative authoring pattern for any skill in .agents/skills/, covering discovery mechanics, description writing, progressive disclosure, and anti-drift maintenance. ## Core Features & Use Cases - Trigger-optimized descriptions: Rules for the 1024-character ceiling, the 300–500 character comfort zone, front-loaded triggers, and action-verb vs. topic-vocabulary anchoring. - Progressive disclosure structure: Guidance on the three loading levels (metadata, body, resources) and when to move detail into references/ or templates into assets/. - Scope and maintenance governance: Criteria for skill vs. always-on instruction, one-skill-per-scope splitting and merging, forbidden body sections, and the anti-drift maintenance block. - Use Case: When asked to create a new domain skill for a project, apply this pattern to write a valid frontmatter, a lean prescriptive body, and ready-to-copy templates from assets/. ## Quick Start Use the skill-authoring skill to review this SKILL.md and fix its frontmatter, description, and structure.

Frequently Asked Questions about skill-authoring

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

FAQPage Schema
How do I write a skill description that triggers correctly?

Put the main use case and trigger words at the start of the description, in running text without lists or keyword fields. Stay in the 300–500 character comfort zone with a hard ceiling of 1024 characters, since the literal description text is what the agent reads to decide loading.

When should a rule become a skill versus an always-on instruction?

A specific, heavy, on-demand procedure becomes a skill; a universal short convention applying to nearly every task belongs in an always-on file like AGENTS.md or CLAUDE.md. Never record the same decision in both places, and escalate ambiguous cases to a human.

What are the naming rules for a SKILL.md frontmatter name?

The name must be 1–64 lowercase characters using only a-z, 0-9, and hyphens, with no leading or trailing hyphen, no double hyphens, no namespace prefix, and it must exactly match the directory name. Errors here make the skill fail silently.

When should skill content move into a references directory?

Move extensive detail such as templates, long technical references, and supporting rules into references/ when the SKILL.md body grows large, treating 500 lines as a reflection point. Keep a short summary and link in the body, and never hide mandatory rules in references.

Why does a skill never trigger or trigger the wrong requests?

A skill that never triggers usually has a vague description without real request words; wrong triggering comes from overlapping scopes with another skill. Fix by front-loading concrete trigger terms and differentiating or merging the overlapping skills.

Can a skill reference another skill for more details?

No. A skill must not reference another skill by name or link, because cross-references bias loading order and create coupling. Describe concepts self-contained, and let each skill's description drive the agent's own loading decision.