creating-skills

Create reusable Agent Skills with SKILL.md frontmatter and directory structure.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/datorresb/vibecoding-starter --skill creating-skills-datorresb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-skills
Source: https://github.com/datorresb/vibecoding-starter/tree/main/.claude/skills/core/creating-skills
Command: npx skills add https://github.com/datorresb/vibecoding-starter --skill creating-skills-datorresb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams standardize the creation of reusable Agent Skills by providing a clear blueprint for SKILL.md frontmatter and the accompanying Markdown body, ensuring consistency across the catalog.

Core Features & Use Cases

  • Structured metadata: Enforces a mandatory YAML frontmatter with name and description and optional fields like license, compatibility, and metadata.
  • Guided skill blueprint: Outlines the required directory structure (skill-name/ with SKILL.md) and optional resources (scripts/, references/, assets/).
  • Reuse and extension: Supports applying the open standard when authoring new skills or updating existing ones, enabling easy sharing and cataloging.

Quick Start

Create a new skill folder named my-skill under the root skills/ directory, add a SKILL.md with proper frontmatter and content, then optionally add scripts/, references/, or assets/ as needed to support your skill.

Frequently Asked Questions about creating-skills

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

FAQPage Schema
How do I structure a reusable AI agent skill for consistent cataloging?

To structure a reusable AI agent skill, create a root directory named after your skill containing a mandatory SKILL.md file with YAML frontmatter, and optionally add scripts, references, and assets folders to support its functionality.

What metadata is required in a SKILL.md frontmatter file?

A SKILL.md frontmatter file requires name and description fields as mandatory metadata, while optional fields include license, compatibility, and additional metadata to ensure proper skill documentation and reuse.

How does the open standard format work for authoring agent skills?

The open standard format for authoring agent skills works by enforcing a standardized directory structure and YAML frontmatter validation within SKILL.md, ensuring consistent naming, metadata compliance, and reusable skill lifecycle management across catalogs.

Can I update existing agent skills using this blueprint instead of creating new ones?

Yes, you can update existing agent skills using this blueprint by applying the open standard to validate their SKILL.md frontmatter and directory structure, ensuring they meet the consistency requirements for sharing and cataloging.

What's the best way to organize scripts and references when creating an agent skill?

The best way to organize scripts and references when creating an agent skill is to place them in dedicated optional directories alongside your SKILL.md file, separating executable logic and supporting documentation from the skill's main metadata.

Do I need any specific dependencies to create a skill using the open standard?

No specific dependencies are required to create a skill using the open standard; you only need to define a SKILL.md file with the mandatory name and description frontmatter fields within a properly named directory structure.