skill-writer

Create and validate Agent Skills with SKILL.md frontmatter and structure.

2|2|Updated Apr 7, 2013
One-click install
npx skills add https://github.com/warpcode/dotfiles --skill skill-writer-warpcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-writer
Source: https://github.com/warpcode/dotfiles/tree/main/generic/.config/opencode/skills/skill-writer
Command: npx skills add https://github.com/warpcode/dotfiles --skill skill-writer-warpcode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides the creation and validation of Agent Skills for Claude Code and opencode, including SKILL.md frontmatter, structure, and references.

Core Features & Use Cases

  • Templates for skill structure, frontmatter, and documentation.
  • Validation guidance and packaging workflows for skills.
  • Progressive disclosure and reference integration to keep skills lean.

Quick Start

Initialize a new skill using the standard SKILL.md template and references.

Frequently Asked Questions about skill-writer

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

FAQPage Schema
How do I create a new Claude Skill with proper SKILL.md structure?

Design a Skill by writing SKILL.md with YAML frontmatter (name and description), a concise body following progressive disclosure, optional references, and assets. Use the standard init and package scripts to validate structure and prepare for deployment.

What should I include in a Skill's frontmatter and documentation?

Frontmatter requires name and description fields in YAML format. Documentation body must stay lean using progressive disclosure—core task first, then details. References and assets integrate separately to keep the main document focused and scannable.

How do I convert an existing prompt or workflow into a Skill?

Break down your prompt or workflow into a structured Skill by identifying the core task, defining inputs and outputs, writing clear SKILL.md documentation with frontmatter, and packaging it with init and package scripts following standard Skill conventions.

Can I validate my Skill before packaging and deployment?

Yes. Validation checks that YAML frontmatter contains required name and description fields, SKILL.md structure follows progressive disclosure, references are properly integrated, and all files meet packaging standards before running the package script.

What are the common issues with Skill discovery and how do I fix them?

Skill discovery relies on clear frontmatter, descriptive names, and proper documentation structure. Troubleshoot by verifying frontmatter completeness, ensuring SKILL.md conciseness without jargon, checking reference formatting, and confirming the standard packaging steps completed successfully.