skill-authoring

Standardize skill creation with YAML frontmatter and structured sections.

21|1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/z3z1ma/agent-loom --skill skill-authoring-z3z1ma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-authoring
Source: https://github.com/z3z1ma/agent-loom/tree/main/.opencode/skills/skill-authoring
Command: npx skills add https://github.com/z3z1ma/agent-loom --skill skill-authoring-z3z1ma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates clear, reusable skill units by enforcing a frontmatter contract and a structured body, preventing ambiguous or duplicate skills.

Core Features & Use Cases

  • Enforces mandatory frontmatter fields (name, description) and optional metadata like license and compatibility.
  • Guides on structuring skill bodies with purpose, preconditions, steps, examples, and gotchas for reusability.
  • Supports versioning and updating guidance to manage skill evolution across projects.

Quick Start

Create a new skill titled with a kebab-case name and provide a concise description following the required frontmatter rules.

Frequently Asked Questions about skill-authoring

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

FAQPage Schema
How do I standardize skill creation to prevent duplicates and vague definitions?

Standardize skill creation by enforcing a strict YAML frontmatter contract and structured body sections, preventing ambiguous or duplicate skill units across projects. This requires mandatory metadata validation and consistent kebab-case naming.

What is the best way to structure reusable skill bodies with preconditions and steps?

The best way to structure reusable skill bodies is to divide them into purpose, preconditions, steps, examples, and gotchas. This structured format guarantees clarity and long-term reusability for complex workflows.

What metadata is required in YAML frontmatter for skill authoring?

Required YAML frontmatter fields for skill authoring include name and description, alongside category and keywords. Optional metadata like license and compatibility can also be added to manage skill evolution.

When do I need frontmatter validation and naming rules for templates?

You need frontmatter validation and naming rules for templates when authoring new skills across multiple projects. This standardization prevents duplicates and ensures metadata requirements are consistently present and validated.

Does skill authoring support versioning and updating guidance for existing skills?

Yes, skill authoring supports versioning and updating guidance to manage skill evolution across projects. This ensures structured definitions remain durable and compatible as dependencies and components change over time.