aweb-bootstrap

Migrates legacy bootstrap-era agents directories to primitive-first aweb setup.

82|9|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/awebai/aweb --skill aweb-bootstrap-awebai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aweb-bootstrap
Source: https://github.com/awebai/aweb/tree/main/packages/codex-plugin/skills/aweb-bootstrap
Command: npx skills add https://github.com/awebai/aweb --skill aweb-bootstrap-awebai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Older aweb projects contain legacy agents/ directories created by the retired aw agents command family, and teams need a safe way to recognize, recover, and migrate those layouts without losing signing keys or team certificates. ## Core Features & Use Cases - Legacy Layout Recognition: Identifies bootstrap-era structures such as agents/team.yaml, agents/roles/, agents/home/<responsibility>/AGENTS.md, and agents/worktrees/. - Safe Recovery Policy: Inspects .aw/ identity state, backs up signing keys and team certificates, and avoids running retired aw agents commands. - Migration Guidance: Recreates workspaces with current primitives like aw team invite, aw team join, aw init, aw workspace connect, and git worktree add, moving reusable roles and instructions into team blueprints or resource packs. - Use Case: You clone an old repository containing an agents/ directory with per-agent homes and worktrees; this skill walks you through inventorying identity state, backing it up, and rebuilding the setup with current aweb primitives. ## Quick Start Ask the assistant to inspect the legacy agents directory in this repository and plan a safe migration to current aweb team and workspace primitives.

Frequently Asked Questions about aweb-bootstrap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a legacy aweb agents directory to the new setup?

Inventory agents/team.yaml, roles, docs, and each home or worktree, then back up all .aw/ state including signing keys and team certificates. Recreate workspaces with aw team invite, aw team join, aw init, or aw workspace connect, and move reusable roles into team blueprints or resource packs.

Can I still run aw agents bootstrap commands?

No, the aw agents command family is retired and should not be run. Use current primitives like aw team admin create, aw team invite, aw team join, aw init, and git worktree add instead.

How do I recognize an old bootstrap-era aweb layout?

Look for an agents/ directory containing team.yaml, docs/, roles/, home/<responsibility>/AGENTS.md, and worktrees/<name>/. Homes or worktrees may also contain ignored .aw/ state with signing keys and identity files.

Is it safe to delete .aw directories in old aweb worktrees?

No, .aw/ directories hold private identity material such as signing.key, identity.yaml, teams.yaml, and team-certs. Always back them up before moving or deleting a legacy home, and never delete a signing key or team certificate.

Should agents/team.yaml be treated as team membership authority?

No, team authority lives in hosted service state or AWID controller-signed certificates, not in team.yaml. For hosted teams use invite or dashboard flows; for BYOT teams only the controller holder signs certificates.