beo-writing-skills

Enforce a test-driven RED-GREEN-REFACTOR workflow for creating beo skills.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/minhtri2710/skills --skill beo-writing-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beo-writing-skills
Source: https://github.com/minhtri2710/skills/tree/main/skills/beo/writing-skills
Command: npx skills add https://github.com/minhtri2710/skills --skill beo-writing-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Solves the problem of untested, error-prone beo skills by enforcing a rigorous, test-driven workflow.

Core Features & Use Cases

  • Establishes a standardized process for skill creation (RED, GREEN, REFACTOR, VALIDATE).
  • Provides templates and pressure-test prompts to surface rationalizations.
  • Enables documentation of baseline tests and CREATION-LOGs for auditability.

Quick Start

Create baseline pressure tests first, then draft the SKILL.md to capture observed rationalizations.

Frequently Asked Questions about beo-writing-skills

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

FAQPage Schema
How do I use test-driven development for writing beo skills?

Pressure testing beo skills means creating baseline tests before drafting content to surface rationalizations and prevent errors, ensuring your skill logic is validated upfront rather than tested after the fact.

How do I use test-driven development for writing beo skills?

Test-driven writing for beo skills follows the RED-GREEN-REFACTOR-VALIDATE cycle: write baseline pressure tests first, draft SKILL.md to capture observed rationalizations, then document pressure-test outcomes in CREATION-LOG.md for full auditability.

What is a CREATION-LOG and why do I need it for skill creation?

A CREATION-LOG is a markdown file documenting baseline pressure-test outcomes and observed rationalizations during skill creation. You need it to maintain auditability and track the RED-GREEN-REFACTOR workflow progress.

Can I use this structured writing workflow to edit existing beo skills?

Yes, you can use this structured writing workflow to edit existing beo skills. It requires establishing baseline pressure tests before modifying content, ensuring your edits do not introduce untested rationalizations or errors.

What's the best way to document pressure-test outcomes in beo skills?

The best way to document pressure-test outcomes is by maintaining a CREATION-LOG.md file throughout the RED-GREEN-REFACTOR cycle. This captures observed rationalizations and provides a standardized audit trail for your skill creation process.

When should I not use pressure testing for skill creation?

You should not skip pressure testing when creating beo skills if you need auditability and error prevention. However, if you are drafting rapid prototypes without requiring structured validation or CREATION-LOG documentation, this workflow may be too rigorous.