writing-skills

Enforces a TDD-driven workflow for creating and verifying SKILL.md entries.

371|38|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers --skill writing-skills-ibrahim-3d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers/tree/main/skills/writing-skills
Command: npx skills add https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers --skill writing-skills-ibrahim-3d

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a TDD-driven process for skill creation and verification.

Core Features & Use Cases

  • Provides a repeatable skill-creation workflow (frontmatter, structure, and guidance) to ensure consistency across Skill units.
  • Encapsulates testing guidance, rationalization tracking, red flags, and deployment readiness checks to minimize regression risk.
  • Serves as a reference for skill authors to craft concise, discoverable SKILL.md entries that Claude can load and apply reliably.

Quick Start

Draft a new SKILL.md with frontmatter and core sections, then run the skill testing workflow to validate it.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I validate a Claude Skill before deployment?

To validate a Claude Skill before deployment, run a TDD-driven testing workflow that checks frontmatter fields, description sections, and deployment readiness to ensure safe skill creation.

What is the process for authoring a new SKILL.md entry?

Authoring a SKILL.md entry involves drafting strict frontmatter fields, concise description sections, and mandatory testing rituals to ensure the skill is discoverable and reliable.

Does skill creation require specific frontmatter and structure?

Yes, skill creation requires strict frontmatter fields and a concise structure to ensure consistency, discoverability, and safe deployment across writing and governance contexts.

What's the best way to prevent regression risk when editing existing skills?

The best way to prevent regression risk when editing existing skills is applying a TDD-driven verification process with rationalization tracking and deployment readiness checks.

When do I need a testing workflow for skill authoring?

You need a testing workflow for skill authoring when drafting new SKILL.md entries, editing existing skills, or verifying readiness before deployment across writing and testing contexts.

Can I use TDD for governance and documentation checks in skill creation?

Yes, you can use TDD for governance and documentation checks in skill creation to enforce consistent structure, validate metadata, and minimize regression risk before deployment.