write-a-skill

Create agent skills with SKILL.md frontmatter and optional resource directories.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yarma-tech/agent-admin-qonto --skill write-a-skill-yarma-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-skill
Source: https://github.com/yarma-tech/agent-admin-qonto/tree/main/.agents/skills/write-a-skill
Command: npx skills add https://github.com/yarma-tech/agent-admin-qonto --skill write-a-skill-yarma-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create new agent skills with proper structure, progressive disclosure, and bundled resources. This ensures every skill includes a mandatory SKILL.md frontmatter and a predictable layout for easy discovery and loading.

Core Features & Use Cases

  • Defines a minimal, self-contained skill unit with SKILL.md at root and optional scripts/references/assets directories.
  • Guides on when to split content, add scripts for deterministic tasks, and how to maintain a consistent structure across skills.
  • Useful for teams standardizing how new skills are authored and published.

Quick Start

Create SKILL.md with a name and description, then validate the unit against the official definition.

Frequently Asked Questions about write-a-skill

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

FAQPage Schema
How do I structure an agent skill with yaml frontmatter and resource directories?

To structure an agent skill, create a root SKILL.md file with mandatory yaml frontmatter fields like name and description, then add optional scripts, references, and assets directories to bundle related resources.

What is the standard layout for writing agent skills to ensure consistent discovery?

The standard layout for writing agent skills is a minimal, self-contained unit with a SKILL.md at the root and predictable directories for scripts and assets, ensuring consistent naming, progressive disclosure, and easy loading.

When should I split content or add scripts when building automation skills?

You should split content or add scripts when building automation skills to handle deterministic tasks, separating complex logic into scripts while keeping the SKILL.md focused on guidelines and progressive disclosure for maintainability.

Can I use this approach to standardize skill creation for a development team?

Yes, you can use this approach to standardize skill creation for a development team by enforcing required frontmatter fields and a predictable file structure across all new skills authored and published within your automation platform.

What are the limitations of using a minimal SKILL.md unit for agent documentation?

The limitation of using a minimal SKILL.md unit is that while it enforces required frontmatter for basic discovery, future extension with references, examples, and scripts requires manual setup of additional optional resource directories.