writing-skills

Develop and document skills using Test-Driven Development principles.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/pxlcrtiv/opencode-setup --skill writing-skills-pxlcrtiv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/pxlcrtiv/opencode-setup/tree/main/skills/writing-skills
Command: npx skills add https://github.com/pxlcrtiv/opencode-setup --skill writing-skills-pxlcrtiv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in creating and documenting skills using Test-Driven Development (TDD) principles, ensuring that skills are clear, effective, and resistant to rationalization.

Core Features & Use Cases

  • Test-Driven Documentation: Develop documentation through the TDD cycle, writing failing tests first and then writing the skill that passes the test.
  • Skill Discovery Optimization: Enhance the discoverability of skills by using concise descriptions, rich keywords, and structured file organization.
  • Bulletproofing Against Rationalization: Learn how to design skills that resist rationalization and ensure compliance under pressure.

Quick Start

To create a new skill, follow the TDD cycle: write a failing test, write the skill to pass the test, and then refactor the skill to close any loopholes.

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 principles to write and document a new skill?

To create a skill using TDD, you write a failing test first, develop the skill to pass the test, and refactor to close loopholes, ensuring clear and effective documentation resistant to rationalization.

How can I optimize skill discovery and ensure compliance under pressure?

You optimize skill discovery by using concise descriptions, rich keywords, and structured file organization, while bulletproofing the design against rationalization to maintain compliance under pressure.

What is test-driven documentation and when do I need it for skill creation?

Test-driven documentation is developing skill docs through the TDD cycle to ensure clarity and effectiveness. You need it when creating skills that must resist rationalization and maintain strict compliance.

What is the best way to bulletproof a skill against rationalization?

The best way to bulletproof a skill against rationalization is designing it via TDD principles, writing tests first to expose loopholes, and refactoring the skill to ensure strict compliance and effectiveness.

Do I need any external dependencies to develop skills using test-driven development?

No external dependencies are required. The skill relies on internal scripts and references to guide the TDD cycle for skill creation, documentation, and optimization.