writing-skills

Enforce Test-Driven Development for creating and updating AI skills.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/HsnSaboor/open-engineer --skill writing-skills-hsnsaboor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/HsnSaboor/open-engineer/tree/main/src/skills/bundled/obra-writing-skills
Command: npx skills add https://github.com/HsnSaboor/open-engineer --skill writing-skills-hsnsaboor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that new and updated skills are robust, well-documented, and effectively guide AI agents by applying Test-Driven Development (TDD) principles to the skill creation process.

Core Features & Use Cases

  • TDD for Documentation: Adapts the RED-GREEN-REFACTOR cycle to writing and verifying skills.
  • Bulletproofing Skills: Provides strategies to close loopholes and prevent AI rationalizations against skill compliance.
  • Use Case: When developing a new skill for handling complex API error codes, use this skill to first write test scenarios that demonstrate an AI failing to interpret those errors, then write the skill to correct the behavior, and finally refactor to ensure it handles all edge cases.

Quick Start

Use the writing-skills skill to create a new skill document following TDD principles.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I apply Test-Driven Development to AI agent training and skill creation?

Test-Driven Development for AI agent training mandates writing a failing test scenario before skill implementation, then refactoring the skill documentation to close loopholes and verify compliance.

What is the best way to write process documentation that prevents AI rationalizations?

Writing process documentation to prevent AI rationalizations requires applying TDD refactoring strategies to close loopholes, ensuring the skill documentation effectively guides the AI agent against bypassing rules.

How does the RED-GREEN-REFACTOR cycle work for writing and verifying skills?

The RED-GREEN-REFACTOR cycle for writing skills maps to creating a failing test scenario demonstrating an AI error, writing the skill to correct the behavior, and refactoring to handle edge cases.

Why do I need a failing test before implementing an AI skill?

A failing test before implementing an AI skill proves the documentation is necessary by demonstrating the agent's current failure to interpret specific scenarios, ensuring robust quality assurance from the start.

Can I use TDD to bulletproof existing skill documentation against edge cases?

Yes, you can use TDD to bulletproof existing skill documentation by writing test scenarios for edge cases, updating the skill to pass them, and refactoring to prevent agent rationalizations against compliance.

What are the limitations of using TDD for skill development?

Using TDD for skill development requires strict adherence to specific TDD mapping for skill creation and verifying against agent rationalizations, which may increase the initial time needed for process documentation.