project-local-skill-generator
Generate thin project-local .codex/skills from a scaffolded repo's actual harness artifacts. Use after scaffold or harness setup when a repo should have local Codex workflows for feature state, sessio
SKILL.mdskills/project-local-skill-generator/SKILL.md
GitHubProject Local Skill Generator
Purpose
Create short repo-specific .codex/skills that teach Codex how to operate in this project day to day, while keeping reusable harness authoring skills in the plugin.
Inspect First
- existing
.codex/skills AGENTS.md, nestedAGENTS.md, docs, scripts, feature state, progress, decisions, runtime docs, UI docs, review docs, and validation commands- whether each proposed local skill has real repo artifacts to link to
Procedure
Suggest local skills from evidence.
- Use
scripts/suggest_project_local_skills.pyfrom this plugin. - Recommend only skills backed by existing repo files.
- Classify suggestions as
daily,on_demand, orlibraryso high-frequency workflows stay easy to find without bloating root instructions. - Skip skills whose artifacts are missing instead of inventing local policy.
- Use
Generate thin local wrappers.
- Use
scripts/generate_project_local_skills.py. - Write to
.codex/skills/<local-skill-name>/SKILL.md. - Default local skills are
project-feature-workflow,project-session-handoff,project-definition-of-done,project-runtime-debugging,project-ui-workflow, andproject-review-protocol. - Stack-specific local skills may include
project-bun-workflow,project-frontend-workflow,project-browser-qa,project-api-workflow,project-data-workflow,project-docker-runtime, andproject-decision-logwhen matching artifacts exist. - Trajectory local skills may include
project-trajectory-supervisorwhen task traces, trajectory policy, orscripts/check-trajectory-riskexists.
- Use
Preserve local edits.
- Inspect existing local skill files before generation.
- Do not overwrite existing local skills unless the task explicitly requests refresh or overwrite behavior.
- Prefer adding missing skills over regenerating edited ones.
Keep plugin and project roles separate.
- Local skills name exact repo files and commands.
- Local skills route heavy harness authoring back to plugin skills.
- Do not copy full plugin skills into
.codex/skills.
Validate local skills.
- Use
scripts/check_project_local_skills.py. - Confirm links point to real files and commands.
- Confirm local skill bodies are short and repo-specific.
- Use
$subagent-review-orchestratorseparately for.codex/agentsgeneration; do not mix local skills and subagent files.
- Use
Validation
- Run
scripts/suggest_project_local_skills.py <repo> --jsonbefore generating. - Run
scripts/generate_project_local_skills.py <repo>when generation is requested. - Run
scripts/check_project_local_skills.py <repo>after generation. - Confirm existing local skills were preserved unless overwrite was explicitly requested.
Completion Criteria
- The repo has only useful project-local skills backed by actual artifacts.
- Generated skills point to repo-local docs/scripts and avoid generic plugin-scale instructions.
- Reusable harness logic remains in the plugin.