菜单
Use when creating, updating, or explaining a standing Repowire agent folder, worker folder, durable-job executor context, or reusable agent-specific AGENTS.md guidance.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Parallel divergent ideation via mesh fan-out. Spawns N frame-shifted peers, scores results, deepens top survivors. Use on open-ended design choices, fuzzy bugs, naming, API surfaces, or explicit /adhd invocation. Skip for syntax, lookups, or closed prompts ("quick", "standard", "canonical").
Get an independent implementation plan from a DIFFERENT AI agent over the repowire mesh before you build (e.g. have Gemini or Codex draft an approach for Claude to critique). Use when you want a second perspective on how to approach a task.
Get a code/PR/plan review from a DIFFERENT AI agent over the repowire mesh (e.g. have Codex review Claude's work). Use when you want an independent second opinion from another backend before merging or committing.
Hand a task to another AI agent peer over the repowire mesh — reuse an existing peer on the chosen backend, or spawn one if none exists. Use when you want to offload work to a specific agent (e.g. delegate a refactor to a Codex peer) and track it to completion.
Install or update repowire and its skill pack from inside an agent session — ensure the repowire CLI/hooks are set up, install the skills, and verify the mesh works. Use on a fresh machine or to refresh skills to the latest.
Reference for how to use the repowire mesh — ask/ack vs notify, broadcast, peer discovery, spawning, and cross-agent workflows. Use when you need to coordinate with other AI agents over repowire and want the right primitive for the job.
| name | create-agent |
| description | Use when creating, updating, or explaining a standing Repowire agent folder, worker folder, durable-job executor context, or reusable agent-specific AGENTS.md guidance. |
Use an agent folder when a repeatable worker needs standing context: domain rules, tool expectations, privacy boundaries, output format, or durable-job instructions.
Agent folders are a convention, not a registry. Jobs and spawns still target --path --backend [--profile].
repowire agents create <name> --backend <runtime>
The command creates .repowire/agents/<name>/AGENTS.md. For Claude Code it also creates CLAUDE.md as a shim. Other supported runtimes load AGENTS.md directly.
Keep it specific to the worker:
Do not store secrets, personal tokens, absolute machine paths, or one user's private service assumptions in a shipped template.
Use the folder as the durable execution context:
repowire jobs create "Daily brief" \
--path "$(pwd)/.repowire/agents/daily-brief" \
--backend codex \
--cron "0 8 * * *" \
--prompt "Prepare the brief and update this job with the result."
If the worker is only a one-off prompt with no standing context, create a normal job instead of an agent folder.