writing-skills

Automate skill creation and verification using a red-green-refactor workflow.

Updated Dec 10, 2024
One-click install
npx skills add https://github.com/melikhanmutlu/web_ar --skill writing-skills-melikhanmutlu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/melikhanmutlu/web_ar/tree/main/skills/writing-skills
Command: npx skills add https://github.com/melikhanmutlu/web_ar --skill writing-skills-melikhanmutlu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to creating and validating skills by applying test-driven development principles to process documentation, ensuring skills are robust before deployment.

Core Features & Use Cases

  • Guides skill authors through a RED-GREEN-REFACTOR workflow applied to documentation.
  • Defines frontmatter with name and description; ensures description triggers discovery.
  • Supports testing of skills using pressure scenarios and rationalization tracking.
  • Provides guidance for including references and flowcharts for progressive disclosure.

Quick Start

Draft the SKILL.md with proper frontmatter and a concise body, then run a baseline RED-GREEN-REFACTOR testing cycle to validate the skill.

Quick Start (Example)

Use this pattern to iterate quickly on a new Skill unit.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I apply test-driven development to process documentation before deployment?

Test-driven development for process documentation applies a RED-GREEN-REFACTOR workflow to validate skills against pressure scenarios, ensuring discovery triggers and guardrails align with real usage before deployment.

What is the RED-GREEN-REFACTOR workflow for skill creation?

The RED-GREEN-REFACTOR workflow for skill creation is a testing cycle that establishes baseline tests, validates explicit frontmatter triggers, and iteratively refines documentation to bulletproof skills before deployment.

How do I write frontmatter descriptions that trigger skill discovery?

Writing frontmatter descriptions that trigger skill discovery requires explicit name and description fields validated through rationalization tracking and pressure scenario testing to ensure alignment with real usage.

Does this TDD documentation approach work for all skill types?

Yes, this TDD documentation approach is applicable to all skill types, using baseline testing and rationalization tracking to verify that discovery triggers and guardguards function correctly across diverse use cases.

When should I use rationalization tracking in skill documentation?

Rationalization tracking should be used during skill documentation testing to validate that guardrails and discovery triggers align with real usage, particularly when running pressure scenarios to bulletproof skills before deployment.

Why do my skill documentation guardrails fail under real usage scenarios?

Skill documentation guardrails fail under real usage when they lack baseline testing and rationalization tracking, which are required to align discovery triggers with actual pressure scenarios before deployment.