writing-skills

Guide TDD-based writing and validation of skill documentation with rationalization tracking.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/juanjaragavi/topfinanzas-us-next --skill writing-skills-juanjaragavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/juanjaragavi/topfinanzas-us-next/tree/main/.agents/skills/writing-skills
Command: npx skills add https://github.com/juanjaragavi/topfinanzas-us-next --skill writing-skills-juanjaragavi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide enables a test-driven approach to writing, editing, and validating Skill units to ensure reliable, reusable documentation under pressure.

Core Features & Use Cases

  • Reusable techniques, patterns, or tools for skill documentation
  • Provides RED-GREEN-REFACTOR workflow for skill creation, plus rationalization tracking
  • Supports progressive disclosure and Claude discovery optimization
  • Encourages concise frontmatter and structured content for quick loading
  • Includes methodologies for testing and iteration

Quick Start

Draft a baseline pressure scenario without the skill, then implement the skill and retest to verify compliance.

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 skill documentation?▼

Test-driven skill documentation drafts a baseline pressure scenario without the skill, then implements the skill and retests to verify compliance. This RED-GREEN-REFACTOR workflow ensures reliable, reusable skill behavior under pressure.

What is the best way to structure SKILL.md entries for Claude discovery?▼

Structuring SKILL.md entries for Claude discovery requires YAML frontmatter with a concise name and description. Progressive disclosure structures content for quick loading, ensuring the skill is easily found and validated.

How does rationalization tracking work when editing existing skills?▼

Rationalization tracking monitors logic changes during skill editing to maintain reliable documentation. It guides baseline testing and validation workflows to ensure skill behavior remains consistent under pressure.

Can I apply subagent testing workflows to validate skill behavior under pressure?▼

Yes, subagent testing workflows validate skill behavior under pressure by applying baseline pressure scenarios. This testing methodology ensures skill documentation remains reliable and reusable during iteration.

Do I need prior testing skills to create new skills using progressive disclosure?▼

No prior testing skills are required, but understanding baseline testing helps. The workflow provides a quick start guide to draft pressure scenarios, implement the skill, and verify compliance through structured iteration.

Why does skill documentation fail Claude discovery without concise frontmatter?▼

Skill documentation fails Claude discovery without concise frontmatter because missing or verbose YAML name and description fields prevent quick loading. Progressive disclosure requires structured content to ensure reliable skill validation.