propose-automationlisted

Scan the current repository, infer its workflow, and propose a short, ranked, high-ROI plan of Codex skills, custom agents, hooks, or plugins tailored to it; scaffold only approved items. Global and project-agnostic. Trigger when the user says "what Codex skills should this project have", "propose automation", "set up skills for this repo", "scaffold agents/hooks", "plan Codex automation", or "what should I automate".
ada-ggf25/AI-Tools · ★ 2 · AI & Automation · score 66

Install: claude install-skill ada-ggf25/AI-Tools

# Propose Codex Automation Scan a repo, infer how work flows through it, and propose a short ranked plan of Codex skills, custom agents, hooks, or plugins. Propose first; scaffold only after approval. ## Operating Principles 1. **Skill vs agent vs hook vs plugin** - Skill: repeatable, context-rich, steerable workflow. - Custom agent: named reusable role for isolated or parallel subagent work. - Hook: deterministic always-on automation. - Plugin: packaged distribution unit for Codex artifacts. 2. **Placement** - Project: `.agents/skills`, `.codex/agents`, repo plugin, or repo hooks when coupled to this repo. - Personal/global: `${CODEX_HOME:-~/.codex}` only when project-agnostic. 3. **Thin artifacts** Generated skills should reference source-of-truth docs such as `AGENTS.md`, README, manifests, and style guides instead of duplicating them. 4. **ROI** Value is frequency times time saved times error reduction. Cost is build time, maintenance, and cognitive overhead. Propose only when value clearly beats cost. 5. **Restraint** Always include a "Deferred / not worth it" section. ## Procedure ### 1. Orient - Read `AGENTS.md`, `CLAUDE.md` if present, README, manifests, CI, and existing `.agents/`, `.codex/`, and plugin files. - Skim recent git history to infer repeated work. - For a large repo, delegate broad exploration to a read-only subagent when available. ### 2. Ask About Pain Ask 2-3 targeted questions only if the user's pain poi