Agent skill · magnus919
agent-skills
Use this skill when creating, reviewing, or editing Agent Skills-format skills, or when implementing skill discovery and loading in an agent client. It covers directory structure, SKILL.md metadata, progressive disclosure, evals, and repository conventions. Do not use this skill for general software work that does not involve the Agent Skills format or lifecycle.
What it needs
About 7k tokens when loaded.
What this skill does
Agent Skills Standard Reference This skill documents the Agent Skills open format — a standardized way to give AI agents new capabilities and expertise. Follow this workflow when creating or editing skills in this repository. Authoritative source: agentskills.io/specification. The bundled specification is a working snapshot; check the authoritative source when currentness matters. --- Directory Structure A skill is a directory containing, at minimum, a SKILL.md file: Required Workflow Create or edit a skill 1. Read the specification before changing SKILL.md metadata or directory structure. 2. Ground instructions in real domain knowledge, project artifacts, and observed failure modes. Read best practices when designing or materially revising instructions. 3. Keep the skill a coherent, triggerable unit. Put only essential instructions in SKILL.md; put conditional detail in focused reference files and state exactly when to read each one. 4. Use a precise description that says what the skill does, when it applies, and when it does not apply. For skills with meaningful overlap, name the nearest alternative or prerequisite in a ## When not to use section. Test the boundary with at least three should-trigger prompts and two should-not-trigger near-misses; keep these harness-specific trigger checks separate from portable output-quality evals. Read optimizing descriptions for trigger design. 5. For every new skill, create evals/evals.json with at least five representative output-quality cases. Each case needs a realistic prompt, an expected outcome, and observable assertions. Include edge cases that exercise risky or ambiguous behavior. Read evaluating skills for the eval format and iteration workflow. 6. When bundling executable code, read using scripts. Document prerequisites and non-interactive invocation in the skill. 7. Before handoff, run the validation checks in this skill and correct every finding. Review a skill 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/agent-skills--cb4cf9