{skill-name}

Standardize Skill unit structure with YAML frontmatter and Markdown body.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/rett-europe/opentreasury --skill skill-name-rett-europe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: {skill-name}
Source: https://github.com/rett-europe/opentreasury/tree/main/.squad
Command: npx skills add https://github.com/rett-europe/opentreasury --skill skill-name-rett-europe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes the creation and discovery of Skill units by enforcing a YAML frontmatter surface and a structured Markdown body that loads into context on activation.

Core Features & Use Cases

  • Enforces a mandatory SKILL.md frontmatter with name and description for discovery.
  • Supports optional resource directories (scripts/, references/, assets/) that are loaded on demand.
  • Provides a consistent template for skill definitions used by Squad tooling and automation.

Quick Start

Create a new Skill by adding a SKILL.md at the root with a valid YAML frontmatter and a descriptive Markdown body.

Frequently Asked Questions about {skill-name}

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

FAQPage Schema
How do I standardize YAML frontmatter for documentation templates?

You standardize YAML frontmatter by defining a mandatory SKILL.md surface with name and description fields, enabling tooling to discover, load, and activate the documentation unit consistently.

What is the required metadata structure for a Skill unit?

The required metadata structure for a Skill unit consists of a SKILL.md file at the root containing valid YAML frontmatter for discovery and a structured Markdown body that loads into context on activation.

How do I set up optional resource directories for a Markdown template?

Set up optional resource directories by creating scripts, references, and assets folders alongside the SKILL.md file, which the tooling loads on demand during runtime rather than at activation.

Can I use this template to prevent unsafe content in skill definitions?

You can use this template to prevent unsafe content by following its concrete guidance and examples, which ensure consistent metadata and standardize the Markdown body loaded at runtime.

What's the best way to create a discoverable skill definition for automation tooling?

The best way to create a discoverable skill definition is adding a SKILL.md at the root with valid YAML frontmatter and a descriptive Markdown body, ensuring Squad tooling and automation can discover it.