box team

box-team

Manage team subtrees in a workspace. Create, list, inspect, find cross-team duplicate slugs, or remove a team from config. Box folder ACLs are the real isolation boundary — this skill creates filesystem structure only.

Usage

/box-team <subcommand> [name]

Subcommands:

• create <name> — add a new team subtree
• ls (or list) — list teams + memory counts
• inspect <name> — show what's in a team
• conflicts — find duplicate slugs/titles across teams
• remove <name> — remove team from config (confirms twice; preserves files)

If no subcommand, defaults to ls. If just a name with no subcommand, defaults to create <name>.

Create flow

1. Validate name (kebab-case)
2. Check not duplicate
3. Create folders: teams/<name>/memories/, teams/<name>/files/, teams/<name>/companions/ (if folder layout)
4. Seed _index.json per folder
5. Update _box-memory.json.teams[]
6. Surface the access-control reminder prominently: "Box folder ACLs (not frontmatter) are what actually enforces isolation. Set sharing settings in Box web UI."

Conflicts detection

Reads every accessible team's _index.json. Reports:

• Same slug in multiple teams (likely same concept written separately)
• Same title in multiple teams (different slugs, same concept)

Doesn't auto-resolve. Surfaces for the user to decide:

• Reconcile to shared workspace memory
• Rename one slug to be team-specific
• Leave as-is (different teams genuinely care about the same topic)

Remove flow (cautious)

1. Confirm twice
2. Remove from _box-memory.json.teams[] + folder_ids.team_<name>_*
3. Does NOT delete files — they stay in Box untouched
4. Optionally moves the team folder to _archive/teams/<name>/

Why frontmatter team: is a hint, not enforcement

In v0.1.0, agents respect the team scope via folder lookup. But the field itself isn't access control — a user with read access to the folder sees everything regardless of team: value. Box folder ACLs are what enforces access.

When to use

• New team onboarding to the workspace
• Cross-team duplicate audit
• Reorg / shutting down a team's workflow

See also

• Architecture — folder-ACL isolation rationale
• Schema — workspace config teams[] and folder_ids
• Source: skills/box-team/SKILL.md