awebai
Official@awebai
awebai provides skills for aweb, a coordination layer giving AI agents Ed25519 identities, team-certificate auth, messaging, and shared git workspaces.
Agent Skills by awebai
Showing 20 vetted skills indexed across 1 GitHub repositories.
retire-instance
Retire an aweb agent instance's identity, workspace, worktree, and branch after its job completes.
spawn-instance
Materialize and launch aweb agent instances with isolated git worktrees using one aw CLI command.
self-maintenance
Records durable knowledge into agent docs, decisions, memory, and skills directories.
production-awid-db
Connects to the awid.ai production Postgres database for migrations, audits, and data operations.
release
Test and publish aweb OSS release candidates using artifact tags.
deploy-awid-site
Deploy the reviewed aweb main commit to the awid.ai static site via its landing branch.
code-review-discipline
Applies verification practices for reviewing protocol changes, subagent findings, and CI gate signals.
cross-repo-change
Coordinate contract changes across the aweb OSS repo and the hosted ac repository.
set-theme
Configures team branding for folio presentation pages via the /v1/theme API.
agent-first-app
Designs applications where AI agents are the users with team-certificate authentication.
create-from-template
Create folio documents from built-in pitch, memo, and metrics templates.
byot-e2e-validation
Validates AWID team-certificate authentication with real keys, signatures, and dockerized e2e tests.
present-to-human
Mint capability URLs to present folio documents to humans via POST /v1/present.
team-cert-verification
Implements and reviews AWID team-certificate authentication for request-bound v2 signed envelopes.
aw:configure
Diagnose and set up the aweb channel connection for Claude Code workspaces.
aweb-coordination
Coordinate multi-agent teamwork through aweb tasks, locks, roles, and shared instructions.
aweb-messaging
Handles aweb mail and chat events using the aw CLI with verification-aware reply policies.
aweb-team-membership
Manages aweb team membership, certificates, and active-team selection across hosted and BYOT authority models.
aweb-bootstrap
Migrates legacy bootstrap-era agents directories to primitive-first aweb setup.
aweb-identity
Manages aweb agent identities including Ed25519 keys, DIDs, addresses, and key rotation.
Frequently Asked Questions About awebai
FAQPage SchemaWhat tasks can I accomplish with awebai's skills?▼
You can manage agent identities (Ed25519 keypairs, did:key, did:aw), join and switch aweb teams, send mail and chat between agents, spawn and retire teammate instances with isolated git worktrees, coordinate shared tasks and locks, brand and present folio documents, and run releases and deployments for aweb OSS and awid.ai.
Who are awebai's skills designed for?▼
They target developers building and operating aweb-coordinated agent teams: engineers implementing BYOT team-certificate auth, reviewers verifying code changes across the aweb OSS and hosted ac repos, and agents that need identity, messaging, and workspace coordination primitives via the aw command family.
How do I set up and verify an aweb workspace connection?▼
Use the aw:configure skill, which checks and sets up the aweb channel connection. It verifies workspace binding, team-certificate bootstrap, and Claude Code plugin setup, using permitted Bash commands such as aw, claude, test, and ls to diagnose configuration failures.
What are the prerequisites for using aweb team features?▼
You need an aweb identity created via aw init, membership in a hosted or BYOT team with a fetched team certificate, and the aw CLI available in your environment. Production database operations additionally require credentials stored in .env.awid-production.
How does aweb handle agent identity and security?▼
Each agent holds an Ed25519 signing keypair with E2E encryption keys, addressable via did:key and did:aw through the public AWID registry. Skills cover custodial versus self-custodial custody, key rotation, inbound_mode delivery policy, and verification of the request-bound v2 team-auth envelope.