writing-skills

Create and test agent skills using test-driven development methodology.

1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/maopujie10-sys/Bailongma --skill writing-skills-maopujie10-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/maopujie10-sys/Bailongma/tree/main/src/skills/superpowers/writing-skills
Command: npx skills add https://github.com/maopujie10-sys/Bailongma --skill writing-skills-maopujie10-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation-style skills for AI agents often produces instructions that agents ignore or misinterpret under pressure. This Skill applies test-driven development to skill authoring so every skill is verified against real agent behavior before deployment. ## Core Features & Use Cases - TDD-Based Skill Authoring: Run baseline pressure scenarios with subagents (RED), write the skill to address observed failures (GREEN), then close rationalization loopholes (REFACTOR). - Discovery Optimization: Guidance on writing descriptions, keywords, and naming so future agents can find the skill when it matters. - Testing Methodology: Includes pressure-scenario design, rationalization tables, red-flag lists, and persuasion principles for bulletproofing discipline-enforcing skills. - Use Case: You want to create a new skill that forces agents to verify work before completion. Use this Skill to first watch a subagent skip verification under time pressure, then write targeted counters and re-test until compliance holds. ## Quick Start Ask the agent to use the writing-skills skill to create a new skill for your chosen technique, starting with a baseline pressure scenario before writing any documentation.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I create a new agent skill with SKILL.md?

Create a directory containing a SKILL.md file with YAML frontmatter defining name and description, followed by markdown instructions. This skill requires running baseline pressure scenarios first, then writing content that addresses the failures you observed.

How to test whether an agent skill actually works?

Run pressure scenarios with subagents without the skill to document baseline failures, then re-run with the skill present to verify compliance. Combine multiple pressures like time limits, sunk cost, and authority to expose rationalizations.

What should go in a SKILL.md description field?

Write a third-person description starting with "Use when..." that lists only triggering conditions and symptoms. Never summarize the skill's workflow, because agents may follow the description instead of reading the full skill body.

When should I not create a new skill?

Skip skill creation for one-off solutions, project-specific conventions, well-documented standard practices, and mechanical constraints that can be enforced with validation or regex instead of documentation.

Why do agents ignore skill instructions under pressure?

Agents rationalize rule violations when facing time pressure, sunk cost, or authority conflicts. Counter this with explicit prohibition of specific workarounds, rationalization tables, red-flag lists, and foundational principles stated early.