Tailor a bootstrapped repo into a project-specific operating system by capturing intent, constraints, and preferences, then updating docs and generating a repo-local REPO_PROFILE.json. Use only when explicitly invoked.
SkillScore83Maintained
Automatic
◆Project Management pack
Last verified 8/3/2026
What it changes
Passed 18 of 22 test cases with the skill, and 8 of 22 without it.
Without skill35%
With skill83%
Checks it passed that the model alone missed
The completion report recommends create-plan as the next step.
The completion report length is bounded between 8 and 14 lines.
The schema requires paths fields for frontend_root and backend_root.
and 13 more in the full report
11 fixed8 passed either way4 still failing0 broke
Pass-rate lift
+48 pp
Tokens
+32%
Agent turns
0%
Response time
-52%
Model gemini-3.6-flashMeasured 8/3/2026v119 of 23 cases passed with skill · 22 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
We have `~/.codex/repo_profile.json` set up on our developer workstation and a local `REPO_PROFILE.json` inside the repository. When personalizing this repository, which file should be modified to serve as the authoritative configuration for downstream build skills?
What was checked, without and with the skill
Checked
Without skill
With skill
The response specifies modifying the repository root REPO_PROFILE.json as the canonical contract.
Passed
Passed
The response treats ~/.codex/repo_profile.json as a read-only reference template.
Missed
Passed
case-07 · gemini-3.6-flash · 8/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md157 linessingle file
Personalize Repo
Goal
Convert a generic scaffold into a project-specific operating system by capturing intent, tradeoffs, and constraints, then updating docs accordingly.
This skill also creates or finalizes the repo’s canonical execution contract:
REPO_PROFILE.json in repo root
The global profile at ~/.codex/repo_profile.json is a reference template only.
This is intentionally more open-ended than bootstrap-repo.
Non-negotiables
Start with questions. Do not edit files until answers are received OR the user approves proceeding with stated assumptions.
Do not create duplicate files. Modify existing files in place.
Keep outputs concrete: update documents, not vibes.
Make assumptions explicit if proceeding without answers.
Do not introduce new skills unless explicitly requested.