writing-skills

Write and validate OpenCode Skills with SKILL.md frontmatter and TDD workflows.

34|6|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/Chikage0o0/opencode --skill writing-skills-chikage0o0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Chikage0o0/opencode/tree/main/skills/writing-skills
Command: npx skills add https://github.com/Chikage0o0/opencode --skill writing-skills-chikage0o0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a meta-guidance framework for authoring and validating other Skills within the OpenCode ecosystem, ensuring consistent quality, discoverability, and testability.

Core Features & Use Cases

  • Establishes consistent SKILL.md frontmatter (name + description) and a structured body that supports progressive disclosure.
  • Promotes TDD-inspired, RED-GREEN-REFACTOR workflows for Skill creation and verification.
  • Defines OSO-friendly discovery via concise, trigger-oriented description and cross-referenced documentation patterns.
  • Guides organization of references, scripts, and assets to keep Skills maintainable and scalable.
  • Enables rigorous deployment readiness checks before publishing or sharing Skills externally.

Quick Start

Read this SKILL.md and follow the RED-GREEN-REFACTOR process to author and test a new Skill.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write an OpenCode Skill that is easy to discover and use?

To write a discoverable OpenCode Skill, you establish consistent SKILL.md frontmatter with trigger-oriented descriptions and organize supporting references using progressive disclosure patterns for scalable structure.

What is the RED-GREEN-REFACTOR workflow for skill authoring?

The RED-GREEN-REFACTOR workflow is a TDD-inspired process for skill authoring that verifies readiness through testing, ensures safe deployment, and validates that your SKILL.md entry meets quality standards.

How should I structure SKILL.md frontmatter to ensure OSO-friendly discovery?

Structure SKILL.md frontmatter to ensure OSO-friendly discovery by including concise name and description fields with trigger-oriented keywords, enabling cross-referenced documentation patterns for reliable skill activation.

How do I validate a new Skill before deploying it to the OpenCode ecosystem?

Validate a new Skill before deployment by running rigorous readiness checks, verifying the SKILL.md body structure, and confirming that references, scripts, and assets are organized for maintainability.

When should I use progressive disclosure in Skill documentation?

Use progressive disclosure in Skill documentation to keep complex references and scripts maintainable, exposing core guidelines in SKILL.md while organizing deeper assets separately for scalable, bulletproof deployment.

Does OpenCode skill writing require external dependencies?

OpenCode skill writing requires no external dependencies, relying entirely on internal meta-guidance frameworks to enforce TDD-like verification, frontmatter consistency, and safe deployment readiness checks.