use-skill-create

Create and edit Skills using the RED-GREEN-REFACTOR cycle with YAML frontmatter.

1|Updated Jan 9, 2026

Search Tags:#tdd #documentation #quality-assurance #process #frontmatter #skill-creation #progressive-disclosure

Ready to run

npx skills add https://github.com/mtthsnc/autonome --skill use-skill-create

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: use-skill-create
Source: https://github.com/mtthsnc/autonome/tree/main/skills/use-skill-create
Command: npx skills add https://github.com/mtthsnc/autonome --skill use-skill-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a rigorous, repeatable approach to Skill authoring that prevents vague guidance and ensures test-driven validation.

Core Features & Use Cases

Enforces RED-GREEN-REFACTOR as the standard workflow for creating and updating Skills.
Requires YAML frontmatter with only name and description, ensuring concise discovery.
Enables optional components (scripts, references, assets) to bundle supporting materials without loading all content by default.

Quick Start

Follow the RED-GREEN-REFACTOR cycle to draft, test, and refine a Skill.

Frequently Asked Questions about use-skill-create

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

FAQPage Schema

How do I create Skills using test-driven development?▼

To create Skills using test-driven development, follow the enforced RED-GREEN-REFACTOR cycle to draft, test, and refine Skill content iteratively. This approach ensures test-driven validation and prevents vague guidance during Skill authoring.

What is progressive-disclosure guidance in Skill creation?▼

Progressive-disclosure guidance in Skill creation is a design approach that enables optional components like scripts, references, and assets to bundle supporting materials without loading all content by default. This keeps Skill discovery concise.

How do I structure YAML frontmatter for a new Skill?▼

To structure YAML frontmatter for a new Skill, include only the required name and description fields. This enforced constraint ensures concise discovery metadata and prevents overloaded frontmatter configurations.

Does this Skill creation process support adding optional components?▼

Yes, the Skill creation process supports adding optional components for scripts, references, and assets. These components bundle supporting materials alongside the core Skill without forcing default content loading.

What's the best way to verify Skills work before deployment?▼

The best way to verify Skills work before deployment is by applying the RED-GREEN-REFACTOR cycle and running built-in safety checks. This disciplined workflow validates functionality and catches structural errors early.

Why does my Skill creation workflow need quality-assurance checks?▼

Your Skill creation workflow needs quality-assurance checks to prevent vague guidance and ensure rigorous, repeatable Skill authoring. Applying safety checks enforces structural integrity and validates test-driven discipline.