writing-skills

Author and validate Skills using test-driven red-green-refactor cycles.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/Suara17/guanlan-sina --skill writing-skills-suara17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Suara17/guanlan-sina/tree/main/.opencode/skills/writing-skills
Command: npx skills add https://github.com/Suara17/guanlan-sina --skill writing-skills-suara17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined approach to writing and validating Skills, ensuring documentation reflects real failure modes observed under pressure and is resistant to rationalization.

Core Features & Use Cases

  • TDD-style Skill creation workflow (RED-GREEN-REFACTOR) with baseline tests, rationalization tracking, and red flags
  • YAML frontmatter validation and lightweight structure to optimize discovery and loading
  • Guidance for documenting triggering conditions, failure rationalizations, and verification steps
  • Support for progressive disclosure: link to heavy references or scripts only when needed
  • Encourages concise naming, consistent terminology, and explicit dependencies when applicable

Quick Start

Create a new Skill by adding SKILL.md with frontmatter name and description, then build a concise body that documents when to use the Skill and how to test it.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I use TDD to write and validate Claude skills?

Test-driven skill writing applies a red-green-refactor cycle to author and validate Skills, ensuring documentation reflects observed failures. You create baseline tests, track rationalizations, and enforce YAML frontmatter constraints for optimized discovery.

What is rationalization tracking in skill documentation?

Rationalization tracking monitors how documentation explains away observed failures across baseline and verification stages. It ensures your skill documentation remains resistant to rationalization and accurately reflects real failure modes under pressure.

How do I structure YAML frontmatter to optimize skill discovery?

Optimizing skill discovery requires enforcing YAML frontmatter constraints with concise naming and trigger-focused descriptions. This lightweight structure minimizes token load and improves loading efficiency.

When should I use progressive disclosure in skill documentation?

Use progressive disclosure when your skill requires heavy references or scripts. Link to these external resources only when needed to keep the core documentation concise and reduce token load during skill execution.

Does the TDD workflow for skill writing require external dependencies?

The TDD workflow for skill writing operates without external dependencies. You only need to create a SKILL.md file with the required frontmatter and a concise body documenting when to use the skill and how to test it.

How do I document triggering conditions for a new skill?

Document triggering conditions by writing a concise skill body that explicitly defines when to use the skill and how to test it. This trigger-focused description approach optimizes discovery and ensures proper activation.