skill-author

Create standardized Agent Skills with SKILL.md and YAML frontmatter.

39|6|Updated Nov 7, 2025

Search Tags:#gemini #guidelines #yaml-frontmatter #agent-skills #skill-authoring #modular-skills

Ready to run

npx skills add https://github.com/ddobrin/gemini-plan-commands --skill skill-author-ddobrin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-author
Source: https://github.com/ddobrin/gemini-plan-commands/tree/main/skills/skills-author
Command: npx skills add https://github.com/ddobrin/gemini-plan-commands --skill skill-author-ddobrin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authoring Agent Skills in a standardized, open framework so teams can create, share, and reuse capabilities with predictable structure and metadata.

Core Features & Use Cases

Establishes a consistent folder and frontmatter pattern for all skills.
Encourages separation of executable logic (scripts) and supporting references/assets.
Supports discovery and governance by modeling metadata and usage patterns.

Quick Start

Create a new skill folder, add a root SKILL.md with valid YAML frontmatter, and place any scripts or references as needed.

Frequently Asked Questions about skill-author

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

FAQPage Schema

How do I structure YAML frontmatter when authoring agent skills?▼

Authoring agent skills requires a root SKILL.md file with valid YAML frontmatter that includes a name and description to ensure predictable structure and metadata for discovery. Optional directories like scripts, references, and assets can be added.

What is the standard folder structure for creating modular agent skills?▼

The standard folder structure for modular agent skills uses a root SKILL.md file, with optional scripts/ for executable logic, references/ for supporting documents, and assets/ directories to separate code from supporting materials.

How do I separate executable logic from references when building agent capabilities?▼

You separate executable logic from references by placing code in the scripts/ directory and supporting materials in the references/ and assets/ directories, while the root SKILL.md with YAML frontmatter governs metadata.

Do I need any dependencies to create standardized agent skills?▼

No dependencies are required to create standardized agent skills. The open standard only requires a root SKILL.md file with valid YAML frontmatter containing a name and description to define the capability.

What's the best way to standardize agent skill metadata for team reuse?▼

Standardizing agent skill metadata for team reuse is best achieved by following an open framework that models usage patterns and metadata in the root SKILL.md YAML frontmatter, ensuring capabilities are shareable and discoverable.

When should I include optional scripts and assets directories in my agent skill?▼

You should include optional scripts/ and assets/ directories in your agent skill when you need to separate executable logic or attach supporting resources, keeping the root SKILL.md focused on frontmatter metadata.