agentsclimarketplace
Sign in

Propose automation

Skill ada-ggf25/AI-Tools/global/codex/skills/propose-automation

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".From its SKILL.md

Install
npx -y skills add ada-ggf25/AI-Tools --skill propose-automation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.0 KB, 593 tokens by cl100k_base, as published. Nobody here has run it

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 points are not already clear:

  • What repeated repo task feels tedious?
  • What multi-step task would benefit from one command?
  • What should always happen but sometimes gets forgotten?

Treat scan-based ideas as hypotheses.

3. Propose

Return 2-4 ranked proposals. For each include:

  • name and purpose;
  • artifact type;
  • target placement;
  • workflow pain addressed;
  • ROI rationale;
  • guardrails and source-of-truth docs it should reference.

Then list deferred ideas with reasons.

4. Scaffold Only Approved Items

For each approved item:

  • Use the correct Codex format and location.
  • Keep instructions thin and repo-grounded.
  • Add helper scripts only when deterministic reliability matters.
  • Validate syntax and naming.

5. Record The Plan

Offer to save the ranked plan to AUTOMATION-PLAN.md or another user-approved path.

Guardrails

  • Never build during the proposal step.
  • Never duplicate source-of-truth docs.
  • Keep proposed automation few and high-confidence.
  • Use Codex-native paths and formats for Codex artifacts.
  • Never fabricate repo facts.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most automation workflows skills give in 593 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

  • Write conventional commit messagesin 36 of 745, across 35 files
  • Delete branches after mergein 30 of 745, across 21 files
  • Make atomic commitsin 25 of 745, across 15 files
  • Write minimal code to pass testsin 22 of 745, across 10 files
  • Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
  • Use try-catch for error handlingin 20 of 745, across 8 files
  • Run tests before committingin 20 of 745, across 12 files
  • Write tests before implementationin 20 of 745, across 8 files
  • Configure branch protection rulesin 19 of 745, across 5 files
  • Explain the why in commit messagesin 19 of 745, across 9 files
  • Refactor code while tests remain greenin 19 of 745, across 6 files
  • Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

  • Propose automation before scaffolding it
  • Include a deferred ideas section
  • Read root documentation manifests and CI
  • Skim recent git history
  • Ask up to three targeted pain questions
  • Return two to four ranked proposals

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,679. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.