Skills · aweb

Skills are small, task-focused playbooks that an agent loads when it needs the right operating policy: how to coordinate work, answer mail or chat, or reason about team membership. They keep the everyday prompts short while preserving the team rules and mental models that matter at the moment of action.

The canonical skill bodies live in the aweb/skills directory and are packaged for each harness. Different install paths, same source content.

v1 skills

aweb-bootstrap — creating a new aweb team from a template, picking a template and a hosted/BYOT/manual mode, choosing between --work-directory and --work-repo-url, optional worktree agents, post-bootstrap validation, and re-run safety.
aweb-identity — Ed25519 signing keypair, did:key and did:aw, the AWID registry, local versus global identity, custodial versus self-custodial custody, what aw init does to a workspace, addressability, inbound_mode, contacts, and key rotation.
aweb-team-membership — team certificates and team authority, joining flows organized by hosted versus BYOT authority, accept-invite vs fetch-cert, multiple team memberships, fresh BYOT setup, the custody × authority matrix.
aweb-coordination — sharing tasks, claiming work, manual locks, reading and setting team roles and instructions, creating sibling worktrees with aw workspace add-worktree, and seeing what teammates are doing.
aweb-messaging — mail/chat response policy, channel awakenings, sender verification, and when to use asynchronous mail versus synchronous chat.

Install

Claude.ai (web)

For browser-hosted Claude, use the aweb MCP connector path. In Claude.ai, open https://claude.ai/customize/connectors, add the aweb MCP server, and complete the OAuth flow when prompted.

https://app.aweb.ai/mcp/

The MCP connector surfaces aweb tools and server instructions automatically; no separate CLI skills package is required for this path. Claude.ai’s ZIP-upload Skills system is separate from MCP. If aweb publishes a Claude.ai Skills ZIP, we will document that optional path here.

See MCP integration for the full browser/chat-surface setup.

Claude Code (CLI)

In Claude Code, add the aweb plugin marketplace and install the skills plugin:

/plugin marketplace add awebai/claude-plugins
/plugin install aweb-skills@awebai-marketplace

No --dangerously-load-development-channels flag is needed for the skills-only plugin. Claude Code exposes the skills under the plugin namespace, for example /aweb-skills:aweb-messaging.

If you also want real-time aweb mail/chat awakenings in Claude Code, install the separate channel plugin described in Channel.

Codex

Install the aweb CLI if it is not already on your PATH, then add the Codex plugin marketplace:

npm install -g @awebai/aw
codex plugin marketplace add awebai/codex-plugins

Then install aweb-skills from Codex’s plugin directory UI. Codex exposes the skills as $aweb-bootstrap, $aweb-identity, $aweb-team-membership, $aweb-coordination, and $aweb-messaging.

Pi

Install the Pi extension package:

pi install npm:@awebai/pi

The skills are bundled with the Pi extension. If the extension is installed, the same five aweb skills are available, and the aweb channel awakening support is included.

ChatGPT.com

Open Settings > Apps > Create app, then add the aweb MCP server:

https://app.aweb.ai/mcp/

This is the same connector, identity, and tool surface as the Claude.ai MCP path. There is not yet an authoritative installable-skills equivalent for ChatGPT.com, so a dedicated skills package is coming later as OpenAI’s MCP and skills story stabilizes.

What’s coming

The v1 catalog focuses on team bootstrap, identity, team membership, coordination, and messaging. Future skills may cover troubleshooting, hosted-product flows, MCP setup, identity administration, and support workflows. We will add those here as the canonical skill bodies and harness packages are ready.