writing-skills

Create and validate agent skills using test-driven development with subagent pressure scenarios.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/marcocpt/trae_skills --skill writing-skills-marcocpt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/marcocpt/trae_skills/tree/main/writing-skills
Command: npx skills add https://github.com/marcocpt/trae_skills --skill writing-skills-marcocpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Untested skill documentation often fails in practice because agents rationalize around rules under pressure. This Skill applies test-driven development to skill authoring so you verify that agents actually follow instructions before deployment. ## Core Features & Use Cases - TDD-based skill authoring: Run baseline pressure scenarios with subagents (red), write the minimal skill addressing observed failures (green), then close rationalization loopholes (refactor). - Claude Search Optimization guidance: Write discovery-focused descriptions with trigger conditions, keyword coverage, and token-efficient structure. - Testing methodology references: Includes guides for pressure-scenario testing with subagents, persuasion principles for discipline-enforcing skills, and Anthropic's official best practices. - Use Case: Before publishing a new TDD-enforcement skill, run a scenario where an agent has 200 lines of untested code and a dinner deadline, capture its rationalizations verbatim, then harden the skill until compliance holds under maximum pressure. ## Quick Start Ask the agent to help you create a new skill using the writing-skills TDD workflow, 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 test a skill before deploying it?

Run baseline pressure scenarios with subagents before writing the skill, record the agent's exact rationalizations verbatim, then write the minimal skill addressing those failures. Retest under combined pressures like time, sunk cost, and authority until no new loopholes appear.

What makes a good skill description for discovery?

Start with trigger conditions describing when to use the skill, written in third person, without summarizing the workflow. Include concrete symptoms, error messages, and searchable keywords so agents can match the skill to their current task.

How do I write a SKILL.md frontmatter correctly?

Include only the required name and description fields in YAML frontmatter, staying under 1024 characters total. Use letters, numbers, and hyphens for the name, and keep the description focused on trigger conditions rather than process summaries.

Why do agents ignore skills under pressure?

Agents rationalize around rules when facing time pressure, sunk costs, or authority conflicts. Counter this with explicit loophole closures, rationalization tables, red-line lists, and foundational principles stating that violating the letter violates the spirit.

When should I not create a new skill?

Skip creating skills for one-off solutions, well-documented standard practices, project-specific conventions that belong in CLAUDE.md, or mechanical constraints better enforced through automated validation like regex checks.