joey-skill-authoring

Create and validate Codex skills with structured frontmatter and placement rules.

Updated May 18, 2026
One-click install
npx skills add https://github.com/Joey-Tools/codex-private-workflows --skill joey-skill-authoring-joey-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: joey-skill-authoring
Source: https://github.com/Joey-Tools/codex-private-workflows/tree/main/personal_codex/skills/joey-skill-authoring
Command: npx skills add https://github.com/Joey-Tools/codex-private-workflows --skill joey-skill-authoring-joey-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? Repeated workflows get re-explained in every session because there is no consistent process for turning them into reusable Codex skills with triggerable descriptions and correct placement. ## Core Features & Use Cases - Skill Authoring Workflow: Guides creation from concrete trigger phrasings through frontmatter description writing to body structure, keeping AGENTS.md terse and moving detail into references. - Placement Decisions: Distinguishes personal skills in ~/.codex/skills from repo-local skills in .agents/skills based on whether the workflow depends on host-level state or repo-owned scripts. - Validation Wrapper: Runs the installed OpenAI quick_validate.py over one or more skills via scripts/codex_skill_validate.py, with uv fallback, validator discovery, and JSON report output. - Use Case: After noticing the same release-check procedure repeated across repos, use this Skill to draft a personal skill, write a description that triggers reliably, and validate it before committing. ## Quick Start Use the joey-skill-authoring skill to turn this repeated workflow into a validated personal Codex skill with a proper frontmatter description.

Frequently Asked Questions about joey-skill-authoring

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

FAQPage Schema
How do I create a Codex skill with a good frontmatter description?

Write the description before the body, stating the main job first followed by two to four concrete triggers. Start from two or three real user phrasings that should activate the skill, then validate the result with quick_validate.py.

When should a skill be personal versus repo-local?

Use a personal skill in ~/.codex/skills for cross-repo habits and host-level workflows driven by files like ~/.codex/rules. Use a repo-local skill in .agents/skills only when the workflow genuinely depends on repo-owned scripts, fixtures, or policy.

How do I validate a Codex skill before committing it?

Run scripts/codex_skill_validate.py with the skill directory as an argument, optionally adding --report to write full JSON results. The wrapper locates the installed OpenAI quick_validate.py and falls back from uv to direct python execution if needed.

What if quick_validate.py fails because PyYAML is missing?

Retry through uv run --isolated --with pyyaml, which the wrapper attempts automatically when uv is available. If uv is unavailable, fall back to explicit checks of the frontmatter, body structure, and referenced resources.

What belongs in AGENTS.md versus SKILL.md versus references?

AGENTS.md holds only short distilled reminders and pointers. SKILL.md contains the workflow, decision rules, and resource-loading instructions, while references/ stores detailed notes, examples, pitfalls, and post-mortems.