staff-writing-skills

Create and harden skill documentation with frontmatter and RED-GREEN-REFACTOR testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps authors turn process knowledge into reusable skills that future agents can discover, load, and follow consistently instead of improvising or drifting from the intended workflow.

Core Features & Use Cases

  • Skill design guidance for deciding when a skill is worth creating.
  • Frontmatter and naming rules for discoverability, including trigger phrases and search keywords.
  • Test-first skill authoring with baseline pressure scenarios, RED-GREEN-REFACTOR iteration, and explicit loophole closure.
  • Content architecture guidance for concise overviews, references, scripts, and progressive disclosure.
  • Use it when writing a new skill, revising an existing skill, or verifying that a skill survives pressure and rationalization.

Quick Start

Use this skill to draft or revise a skill by identifying the trigger, writing the frontmatter, and validating the instructions against realistic failure scenarios.

Frequently Asked Questions about staff-writing-skills

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

FAQPage Schema
How do I write agent skills that AI models actually follow reliably?

Writing reliable agent skills requires valid YAML frontmatter, strong discovery keywords, and concise progressive disclosure so agents can discover, load, and follow instructions instead of improvising or drifting from the intended workflow.

What is RED-GREEN-REFACTOR testing for skill authoring?

RED-GREEN-REFACTOR testing for skill authoring is a test-first method that validates skill instructions against baseline pressure scenarios, iterates until compliance passes, then refactors to close loopholes where agents might rationalize or drift.

Why do AI agents ignore or drift from my skill documentation?

AI agents drift from skill documentation when instructions lack valid frontmatter, clear trigger phrases, or concise progressive disclosure, allowing pressure, rationalization, or unclear discovery keywords to cause compliance failures during execution.

How do I make a skill discoverable for AI agents using search keywords?

Making a skill discoverable requires valid YAML frontmatter with strong trigger phrases and search keywords that match user queries, ensuring future agents can reliably find and load the skill documentation when needed.

When should I create a new skill instead of adding instructions to an existing prompt?

You should create a new skill when you have reusable process knowledge that future agents need to discover, load, and follow consistently, rather than improvising or drifting from the intended workflow in an ad-hoc prompt.