skills.rest
jordanhindo
jordanhindoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-skills

Create and verify agent Skill documentation with a RED-GREEN-REFACTOR test-driven process.

4|1|Updated Jan 22, 2026
Search Tags:#process documentation#test-driven development#skill authoring#skill discovery#agent compliance#rationalization loopholes
One-click install
npx skills add https://github.com/jordanhindo/Turtlez --skill writing-skills-jordanhindo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/jordanhindo/Turtlez/tree/main/.claude/skills/writing-skills
Command: npx skills add https://github.com/jordanhindo/Turtlez --skill writing-skills-jordanhindo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps agents create and edit Skill documentation reliably by enforcing a test-driven loop that prevents rationalized, “it seems obvious” compliance failures.

Core Features & Use Cases

  • TDD for documentation: maps RED-GREEN-REFACTOR to skill-authorship so the Skill is proven under pressure, not assumed correct.
  • Discovery-optimized SKILL.md: requires YAML frontmatter (name, description) and strongly guides how to write descriptions that trigger proper loading.
  • Bulletproofing against loopholes: captures baseline rationalizations verbatim and adds explicit negations, red flags, and re-verification steps.
  • Structured testing with pressure scenarios: uses multi-pressure “pressure scenario with subagent” patterns (time, authority, sunk cost, exhaustion) to validate real compliance.

Quick Start

Use writing-skills when creating or updating a Skill and you need proof it works before deployment.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write process documentation that agents follow under pressure?▼

Use a test-driven development loop for process documentation that maps RED-GREEN-REFACTOR to skill authoring, verifying agent compliance under multi-pressure scenarios like time, authority, and sunk cost.

What is test-driven development for skill authoring?▼

Test-driven skill authoring applies RED-GREEN-REFACTOR to documentation creation, requiring baseline failure observation and iterative loophole closure to prevent rationalized non-compliance before deployment.

How do I prevent rationalization loopholes in agent documentation?▼

Capture baseline rationalizations verbatim and add explicit negations, red flags, and re-verification steps to close loopholes, ensuring agents follow discipline-like rules under pressure.

How do I format SKILL.md frontmatter for proper skill discovery?▼

Include YAML frontmatter with name and description fields in SKILL.md, writing descriptions that trigger proper loading and optimize the skill for agent discovery.

When should I use a test-driven approach for documentation?▼

Apply test-driven documentation when creating or updating a Skill and you need proof it works before deployment, using structured testing with subagent pressure scenarios to validate real compliance.

Related Skills

Explore More Content & Communication Skills→
axiomanticaxiomantic
8

writing-skills

Write and validate Skill documentation using a RED-GREEN-REFACTOR workflow.

Official
Advanced
KanuToCLKanuToCL

testing-skills-with-subagents

Test AI agent skills using Red-Green-Refactor and pressure simulations.

Community
Advanced
haojing8312haojing8312
154

writing-skills

Create, edit, and validate Claude skills with test-driven development.

Community
Advanced
samjhechtsamjhecht
4

writing-skills

Apply test-driven development to SKILL.md documentation and validate skill robustness.

Community
Basic