writing-skills

Create, edit, and validate Claude skills with TDD-style guidelines and pressure-scenario templates.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill writing-skills-jmduea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/jmduea/emotiv-cortex-rs/tree/main/.github/skills/writing-skills
Command: npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill writing-skills-jmduea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating reliable Claude skills is error‑prone and often skips the essential testing phase, leading to undocumented loopholes and inconsistent agent behavior.

Core Features & Use Cases

  • TDD‑style workflow: RED‑GREEN‑REFACTOR cycle for skill documentation.
  • Pressure‑scenario templates: Ready‑made scenarios that expose rationalizations agents might use to bypass a skill.
  • Checklists & red‑flag tables: Structured lists that ensure all loopholes are closed before deployment.
  • When to use: Authoring new skills, revising existing SKILL.md files, or verifying that a skill works under realistic pressures.

Quick Start

Run the writing-skills skill to get step‑by‑step guidance for creating, editing, and testing Claude skills.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I test Claude skills before deployment?

Test Claude skills before deployment using TDD-style RED-GREEN-REFACTOR workflows, pressure-scenario templates, and checklist enforcement to expose rationalizations agents might use to bypass the skill.

What is the best way to author SKILL.md files?

Author SKILL.md files by applying TDD-style guidelines and structured red-flag tables, ensuring all documentation loopholes are closed and agent behavior remains consistent across scenarios.

Why does my Claude skill fail under realistic pressure?

Claude skills fail under realistic pressure when pressure-scenario templates are skipped during creation, leaving undocumented loopholes that allow agents to rationalize bypassing the skill instructions.

How do I validate skill compliance and close documentation loopholes?

Validate skill compliance by enforcing structured checklists and red-flag tables during the TDD cycle, systematically identifying and closing loopholes before the skill is deployed.

Can I use a TDD workflow for Claude skill documentation?

Yes, you can use a TDD workflow for Claude skill documentation by applying the RED-GREEN-REFACTOR cycle to author, edit, and test skills, ensuring bulletproof creation before deployment.