write-a-skill

Draft standardized skill directories with SKILL.md frontmatter and optional scaffolding.

12|1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/helderberto/skills --skill write-a-skill-helderberto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-skill
Source: https://github.com/helderberto/skills/tree/main/write-a-skill
Command: npx skills add https://github.com/helderberto/skills --skill write-a-skill-helderberto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Draft standardized skill directories to streamline creating new agent skills.

Core Features & Use Cases

  • Provides a ready-to-use SKILL.md frontmatter template with required fields
  • Encourages optional scaffolding like scripts/ for helpers and references/assets for documentation
  • Supports a repeatable workflow: draft, review, and validate

Quick Start

Create a new directory named write-a-skill with a SKILL.md frontmatter and an optional scripts/ folder for helpers.

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 a standardized template for new agent skills?

To create a standardized template for new agent skills, draft a directory with a SKILL.md file containing required frontmatter fields like name and description, then add optional folders for scripts and references to complete the structure.

What is included in an agent skill scaffolding directory?

An agent skill scaffolding directory includes a SKILL.md file with a frontmatter schema for metadata validation, alongside optional subdirectories for scripts, references, and assets to organize helper code and documentation.

How do I validate frontmatter fields when building a developer skill?

You validate frontmatter fields in a developer skill by ensuring the SKILL.md metadata schema requires essential attributes like name and description, applying a repeatable workflow to draft, review, and validate the content.

Do I need YAML frontmatter to structure a new CLI automation skill?

Yes, YAML frontmatter is needed to structure a new CLI automation skill because it defines the required name and description metadata fields that ensure the skill directory is properly recognized and validated.

What's the best way to scaffold optional scripts and references for agent skills?

The best way to scaffold optional scripts and references for agent skills is to create dedicated subdirectories within the main skill folder, separating helper logic in scripts from documentation in references and assets.

Why does my skill directory fail validation without a SKILL.md file?

Your skill directory fails validation without a SKILL.md file because the standard review and validation workflow requires this file to confirm that mandatory frontmatter fields like name and description are present.