tkersey
@tkersey
Public Skills
lift
by tkersey
"Comprehensive, measurement-driven performance optimization for latency, throughput, memory/GC, and tail behavior. Use when the user asks to optimize/speed up, reduce latency (p95/p99), increase throughput/QPS, lower CPU/memory/allocations/GC pauses, profile hot paths, or run a benchmarked perf pass (including JSONL/query-heavy code). Requires before/after measurement on a runnable workload (or an explicit UNMEASURED plan) plus a correctness gate. Zig-first CLI iteration where bench_stats/perf_report are proven first and wrappers are kept in parity."
tk
by tkersey
"Software surgery protocol for proof-backed, minimal-diff implementation: Contract to Invariants to Creative Frame to inevitable incision to Proof. Use when users say \"run $tk\", \"patch-first\", \"keep the diff small\", \"state contract + invariants\", \"one clear incision\", \"fix it with a validation signal\", or orchestration cues like \"workers use $tk\" / \"internally use $tk\"."
st
by tkersey
Manage persistent task plans in repo-committed JSONL (.step/st-plan.jsonl) so state survives turns/sessions and stays reviewable in git. Use when users ask to "use $st", "resume the plan", "export/import plan state", "checkpoint milestones", "track dependencies/blocked work", "show ready next tasks", "keep shared TODO status on disk", "map a $select plan into durable execution state", "prove $st works for implementation tracking", or diagnose/repair st-plan.jsonl concerns (for example append-only vs mutable semantics, lock-file gitignore policy, or seq/checkpoint integrity).
logophile
by tkersey
"Precision copy edits + naming: compress and clarify without changing meaning. Triggers: $logophile, rewrite/reword/rephrase, shorten, rename titles/labels/headings. Avoid operational scope/validation tasks unless rewriting is explicit."
creative-problem-solver
by tkersey
Lateral-thinking playbook that always returns a five-tier strategy portfolio (Quick Win through Moonshot). Use when you need options, alternatives, or trade-offs; when progress is stalled or failing repeatedly; or when you ask to think creatively, reframe constraints, and choose a strategic path before execution.
plan
by tkersey
Produce essay-heavy, decision-complete plans in proposed_plan block format. Use when asked to run $plan, turn a project brief into an execution-ready architecture plan, or iteratively refine strategy; optionally export to iterative plan-N.md files (max N=5) when explicitly requested outside Plan Mode.
ghost
by tkersey
Create a language-agnostic ghost package (spec + portable tests) from an existing repo by extracting SPEC.md, exhaustive tests.yaml (operations and/or scenarios), INSTALL.md, README.md, VERIFY.md, and upstream LICENSE files with provenance and regeneration instructions. Use when prompts say "$ghost", "ghostify this repo", "spec-ify/spec-package this library", "ghost library", or ask to extract portable spec/tests for libraries or tool-using agent loops (scenario testing); do not use for implementation work or editing skills.
mesh
by tkersey
Swarm coordinator activated only by explicit $mesh invocation. Trigger cues/keywords: orchestrate subagents/workers, execute ready $st slices/tasks, run propose/critique/synthesize/vote cycles, coordinate concurrent workers, require consensus + validation before completion, and persist learnings via $learnings.
fix
by tkersey
Review+fix protocol with safety guardrails (unsoundness, invariants, footguns, incidental complexity). Use when prompts say "$fix this PR", "fix current branch", "fix this diff", "repair CI red", or "apply a minimal patch", and when crash/corruption/invariant-break issues need correction with a validation signal.
puff
by tkersey
Launch and manage Codex Cloud tasks from the CLI, including detached background watchers that track completion. Use when users ask to run coding work in cloud/background agents, queue multiple cloud tasks, poll task status, fetch cloud diffs, apply cloud outputs locally, or pair cloud kickoff with $cas orchestration.
learnings
by tkersey
"Capture and persist evidence-backed execution learnings into .learnings.jsonl. Trigger cues/keywords: $learnings, lessons learned, takeaways, wrap up, handoff, before commit/PR, after tests pass, fail-to-pass, strategy pivot, footgun, retry loop."
cron
by tkersey
Create and manage Codex app automations stored in the local SQLite database (~/.codex/sqlite/codex-dev.db). Use when you need to add, list, update, enable/disable, delete, or run-now automations; edit automation names, prompts, RRULE schedules, or cwd scopes; or inspect automation records while troubleshooting app automation behavior.
seq
by tkersey
"Mine Codex sessions JSONL (~/.codex/sessions) and file-based memories (~/.codex/memories) for skill usage, section/format compliance, trigger evidence, token metrics, and prompt-to-session lookup for resume workflows. Use for prompts like $seq, analyze session history, find sessions by prompt, rank skill mentions, audit missing sections, report token usage, mine memories, or use $seq to improve skill trigger descriptions/frontmatter."
web-browser
by tkersey
"Use when tasks need real-browser web automation in Chrome/Chromium via CDP: open or navigate URLs, click/type/select in forms, run page JS, wait for selectors, scrape structured content, capture screenshots, validate UI flows, or run measured web-browser latency checks (bench:eval, bench:all) for perf regressions."
grill-me
by tkersey
Clarify ambiguous or conflicting requests by researching first, then asking only judgment calls. Use when prompts say "$grill-me"/"grill me", "ask hard questions", "pressure-test assumptions", "clarify scope/requirements", "define success criteria", or request system-design/optimization decisions before implementation; stop before implementation.
reduce
by tkersey
Deconstruct high-cost abstractions and recommend lower-level primitives that reduce tooling, indirection, and hidden steps. Use when requests ask for fewer layers (for example "too many layers", "remove this framework/plugin/DI", "ditch codegen/task runners", "replace with plain scripts/config/SQL"), or ask for an abstraction audit with a prioritized cut list and phased migration with rollback (analysis-only unless implementation is explicitly requested).
xit
by tkersey
"Use when a repo has .xit/ or the user asks for xit: translate git-like intents to non-interactive xit CLI commands (status/diff/log --cli, add/commit/branch/merge/cherry-pick), avoid the TUI, and do not use git unless explicitly requested."
patch
by tkersey
Create micro-patches from staged git changes (minimal incision) with at least one validation signal per patch. Use when asked to split work into small .patch files, export/share diffs, or produce patches instead of commits.
prove-it
by tkersey
Gauntlet for absolute claims (always/never/guaranteed/optimal); pressure-test, then refine with explicit boundaries. Use when users ask to prove or disprove strong certainty claims, request devil's-advocate challenge rounds, or want the $prove-it gauntlet to run in default autoloop/full-auto style.
refine
by tkersey
Refine an existing Codex skill via $ms with minimal diffs, then validate with quick_validate. Trigger when asked to improve a skill's trigger description/frontmatter, workflow text, metadata, scripts/references/assets, or agents/openai.yaml; also for requests to iterate, refactor, rename, or fix a skill using usage/session-mining evidence (for example from $seq).
invariant-ace
by tkersey
"Turn 'should never happen' into 'cannot happen' by defining owned inductive invariants and enforcing them at parse/construct/API/DB/lock/txn boundaries with a verification signal. Use when prompts mention invariants, impossible states, validation sprawl, cache/index drift, idempotency/versioning, retries/duplicates/out-of-order events, race/linearization bugs, loop correctness, or hardening another workflow (for example $fix) with invariant checks first."
ms
by tkersey
Create, update, or refactor Codex skills in this repo, including SKILL.md, frontmatter trigger text, agents/openai.yaml, and scripts/references/assets. Use when asked to create or improve a skill, tighten trigger descriptions from usage evidence (for example via $seq), regenerate/verify agents/openai.yaml, or adjust skill metadata/workflows.
commit
by tkersey
Create micro-commits (minimal incision) with at least one validation signal per commit. Use when requests say "split this into micro commits," "stage only the minimal change and commit," "keep commits tiny while checks pass," or when parallel workers/slices need isolated, reviewable commits.
complexity-mitigator
by tkersey
Mitigate incidental code complexity when control flow is tangled, nesting is deep, names are hard to parse, or reasoning requires cross-file hops. Use when a review stalls on readability, you need an analysis-first refactor plan before edits, or you want essential-vs-incidental verdicts, ranked simplification steps, a small structural sketch, and a TRACE assessment (analysis-only; no edits).
fin
by tkersey
"Finalize GitHub PRs end-to-end: update branch/PR, monitor CI until green, squash-merge, and clean up local/remote state. Use when asked to $fin or to finish/land/merge/close a PR, watch checks or runs, squash-merge, delete the branch, and sync local state."
cas
by tkersey
Run a v2-only Node JSONL proxy that spawns codex app-server and exposes an automation-friendly stream API. Use when you need to drive the app-server programmatically (automation/orchestration/session mining), have subagents send updates or code patches into live sessions, auto-handle approvals, forward server requests with deterministic timeouts, mine sessions via thread/*, steer active turns (turn/steer), or run N parallel instances (each instance is one proxy + one app-server child).
join
by tkersey
"PR autopilot via gh only: create/manage PRs, keep branches current, enforce required CI gates, apply surgical code patches, and publish merge-ready handoff without merging. Use when asked to run or monitor PR automation, fix failing required checks, keep local/remote branch state clean, or prepare branch/PR cleanup for human merge."
zig
by tkersey
"Use when requests involve Zig code or toolchain work: editing .zig, changing build.zig/build.zig.zon, defining or fixing zig build steps (for example zig build ci), handling .zig-cache/CI wiring, running or fixing zig build test run fmt fetch, debugging compile/runtime/test failures, comptime/reflection/codegen, allocator ownership, SIMD (std.simd/@Vector), threads (std.Thread/Thread.Pool), cross-compilation, zero-copy parsing, C interop (@cImport), or Zig 0.15.2 pin/migration issues. Enforce correctness-first validation with tests, std.testing.fuzz, and allocation-failure checks."
select
by tkersey
"Swarm-ready work selector: choose one source (invocation list, SLICES.md, or plan-N.md), refine it into dependency-aware atomic tasks, and emit an OrchPlan (waves + delegation) plus optional pipelines. Use for prompts like $select, use $select, pick the next ready slice, orchestrate workers from SLICES, or what should run in parallel next. Plan-only; no writeback; orchestration-agnostic."
ship
by tkersey
"Finalize work after validation: confirm a signal, capture proof in the PR description, and open a PR (no merge). Use when asked to run $ship, ship/finalize a branch, prepare or open a PR without merging, or publish validation proof before handoff."