メニュー
Use when adding, updating, splitting, or reviewing local orchestrator skills for reusable procedures, including controlled self-improvement of the orchestrator.
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-skill |
| description | Use when adding, updating, splitting, or reviewing local orchestrator skills for reusable procedures, including controlled self-improvement of the orchestrator. |
Use a skill when a procedure is reusable, conditional, and too detailed for always-loaded AGENTS.md.
Do not add a skill for one-off status, a current project decision, a private user workflow, or a rule that belongs in comms.md, projects.md, memory, or a project-local agent file.
Create ./.agents/skills/<name>/SKILL.md with required frontmatter:
---
name: <name>
description: Use when ...
---
# <Title>
The description is the trigger surface. Make it concrete enough that an agent can load the skill only when relevant.
Ship general mechanics: delegation, review cycles, durable jobs, handover, worktree isolation, cleanup.
Keep local-only: project-specific routing, named personal channels, account assumptions, private credentials, customer-specific policy, or personal release authority.
If a skill starts mixing both, split it: product-general guidance in the shipped skill, user-specific preferences in local memory or local-only skills.