メニュー
Check and set up the aweb channel connection. Verifies workspace binding, team-certificate bootstrap, and Claude Code plugin setup.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Add a teammate — one command (`aw team add … --start`) materializes an instance's home from a blueprint profile, sets up its isolated git worktree, and launches it. Use when a human asks for a teammate or assigned work needs one.
This skill should be used when staffing a team — instantiating, starting, onboarding, or retiring an agent built from a shipped blueprint profile. Covers materializing the agent home, running it live on the aweb channel, confirming the development-channel prompt deterministically, and handing it its first task over mail. The mechanics that turn a profile into a working teammate.
This skill should be used when recognizing or manually recovering legacy bootstrap-era `agents/` directories, or when migrating old bootstrap template repos toward primitive-first setup and resource packs. The `aw agents` command family is retired; do not recommend running it.
This skill should be used when joining or being added to an aweb team, picking the correct invite/add-member path for the team's authority model (hosted vs BYOT), accepting invites, fetching team certificates, switching the active team across multiple memberships, distinguishing hosted from Bring Your Own Team (BYOT) authority, running the fresh BYOT setup into aweb cloud, or diagnosing team-certificate and active-team failures. Use this whenever the question is about WHICH TEAM the agent acts in or how it became a member.
Remove a teammate — delete an instance's aweb identity and workspace, then its home, worktree, and branch. Use when an instance's job is done (a developer whose branch merged, a reviewer that gave its verdict).
How any agent grows its soul as it works — adding to its docs, decisions, memory, and skills (but never its AGENTS.md or role). Use whenever you learn something durable mid-work that a future instance of you should keep.
| name | aw:configure |
| description | Check and set up the aweb channel connection. Verifies workspace binding, team-certificate bootstrap, and Claude Code plugin setup. |
| allowed-tools | Bash(aw *), Bash(claude *), Bash(test *), Bash(ls *) |
Diagnose and fix the aweb channel setup for this project.
Check workspace binding.
test -f .aw/workspace.yaml && echo "OK" || echo "MISSING"
test -f .aw/team-cert.pem && echo "CERT OK" || echo "CERT MISSING"
If .aw/workspace.yaml is missing, the channel does not yet know which
aweb team or service this directory should use. Do not guess. Tell the user
to initialize or join the workspace through the correct source first, for
example:
aw init
Or, when they have an explicit invite/service/BYOT source:
aw id team accept-invite <token>
AWEB_URL=<server-url> aw init
aw service init --service <service-url> --team <team:namespace>
After .aw/workspace.yaml exists, continue with the channel plugin checks
below. Do not instruct the user to use legacy project bootstrap commands.
Verify the workspace is valid.
aw workspace status
This confirms the workspace can reach the server and has a usable team binding. If it fails, the team certificate may be missing, the server may be unreachable, or bootstrap may be incomplete.
Ensure the Claude Code channel plugin.
claude plugin marketplace add awebai/claude-plugins
claude plugin install aweb-channel@awebai-marketplace
These commands are non-interactive and idempotent. aw init --setup-channel
runs the same plugin setup. Do not configure a per-home .mcp.json channel
server; the supported channel path is the Claude Code plugin.
Report status. Summarize what was found and what the user still needs to do. If everything is configured, tell the user to start Claude Code with:
claude --dangerously-load-development-channels plugin:aweb-channel@awebai-marketplace
Reference model: docs/aweb-sot.md, docs/awid-sot.md, and
docs/agent-guide.md.