agentleFS
awebaiawebai/aweb/skills/aweb-bootstrap/SKILL.md

aweb-bootstrap

Skill129 starsChanged 4 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill only to recognize old bootstrap-era layouts and migrate them to primitive-first setup.

    line 10
  2. Very specific:

    check for .aw/signing.key, .aw/identity.yaml, .aw/teams.yaml, and .aw/team-certs/ under homes/worktrees.

    line 44
  3. Very specific:

    run aw workspace status only from a concrete home/worktree, not from an uninitialized repo root.

    line 46
  4. Very specific:

    create/join teams with aw team admin create, aw team invite, aw team join, or controller-side aw id team ...

    line 50
  5. Very specific:

    create worktrees with git worktree add or the narrower aw workspace add-worktree helper when appropriate.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

aweb Bootstrap (retired command family)

The aw agents bootstrap / aw agents ... command family has been retired. Use this skill only to recognize old bootstrap-era layouts and migrate them to primitive-first setup. Do not instruct users to run aw agents ....

For new setup, use:

  • aweb-team-membership for invites, joins, certificates, switching, and hosted vs BYOT authority decisions;
  • aweb-identity for local/global identity state, custody, keys, and address claims;
  • ordinary git worktree / filesystem operations for worktrees and copied resources;
  • team blueprints / resource packs for reusable roles, instructions, skills, and harness adapters.

How to recognize an old bootstrap layout

Legacy repos may contain:

agents/
  team.yaml
  docs/
  roles/
  home/<responsibility>/AGENTS.md
  worktrees/<name>/

Some homes or worktrees may contain ignored .aw/ state and signing keys. Treat that state as private identity material. Never delete it casually.

Safe recovery policy

  1. Inspect before mutating:
    • list agents/team.yaml, agents/home/*, agents/worktrees/*;
    • check for .aw/signing.key, .aw/identity.yaml, .aw/teams.yaml, and .aw/team-certs/ under homes/worktrees;
    • run aw workspace status only from a concrete home/worktree, not from an uninitialized repo root.
  2. Back up any .aw/ directory before moving or deleting a legacy home.
  3. Recreate needed workspaces with current primitives:
    • create/join teams with aw team admin create, aw team invite, aw team join, or controller-side aw id team ... primitives;
    • connect existing certs with aw init, aw workspace connect, or aw service init;
    • create worktrees with git worktree add or the narrower aw workspace add-worktree helper when appropriate.
  4. Apply reusable resources from current team blueprints / resource packs rather than treating old team.yaml as authority.

Migration guidance

  • Roles and instructions from agents/roles/ and agents/instructions.md can be copied into a resource pack or applied explicitly with aw roles / aw instructions.
  • Per-agent startup text from agents/home/<responsibility>/AGENTS.md can move into blueprint profile instructions or a manually maintained home.
  • Final names, DIDs, addresses, certificates, and .aw state must remain local runtime state; do not commit them into resource packs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.