openai-ads-mcp: Skill for Claude Code

Maintainer Orchestrator

A control-plane skill: inspect, classify, act, monitor, and report. It does not invent product direction — it moves the existing backlog toward a clean, green, reviewed state and escalates anything that needs a human decision.

This skill is designed to run autonomously inside a Claude Code Routine (claude.ai/code/routines) — a cloud session with no permission prompts — but also works when invoked by hand in an interactive session.

The loop (one run)

Each run is one pass. Do these in order, then stop.

1. Scope (owner-guarded). Determine the target repositories.
   • If the Routine cloned multiple repos, act on all of them; if invoked in a single repo with a GitHub remote, act on that repo only.
   • Owner allowlist: only operate on repos whose owner is adityash8 or ITSEZMONEY. Skip any cloned repo outside those owners entirely — no triage, no PR, no merge — and record the skip in the run summary, never in the skipped repo (you have no business writing to it).
   • Do not broaden beyond the cloned/selected repos unless the prompt says all / org-wide.
2. Triage. Invoke the github-project-triage skill to build item cards for every open issue and PR (URL, what/why, author trust, fit, risk, proof/test state, blockers, next action) and sort them into three buckets: autonomous · needs-owner · defer/close.
3. Read the ledger (single, race-safe). Locate the repo's ledger by the maintainer-ledger label (canonical), falling back to the exact title 🤖 Maintainer Loop — Ledger. Exactly one must stay open. If several are open — two runs can race and each create one — keep the lowest-numbered open ledger, close the rest as duplicates (state_reason: duplicate with duplicate_of set to the survivor), and continue on the survivor. If none exists, create it, ensure the maintainer-ledger label exists, and apply it. Never open a second ledger when one is already open. The ledger is the durable memory across runs (cloud sessions are ephemeral); skip anything it marks resolved or wontfix.
4. Act on autonomous items, one at a time, verifying each before moving on (see Autonomy policy below). Stop touching an item the moment it stops meeting the bar and reclassify it as needs-owner.
5. Escalate needs-owner items. Don't guess at product/direction/secret decisions. Label needs-owner, leave a one-paragraph comment stating the decision required and the options, and record it in the ledger.
6. Defer/close stale, duplicate, or superseded items with a short reason.
7. Report. Update the ledger issue with what changed this run (landed, escalated, deferred, still-in-flight) and the timestamp. Keep it skimmable.