Claude Code skills I actually run — the clodex plan→build→verify→ship pipeline for Claude Code + Codex CLI, three adversarial-rigor skills, and standalone process skills
Skill Claude CodeCodex
Use when onboarding a new agentmail agent — giving a repo its own email and Telegram identity behind the human-approval send gate. Triggers - "onboard a new agentmail agent", "onboard an email agent", "give this repo an email identity", "give this repo a mailbox and Telegram identity", or an explicit…
Skill Claude CodeCodex
Use when the clodex router hands off a run whose lane is audit — a review / inventory / assessment ask with no change requested yet — or when a resumed run's manifest shows lane audit and the run is not closed.
Skill Claude CodeCodex
Use when the clodex router or clodex-plan hands off a run at stage build, when a resumed run has an approved plan whose batches are not all committed and reviewed, or when a plan assumption turns out to be wrong while implementation is already in flight.
Skill Claude CodeCodex
Use when the clodex router hands off a run at stage open or plan, when a run the router resumed shows no recorded plan or a plan with no standing approval, or when plan-review findings on such a run still need dispositions before work can start.
Skill Claude CodeCodex
Use when the clodex router or clodex-verify hands off a run at stage ship, when a resumed run's manifest shows stage ship or a release step still pending, or when a run's release state is push-failed or deploy-failed.
Skill Claude CodeCodex
Use when the clodex router or clodex-build hands off a run at stage verify, when a run's declared evidence classes have not all been produced or written off, or when a resumed run's manifest shows stage verify.
Skill Claude CodeCodex
Use when any development work starts in a repository — a feature request, a dense brief, a bug fix, "continue where we left off", or an ask whose shape is unclear. Also use when a repo has a .clodex/ directory with an unfinished run, and before invoking clodex-plan, clodex-build, clodex-verify, or clodex-ship.
Skill Claude CodeCodex
Use when developing a strategy, defending a position, processing a belief, or something feels right but not the whole story — before presenting, committing to, or shipping it.
Skill Claude CodeCodex
Use when a claim, statistic, or assumption is about to be repeated, cited, or built upon — especially in a deck, meeting, or strategy document — and hasn't been checked against real evidence.
Skill Claude CodeCodex
Use when building or restyling any user-facing UI — web apps, dashboards, media libraries, client deliverables, prototypes, artifacts — before writing the first component or stylesheet. Also use when an existing UI feels generic, templated, or AI-generated and needs a design pass.
Skill Claude CodeCodex
Use when orchestrating a large multi-deliverable task (document set, research corpus, audit, migration, parallel build) that should run end to end while conserving main-thread premium-model tokens, when the user asks for the Fable-plans-Opus-executes split or to protect usage limits on delegated work, or when…
Skill Claude CodeCodex
Use when about to present, ship, or commit to a plan, pitch, contract, or decision, and want every gap and weak assumption found before a client, stakeholder, or reality finds it.
Skill Claude CodeCodex
Use when asked to run a vinyl-shop dig — crawl a set of local record shops' online catalogs in parallel, benchmark prices against Discogs, and produce a tiered buy list. Originated for Johnny's Chicago digs; portable to any city/shop-list as long as the calling project provides the companion files below.