Menu
Use when creating, editing, auditing, or validating Agent Skills. Covers TDD-based creation and specification compliance auditing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user mentions "analyzing a project", "analyzing a repository", "analyzing GitHub", "project analysis", "source code analysis", "architecture analysis", "code analysis", "studying this project", "studying this framework", "seeing how this library is implemented", "comparing two projects", "project evaluation", "framework evaluation"
Design and implement distinctive, production-ready frontend interfaces with strong aesthetic direction. Use when asked to create or restyle web pages, components, or applications (HTML/CSS/JS, React, Vue, etc.).
Interview the user relentlessly about a plan, design, or domain model until reaching shared understanding. Use when user wants to stress-test a plan, get grilled, or mentions "grill me".
Trigger native web search. Use when you need quick internet research with concise summaries and full source URLs.
Fetch a URL or convert a local file (PDF/DOCX/HTML/etc.) into Markdown using `uvx markitdown`, optionally it can summarize
Use `uv` instead of pip/python/venv. Run scripts with `uv run script.py`, add deps with `uv add`, use inline script metadata for standalone scripts.
| name | skill-authoring |
| description | Use when creating, editing, auditing, or validating Agent Skills. Covers TDD-based creation and specification compliance auditing. |
Skill Authoring is the complete lifecycle of creating and maintaining high-quality Agent Skills. It combines Test-Driven Development (TDD) for creation with rigorous auditing for specification compliance and quality.
Core principle: If you didn't watch an agent fail without the skill, you don't know if the skill teaches the right thing.
Writing skills is TDD applied to process documentation.
| TDD Concept | Skill Creation |
|---|---|
| RED | Run baseline scenario WITHOUT skill. Document exact failure/rationalization. |
| GREEN | Write minimal skill addressing those specific violations. Watch it pass. |
| REFACTOR | Close loopholes and consolidate logic while maintaining compliance. |
NO SKILL WITHOUT A FAILING TEST FIRST. Delete any untested skill code.
Maintain a clean, efficient library by identifying redundant skills and specification violations.
name (kebab-case, max 64 chars) and description (max 1024 chars).## Overview and ## When to Use sections.Skills are duplicates if they share the same name, same purpose, or overlapping functionality.
name and description?# Check name matches directory
name=$(grep "^name:" SKILL.md | cut -d' ' -f2)
[ "$name" == "$(basename $PWD)" ] || echo "Error: Name mismatch"
# Check for required sections
grep -q "^## Overview" SKILL.md && grep -q "^## When to Use" SKILL.md || echo "Error: Missing sections"