| name | agent-config-maintenance |
| description | Refactor Codex configuration files and Agent Skills by splitting concerns, deduplicating instructions, and reorganizing guidance across AGENTS.md, project docs, and skills. Use when asked to clean up AGENTS.md, move instructions into skill bundles, or standardize agent setup rules. |
Agent Config Maintenance
Scope
- Target files:
AGENTS.md, project-doc sections,skills/*/SKILL.md, and any references underskills/*/references/. - Focus on separation of concerns: global agent rules vs task-specific workflows.
Workflow
- Inventory instructions
- Use
rgto find duplicate or conflicting rules across AGENTS, project docs, and skills. - Note which rules are global constraints vs task-specific procedures.
- Use
- Decide the split
- Keep only global, always-on constraints in
AGENTS.md. - Move task-specific procedures into the relevant skill
SKILL.mdorreferences/. - Remove duplicated bullets after moving.
- Keep only global, always-on constraints in
- Update skill metadata
- Fill
SKILL.mdfrontmatter withnameand a trigger-readydescription. - Keep the description explicit about when to use the skill.
- Fill
- Write the skill body
- Use imperative form.
- Keep core workflow in
SKILL.md. - Move large checklists or detailed examples into
references/and link them.
- Validate consistency
- Ensure AGENTS and skills do not contradict each other.
- Verify naming conventions (lowercase + hyphen).
- Confirm only necessary files exist; avoid extra docs.
Quality gates
- Keep
SKILL.mdunder 500 lines. - Avoid duplication between
SKILL.mdand any reference files. - If adding scripts, run them once to validate behavior.