claude-exec
FreeRun one prompt through headless Claude with scoped permissions and a time bound. Use when: scripting or automating a `claude -p` call, even a simple one.
The English summary is being prepared. Showing the original description.
32 skills (repositories by boshu2) · sorted by popularity
Run one prompt through headless Claude with scoped permissions and a time bound. Use when: scripting or automating a `claude -p` call, even a simple one.
The English summary is being prepared. Showing the original description.
Settle what domain terms mean per context, and which repository conventions or language standards (Go, Python) apply. Use when: names disagree or a rename is proposed.
The English summary is being prepared. Showing the original description.
Drive one accepted change through implementation and checks to done, with one fresh review only where a mistake is costly. Use when: selected by name.
The English summary is being prepared. Showing the original description.
Operate a caller-selected Gas City 1.4 with upstream registry packs and native run-centered surfaces while keeping GC runtime state out of AgentOps verdicts. Triggers: "using gc", "gas city", "drive the mayor", "dispatch through gc".
The English summary is being prepared. Showing the original description.
Freshly judge exact subject content against bead or caller acceptance, optionally persist verdict.v2 for a declared consumer, and stop. Triggers: "validate", "independently validate", "vibe".
The English summary is being prepared. Showing the original description.
Run a supplied task in headless AGY (Antigravity, Gemini) and collect its result. Use when: AGY, Antigravity or Gemini is requested by name; never a fallback.
The English summary is being prepared. Showing the original description.
Explain why a change, incident or session went as it did, separating proven causes from coincidence. Use when: a postmortem or retro is selected by name.
The English summary is being prepared. Showing the original description.
Interview you one question at a time, each with a recommendation, to settle a big outcome before agents work alone. Use when: selected by name.
The English summary is being prepared. Showing the original description.
Coordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead one. Use when: managing multiple agents.
The English summary is being prepared. Showing the original description.
Dispatch independent tasks to parallel workers or subagents without write collisions. Use when: running or planning agents in parallel, even two; check scopes before any launch.
The English summary is being prepared. Showing the original description.
Run one prompt through headless Codex and capture the result. Use when: wanting a one-shot `codex exec` run or CI step. Not for batches or retries.
The English summary is being prepared. Showing the original description.
Compare independent opinions from several models or contexts without inflating agreement. Use when: wanting a second opinion or debate, or summarizing several reviewers' results.
The English summary is being prepared. Showing the original description.
Draft or lint a bounded long-running goal prompt with a finish line and hard limits. Use when: selected by name; one change goes to Plan.
The English summary is being prepared. Showing the original description.
Write or update READMEs, docs, repo instructions and handoff notes, checked against source. Use when: documenting something, writing a README or leaving a session handoff.
The English summary is being prepared. Showing the original description.
Brainstorm evidence-backed options for what to build, or stress-test an idea. Use when: deciding what to build next, comparing options or testing an idea.
The English summary is being prepared. Showing the original description.
Change or repair code, config or services without weakening tests; report what ran and what did not. Use when: implementing a change or fixing a defect.
The English summary is being prepared. Showing the original description.
Write, find or curate lessons and agent rules with stated evidence and limits. Use when: asked to remember something or write a rule into agent instructions.
The English summary is being prepared. Showing the original description.
Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Use when: planning, breaking down or scoping a change.
The English summary is being prepared. Showing the original description.
Find how a rollout plan could fail before committing to it. Use when: asked what could go wrong or to poke holes in a plan.
The English summary is being prepared. Showing the original description.
Restructure or clean up code with no behavior change, proved by before-and-after checks. Use when: asked to clean up, extract, dedupe or simplify, even one function.
The English summary is being prepared. Showing the original description.
Answer one cited question: how code works, or whether a repeated pattern deserves a rule. Use when: asked how, why, or whether to enforce a pattern.
The English summary is being prepared. Showing the original description.
Tear down a competitor's repo or product into a feature inventory and adoption choices. Use when: comparing us to another tool or asking what to steal.
The English summary is being prepared. Showing the original description.
Give advisory feedback on a plan, design or code change. Use when: asked for an opinion or a look-over, even informally. Not for acceptance; use Validate.
The English summary is being prepared. Showing the original description.
Create, repair, audit or consolidate agent skills (SKILL.md packages). Use when: writing or fixing a skill, its description or structure. Not for one-off lessons; use Memory.
The English summary is being prepared. Showing the original description.