create-agent-skills

Draft and validate OpenCode skills with proper frontmatter and routing.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/fro-bot/systematic --skill create-agent-skills-fro-bot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-agent-skills
Source: https://github.com/fro-bot/systematic/tree/main/components/create-agent-skills
Command: npx skills add https://github.com/fro-bot/systematic --skill create-agent-skills-fro-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OpenCode skills and slash commands often suffer from inconsistent structure and unclear discovery. This guide provides expert guidance for authoring new skills, improving existing ones, creating slash commands, and aligning with the official skill specification.

Core Features & Use Cases

  • Step-by-step patterns for turning ideas into skill directories (SKILL.md + optional workflows, references, and assets).
  • Frontmatter-driven discovery, router vs single-file patterns, and progressive disclosure for maintainable skills.
  • Guidance on evaluating and auditing skills for best practices and compliance across teams.

Quick Start

Write a new skill by following the standard SKILL.md format, including name/description frontmatter, an inline objective, quick_start, and success criteria.

Frequently Asked Questions about create-agent-skills

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

FAQPage Schema
How do I structure an OpenCode skill directory for reliable AI workflows?

Structure an OpenCode skill directory by creating a SKILL.md file with name and description frontmatter, an inline objective, quick_start, and success criteria. You can add optional workflows, references, and assets to support progressive disclosure and maintainable AI-driven workflows.

What is progressive disclosure in skill authoring and when should I use it?

Progressive disclosure in skill authoring is the practice of revealing complexity incrementally through frontmatter-driven discovery and explicit reference routing. Use it to maintain scalable, maintainable skills that guide AI without overwhelming the core SKILL.md with excessive inline content.

How do I validate frontmatter correctness for OpenCode skills?

Validate frontmatter correctness for OpenCode skills by auditing the SKILL.md file against the official specification. Ensure name and description fields are present and accurate, enabling proper discovery and compliance across teams for reliable AI execution.

When should I use a router pattern vs a single-file pattern for slash commands?

Use a router pattern for slash commands when managing complex skills requiring explicit reference routing and multiple workflows. Use a single-file pattern for simpler skills where a straightforward SKILL.md with inline objectives and quick_start instructions suffices for the AI workflow.

Does this skill authoring guide work for auditing existing skills across teams?

Yes, this skill authoring guide works for auditing existing skills across teams. It provides best practices for evaluating frontmatter correctness, progressive disclosure, and official specification compliance to ensure reliable AI-driven workflows and maintainable skill directories.

What are the limitations of using XML-structure in OpenCode skill references?

XML-structure in OpenCode skill references requires strict adherence to the official specification to avoid parsing errors. Limitations include potential verbosity and rigid formatting constraints, meaning you should carefully balance explicit reference routing with progressive disclosure for optimal AI comprehension.