writing-skills

Create and validate SKILL.md files with YAML frontmatter for name and description.

Updated May 19, 2026
One-click install
npx skills add https://github.com/costrict-plugins-repo/anthropic-superpowers --skill writing-skills-costrict-plugins-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/costrict-plugins-repo/anthropic-superpowers/tree/main/skills/writing-skills
Command: npx skills add https://github.com/costrict-plugins-repo/anthropic-superpowers --skill writing-skills-costrict-plugins-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing well-structured Skill documentation is hard without a standardized entry point. This guide helps teams create repeatable, frontmatter-driven SKILL.md files that agents can discover and load reliably.

Core Features & Use Cases

  • Enforces a single entry point: SKILL.md that contains mandatory YAML frontmatter with name and description.
  • Supports optional resources (scripts/, references/, assets/) for on-demand loading.
  • Guides the authoring process from initial drafting to testing and deployment, ensuring consistency across Skills.

Quick Start

Draft a new Skill named 'my-skill' with proper frontmatter and a concise guide.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write SKILL.md documentation with frontmatter for agent discovery?

Use this guide to draft a new Skill by creating a SKILL.md file with mandatory YAML frontmatter specifying name and description. This standardized entry point enables agents to reliably discover and load your Skill.

What is frontmatter-driven skill documentation and when do I need it?

Frontmatter-driven skill documentation uses a SKILL.md entry point with mandatory YAML metadata for name and description. You need it when adding or modifying Skills to ensure agents can reliably discover and load them across a searchable namespace.

How to structure a Skill directory with scripts, references, and assets?

Structure your Skill directory by creating a SKILL.md entry point with YAML frontmatter, then add optional scripts/, references/, and assets/ subdirectories. These support on-demand loading of supplementary resources during skill execution.

Can I use optional directories for on-demand loading in my Skill?

Yes, you can use optional scripts/, references/, and assets/ directories for on-demand loading within your Skill. These directories sit alongside the mandatory SKILL.md file and provide supplementary resources when the Skill is invoked.

What's the best way to validate Skill documentation before deployment?

The best way to validate Skill documentation before deployment is to verify that your SKILL.md file contains mandatory YAML frontmatter with name and description fields. This guide walks you through the authoring process from initial drafting to testing and deployment.

Why does my Skill fail agent discovery without proper YAML frontmatter?

Your Skill fails agent discovery without proper YAML frontmatter because the searchable namespace requires a standardized SKILL.md entry point containing mandatory name and description metadata. Without these fields, agents cannot reliably identify or load your Skill.