create-skill

Creates OTTO skills with SKILL.md frontmatter and router patterns.

Updated May 25, 2026
One-click install
npx skills add https://github.com/cmetech/otto-cli --skill create-skill-cmetech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/cmetech/otto-cli/tree/main/src/resources/skills/create-skill
Command: npx skills add https://github.com/cmetech/otto-cli --skill create-skill-cmetech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates clear, scalable OTTO skills by teaching how to author SKILL.md, structure router patterns, and organize workflows, references, and scripts effectively.

Core Features & Use Cases

  • Instructs on turning unstructured skill ideas into a clean, maintainable router-based skill
  • Documents best practices for progressive disclosure, validation, and discovery across OTTO skills
  • Provides a blueprint for converting simple skills into router patterns and for adding workflows, references, and templates

Quick Start

Draft a router-based SKILL.md with intake and routing, then scaffold workflows and references in the new skill directory.

Frequently Asked Questions about create-skill

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

FAQPage Schema
How do I structure an OTTO skill using a router pattern?

A router pattern in OTTO skills structures SKILL.md into intake and routing logic that directs workflows and references, enforcing progressive disclosure and XML body structure for scalable architecture.

What is the best way to write YAML frontmatter for SKILL.md files?

The best way to write YAML frontmatter for SKILL.md is to enforce best practices for validation and discovery, ensuring structured metadata that supports scalable skill architecture and router patterns.

How do I convert unstructured skill ideas into maintainable OTTO workflows?

Convert unstructured skill ideas into maintainable OTTO workflows by applying a router pattern blueprint, scaffolding workflows and references, and organizing templates effectively within the skill directory.

When do I need progressive disclosure in skill creation?

You need progressive disclosure in skill creation when structuring complex OTTO skills, ensuring the XML body and router pattern expose workflows and references progressively to maintain scalability.

Does building router-based skills require existing templates and references?

Building router-based skills uses templates and references as core components, providing blueprints to scaffold workflows and document best practices for SKILL.md frontmatter and XML body structure.