writing-skills

Guide AI skill creation through RED-GREEN-REFACTOR cycles and loophole closure.

58|6|Updated Jan 20, 2026

Search Tags:#skill development #testing #tdd #documentation #rationalization #ai skills

Ready to run

npx skills add https://github.com/barretstorck/gemini-superpowers --skill writing-skills-barretstorck

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/barretstorck/gemini-superpowers/tree/main/skills/writing-skills
Command: npx skills add https://github.com/barretstorck/gemini-superpowers --skill writing-skills-barretstorck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigorous, test-driven framework for creating and refining AI Skills, ensuring they are effective, discoverable, and robust against common pitfalls.

Core Features & Use Cases

Test-Driven Skill Development: Apply the RED-GREEN-REFACTOR cycle to skill creation and editing.
Rationalization Countermeasures: Explicitly address and prevent AI agents from bypassing skill rules through logical loopholes or excuses.
Use Case: You need to create a new Skill for your team that enforces a specific coding standard. Use this Skill to guide the creation process, ensuring the new Skill is well-defined, tested against potential violations, and clearly documented.

Quick Start

Follow the RED-GREEN-REFACTOR process outlined in this skill to create a new skill.

Frequently Asked Questions about writing-skills

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

FAQPage Schema

How do I use test-driven development for AI skill creation?▼

Test-driven AI skill development applies the RED-GREEN-REFACTOR cycle to guide creation and editing, ensuring the resulting skill is well-defined, tested against potential violations, and clearly documented.

What is rationalization in AI skills and how do I prevent it?▼

Rationalization occurs when AI agents bypass skill rules through logical loopholes. You prevent it by applying explicit rationalization countermeasures and pressure testing during development to close loopholes and enforce skill integrity.

What's the best way to enforce a coding standard for my development team?▼

Use a test-driven framework to guide skill creation, ensuring the new skill enforcing the coding standard is well-defined, tested against potential violations, and clearly documented for your team.

How does the RED-GREEN-REFACTOR cycle work when writing AI skills?▼

The RED-GREEN-REFACTOR cycle guides AI skill creation by writing a failing test for behavior first (RED), making it pass (GREEN), then refining documentation and logic (REFACTOR) to ensure discoverability and robustness.

Do I need any dependencies to start writing better skills faster?▼

No dependencies are required to start writing better skills faster. The framework operates independently using its internal references to guide you through pressure testing and loophole closure for skill integrity.

When should I pressure test an AI skill during development?▼

You should pressure test an AI skill during the REFACTOR phase of development. This ensures the skill is resistant to common pitfalls, robust against edge cases, and completely closed to logical loopholes.