skill-authoring

Authors, reviews, and evaluates Agent Skills and their SKILL.md files.

22|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/Lynricsy/HyperSkills --skill skill-authoring-lynricsy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-authoring
Source: https://github.com/Lynricsy/HyperSkills/tree/main/skills/skill-authoring
Command: npx skills add https://github.com/Lynricsy/HyperSkills --skill skill-authoring-lynricsy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing an Agent Skill that actually triggers, loads, and improves agent behavior is hard: descriptions fail to route, bodies exceed context budgets, references never get read, and rules restate what the model already knows. This Skill provides the specification constraints, authoring rules, evaluation methodology, and publishing mechanics to build skills that measurably close real baseline gaps. ## Core Features & Use Cases - Specification-grounded authoring: Enforces the agentskills.io frontmatter contract (name rules, description limits, allowed fields) plus body budgets, one-level reference depth, and progressive disclosure tiers. - Evaluation-driven development: Requires at least three scenarios with a near-miss negative and a measured no-skill baseline before writing body text, with grading schemas and variance guidance. - Review and optimization workflows: Structured checklists for reviewing existing skills, optimizing descriptions with held-out trigger query sets, and a two-agent iteration loop that reads navigation signals. - Publishing and provenance: Covers installer scan rules, flat repository layout, per-directory licensing, SOURCES.yaml provenance records, and generated NOTICE attribution. - Use Case: A team repeatedly re-explains internal GraphQL gateway rules to their agent; use this Skill to baseline the failures, draft a minimal skill closing only those gaps, and verify with trigger-rate measurements before publishing it to the team repository. ## Quick Start Ask the agent to review your existing SKILL.md file for spec compliance, description quality, and reference structure, and to report actionable findings with replacement text.

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 good SKILL.md description?

Write one third-person English routing sentence naming the task and key technology, usually 8-16 words and under 160 characters. Front-load the identifying nouns because hosts may truncate listings, and keep capability lists and procedures in the body instead.

How do I test whether an Agent Skill actually works?

Create at least three evaluation scenarios with observable expected behaviors, including one near-miss negative that should not trigger the skill. Run each scenario with and without the skill, grade each expectation against transcript evidence, and require at least one baseline failure the skill closes.

What are the naming rules for an Agent Skill?

The name must be 1-64 characters of lowercase letters, digits, and single hyphens, with no leading, trailing, or doubled hyphens, no XML tags, and no vendor reserved words. It must exactly match the directory containing SKILL.md, since hosts derive skill identity from that directory.

Why is my skill never triggered by the agent?

Undertriggering usually comes from a vague or first-person description, or from relying on host-specific frontmatter fields that other hosts ignore. Measure trigger rates with roughly twenty realistic queries including near-miss negatives, and score candidate descriptions on a held-out split.

Can I use Claude Code frontmatter fields in a portable skill?

No. Fields like when_to_use, paths, disallowed-tools, and hooks are host-specific and ignored elsewhere, leaving activation unhandled. Portable skills use only the six specification fields: name, description, license, compatibility, metadata, and allowed-tools.

When should a skill bundle a script instead of instructions?

Bundle a script only after transcripts show runs repeatedly rewriting the same code. The script must solve rather than defer, declare its dependencies, contain no unexplained constants, and be labelled Run or See in SKILL.md.