writing-skills

Create, edit, and verify agent skills using test-driven development with subagent pressure scenarios.

66|4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/SummerEngine/summer --skill writing-skills-summerengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/SummerEngine/summer/tree/main/library/skills/writing-skills
Command: npx skills add https://github.com/SummerEngine/summer --skill writing-skills-summerengine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing agent skills without testing them is guesswork: you cannot know whether a SKILL.md actually changes agent behavior until you watch an agent fail without it. This Skill applies the RED-GREEN-REFACTOR cycle to skill authoring so every skill is verified against real baseline failures 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). - Discovery optimization (CSO): Guidance for writing trigger-focused descriptions, keyword coverage, token-efficient structure, and correct cross-referencing between skills. - Testing methodology reference: The companion file testing-skills-with-subagents.md details pressure types, rationalization tables, red-flag lists, and meta-testing techniques. - Use Case: You want to add a new discipline-enforcing skill (e.g., verification-before-completion). Run a scenario where an agent is under time and sunk-cost pressure without the skill, record its exact rationalizations, write the skill to counter them, and re-test until the agent complies under maximum pressure. ## Quick Start Ask your agent to use the writing-skills skill to create a new skill for a recurring workflow, starting with a baseline pressure scenario before writing any SKILL.md content.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I test an agent skill before deploying it?

Run pressure scenarios with a subagent without the skill first to document baseline failures verbatim, then write the skill addressing those failures and re-run the same scenarios. Combine three or more pressures like time, sunk cost, and authority to verify the agent complies under stress.

What should a SKILL.md description field contain?

The description should start with "Use when..." and list only triggering conditions, symptoms, and situations in third person. Never summarize the skill's workflow, because agents may follow the description shortcut instead of reading the full skill body.

What is the required structure of a SKILL.md file?

A SKILL.md requires YAML frontmatter with name and description fields (max 1024 characters total), followed by a Markdown body with an overview, when-to-use guidance, core patterns, quick reference, and common mistakes. The name must use only letters, numbers, and hyphens.

When should I not create a new agent skill?

Skip creating skills for one-off solutions, project-specific conventions (those belong in CLAUDE.md), well-documented standard practices, and mechanical constraints that can be enforced with regex or validation. Reserve skills for judgment calls and reusable techniques.

Why do agents ignore skills under pressure?

Agents rationalize violations with excuses like sunk cost, spirit-versus-letter arguments, or pragmatic framing. Counter this by closing each loophole explicitly, building a rationalization table, adding a red-flags list, and stating that violating the letter violates the spirit.