writing-skills

Applies RED-GREEN-REFACTOR cycle to author and maintain AI skills.

947|163|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/guanyang/antigravity-skills --skill writing-skills-guanyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/guanyang/antigravity-skills/tree/main/skills/writing-skills
Command: npx skills add https://github.com/guanyang/antigravity-skills --skill writing-skills-guanyang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that new and updated skills are robust, effective, and adhere to best practices by applying Test-Driven Development (TDD) principles to the skill authoring process. It prevents the creation of poorly documented or easily bypassed skills.

Core Features & Use Cases

  • TDD for Skills: Adapts the RED-GREEN-REFACTOR cycle for skill documentation.
  • Pressure Testing: Develops scenarios to test skills under realistic constraints (time, sunk cost, authority).
  • Rationalization Countermeasures: Identifies and explicitly addresses common excuses agents use to bypass rules.
  • Use Case: Before deploying a new skill that enforces a critical coding standard, you would use this skill's methodology to write test scenarios that agents would fail without the skill, then write the skill to make them pass, and finally refactor to ensure they can't find loopholes.

Quick Start

Follow the RED-GREEN-REFACTOR cycle to create or update any skill.

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 skill development?

Test-Driven Development for AI skill development applies the RED-GREEN-REFACTOR cycle to skill documentation, ensuring robust and effective agent behavior through rigorous pressure testing and compliance checks.

Why does my AI agent bypass skill documentation under realistic constraints?

Agents often bypass skill documentation under realistic constraints like time or sunk cost due to rationalization. This issue is solved by identifying common excuses and applying explicit countermeasures during skill authoring.

What is the best way to pressure test agent behavior for compliance?

The best way to pressure test agent behavior is to develop scenarios that simulate realistic operational constraints, verifying that the skill documentation maintains strict rule enforcement without finding loopholes.

How do I write test scenarios for skill documentation?

To write test scenarios for skill documentation, follow the RED-GREEN-REFACTOR cycle: write scenarios agents fail without the skill, write the skill to make them pass, then refactor to eliminate any rationalization loopholes.

When do I need to use TDD for skill authoring?

You need to use TDD for skill authoring before deploying new or updated skills that enforce critical coding standards, ensuring the documentation is robust, compliant, and effective under realistic operational constraints.