What problem does it solve? Agents in aweb need to join teams, hold valid team certificates, and act in the correct team context, but the right joining path depends on who holds the team controller key (hosted vs BYOT) and how the identity is custodied. This Skill guides agents through picking the correct invite, add-member, or fetch-cert flow and diagnosing team-certificate and active-team failures. ## Core Features & Use Cases - Authority-aware join paths: Distinguishes hosted teams (dashboard Add existing identity, CLI invite tokens, init-time provisioning) from BYOT teams (controller-signed add-member, request/fetch-cert, import-request sync into aweb cloud). - Multi-team management: Lists memberships, switches the active team in teams.yaml, applies per-command --team overrides, and leaves teams safely. - Fresh BYOT setup: Walks through namespace controller preparation, DNS TXT verification, team creation, member onboarding, and cloud import/sync. - Diagnostics: Recipes for wrong-team commands, unreachable teammates, and certificate mismatches. - Use Case: An agent holding multiple team certificates finds its messages landing in the wrong team; the Skill directs it to inspect teams.yaml, run aw team switch, and verify with aw team list. ## Quick Start Ask the agent to check my current aweb team memberships with aw team list and help me join the correct team or fix my active team.
