writing-skills

Apply test-driven documentation to create and validate SKILL.md entries.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Kinshuk699/sEYEght --skill writing-skills-kinshuk699
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Kinshuk699/sEYEght/tree/main/.agents/skills/writing-skills
Command: npx skills add https://github.com/Kinshuk699/sEYEght --skill writing-skills-kinshuk699

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents untested, inconsistent, or easily-rationalized agent skills by applying a test-driven documentation process so skills reliably change agent behavior under pressure.

Core Features & Use Cases

  • TDD mapping for skills: RED-GREEN-REFACTOR cycle adapted to SKILL.md authoring and validation.
  • Pressure testing methodology: Create realistic scenarios with subagents to capture rationalizations and verify compliance.
  • Guidance and tooling: Checklists, persuasion principles, deployment requirements, and a graph-rendering utility to visualize flowcharts.
  • Use Case: Author or edit a SKILL.md for a discipline-enforcing practice (e.g., TDD rules) and verify the skill prevents common loopholes under combined pressures.

Quick Start

Use writing-skills to design a SKILL.md, run baseline pressure scenarios without the skill, record failures verbatim, then iterate until agents comply under pressure.

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 to write agent skills that resist rationalization?

Test-driven development for agent skills applies a RED-GREEN-REFACTOR cycle to SKILL.md authoring. You record baseline pressure failures without the skill, then iterate documentation until subagents comply under combined pressures. This prevents untested or rationalized skill behavior.

What is the best way to pressure test agent skills against loopholes?

The best way to pressure test agent skills is deploying subagents in realistic scenarios to capture rationalizations and verify compliance. You run baseline pressure scenarios without the skill, record failures verbatim, and iterate the SKILL.md until agents comply under pressure.

Do I need subagents to validate SKILL.md entries for agent workflows?

Yes, subagents are required to validate SKILL.md entries by running pressure scenarios that capture rationalizations. This test-driven documentation process ensures skills reliably change agent behavior under pressure rather than relying on untested assumptions.

How does TDD mapping work when creating discipline-enforcing patterns for agents?

TDD mapping adapts the RED-GREEN-REFACTOR cycle to SKILL.md authoring and validation. You design a discipline-enforcing practice, run baseline pressure scenarios without it, record failures, then iterate the documentation until agents comply under combined pressures.

Can I visualize flowcharts for skill testing and documentation workflows?

Yes, you can visualize flowcharts for skill testing workflows using the included graph-rendering utility. This tool helps render the RED-GREEN-REFACTOR cycle and pressure testing methodology applied to SKILL.md authoring and validation.

What format does a SKILL.md entry require for test-driven documentation validation?

A SKILL.md entry requires frontmatter with name and description fields for test-driven documentation validation. Optional reference or script files can be included for heavy resources when applying the RED-GREEN-REFACTOR testing cycle.