write-a-skill

Create agent skills with SKILL.md frontmatter and structured directories.

6.3k|548|Updated Jan 18, 2017
One-click install
npx skills add https://github.com/sanity-io/sanity --skill write-a-skill-sanity-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-skill
Source: https://github.com/sanity-io/sanity/tree/main/.agents/skills/write-a-skill
Command: npx skills add https://github.com/sanity-io/sanity --skill write-a-skill-sanity-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to creating new agent skills with a consistent format, frontmatter, and optional resources, reducing ambiguity and setup time.

Core Features & Use Cases

  • Enforces a minimal SKILL.md with name and description, a descriptive workflow, and optional references, scripts, or assets.
  • Defines a clear structure for skill directories (skill-name/, SKILL.md, optional REFERENCE.md, EXAMPLES.md, scripts/, references/, assets/).
  • Guides rapid creation and review by outlining steps from drafting to review with a concise template.

Quick Start

Create a new skill by defining SKILL.md with frontmatter and a concise workflow.

Frequently Asked Questions about write-a-skill

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

FAQPage Schema
How do I create agent skills with proper markdown structure and frontmatter?

To structure agent skills, start by drafting a SKILL.md file with required frontmatter fields for name and description, write a concise markdown workflow body, add optional reference or script folders, and finish with a review to ensure consistent skill directory formatting.

What is the required directory structure for building agent skills?

The required directory structure for building agent skills uses a root skill-name/ folder containing a SKILL.md file, alongside optional REFERENCE.md, EXAMPLES.md, scripts/, references/, and assets/ directories to separate instructions from bundled resources.

Do I need external dependencies to generate skill definitions with markdown?

You do not need external dependencies to generate skill definitions with markdown. The skill operates with zero dependencies, relying only on standard markdown files and YAML frontmatter to establish the required structure and workflow.

What's the best way to maintain consistency across multiple agent skill definitions?

The best way to maintain consistency across multiple agent skill definitions is to enforce a standardized skill directory layout using a SKILL.md template with mandatory frontmatter, structured markdown workflows, and optional bundled resource folders for every new skill.

Can I bundle scripts and reference assets directly within my agent skills?

Yes, you can bundle scripts and reference assets directly within your agent skills by utilizing the optional scripts/, references/, and assets/ folders defined within the standard skill directory structure to support progressive disclosure.

Why does my agent skill require a specific markdown frontmatter format?

Your agent skill requires a specific markdown frontmatter format to ensure the agent can parse the name and description metadata correctly, enabling proper progressive disclosure and reducing ambiguity during skill setup and execution.