Workspace Admin Skill

1---
2name: agentclash-workspace-admin
3description: Use when creating or administering AgentClash organizations and workspaces, inviting members, updating roles, or binding default workspace context beyond basic CLI login.
4metadata:
5  agentclash.role: admin
6  agentclash.version: "1"
7  agentclash.requires_cli: "true"
8---
9
10# AgentClash Workspace Admin
11
12## Purpose
13Administer tenancy: organizations, workspaces, memberships, and default workspace binding for teams operating multiple eval environments.
14
15## Use When
16- Creating a new workspace for a team or environment (staging vs prod eval).
17- Listing orgs/workspaces after login to pick the right target.
18- Inviting teammates or changing workspace/org membership roles.
19- Enabling `public_packs` on a workspace or archiving inactive workspaces.
20- Setting default workspace context after auth (when `agentclash link` is not enough).
21
22## Do Not Use When
23- First-time CLI install and device login — use `agentclash-cli-setup` and `agentclash link`.
24- Running evals in an already-selected workspace — use `agentclash-eval-runner`.
25- Managing provider secrets, deployments, or runtime resources — use `agentclash-runtime-resources-setup`.
26
27## Inputs Needed
28- Authenticated CLI session (`agentclash auth login --device` or `AGENTCLASH_TOKEN`).
29- Organization ID for workspace create/list (from `agentclash org list` or saved config).
30- Workspace ID for member admin commands (from `agentclash workspace list` or `agentclash link`).
31- Email addresses and roles for invites.
32
33## Environment
34```bash
35export AGENTCLASH_API_URL="https://api.agentclash.dev"
36agentclash auth login --device
37agentclash org list
38agentclash workspace list --org <organization-id>
39export AGENTCLASH_WORKSPACE="<workspace-id>"
40```
41
42Role values:
43- Org: `org_admin`, `org_member`
44- Workspace: `workspace_admin`, `workspace_member`, `workspace_viewer`
45
46## Procedure
471. Verify auth with `agentclash auth status`.
482. List organizations; create one if needed.
493. List or create workspaces under the org.
504. Set default workspace with `workspace use` or guided `link`.
515. Optionally bind project config with `agentclash init --workspace-id ... --org-id ...`.
526. Invite members and adjust roles/status as the team grows.
537. Run `agentclash doctor` in the target workspace to confirm eval readiness.
54
55## Commands
56
57### Organizations
58```bash
59agentclash org list
60agentclash org get <org-id>
61agentclash org create --name "Acme Eval" --slug acme-eval
62agentclash org update <org-id> --name "Acme Eval Platform"
63agentclash org members list --org <org-id>
64agentclash org members invite --org <org-id> --email user@example.com --role org_member
65agentclash org members update <membership-id> --role org_admin
66```
67
68Alias: `agentclash organization` = `agentclash org`.
69
70### Workspaces
71```bash
72agentclash workspace list --org <org-id>
73agentclash workspace get <workspace-id>
74agentclash workspace create --org <org-id> --name "Staging" --slug staging
75agentclash workspace update <workspace-id> --name "Staging Eval" --public-packs
76agentclash workspace update <workspace-id> --status archived
77agentclash workspace use <workspace-id>
78agentclash link
79```
80
81Alias: `agentclash ws` = `agentclash workspace`.
82
83`workspace use` validates access and saves `default_workspace` (and `default_org` when present) to user config.
84
85Project-local binding:
86```bash
87agentclash init --workspace-id <workspace-id> --org-id <organization-id>
88```
89
90### Workspace members
91```bash
92agentclash workspace members list
93agentclash workspace members invite --email user@example.com --role workspace_member
94agentclash workspace members update <membership-id> --role workspace_admin
95agentclash workspace members update <membership-id> --status suspended
96```
97
98Member commands require a resolved workspace (`--workspace`, `AGENTCLASH_WORKSPACE`, saved config, or project `.agentclash.yaml`).
99
100## Expected Output
101- `workspace create` prints workspace ID and name.
102- `workspace use` / `link` saves defaults and confirms the selected workspace.
103- `members invite` confirms email and role.
104- `--json` on any command returns structured API payloads.
105
106## Failure Modes
107- `organization ID required` on `workspace list` → pass `--org` or set default org via `link` / config.
108- `no workspace specified` on member commands → run `workspace use` or export `AGENTCLASH_WORKSPACE`.
109- `Workspace <id> is not accessible` → token lacks membership; re-auth or pick another workspace.
110- `no fields to update` on update commands → pass at least one changed flag.
111
112## Safety Notes
113- Confirm workspace ID before invites or archival — operations affect the whole team.
114- Prefer `workspace_viewer` for read-only stakeholders; escalate to `workspace_admin` deliberately.
115- Do not share `AGENTCLASH_TOKEN` in tickets or chat; use per-user device login when possible.
116
117## Report Back Format
118```text
119Org: <id> (<name>)
120Workspace: <id> (<name>, <status>)
121Default workspace: <saved id or none>
122Members: <count or n/a>
123Public packs: <enabled/disabled>
124Doctor ready: <yes/no>
125Next: agentclash quickstart OR agentclash eval start
126```
127
128## Related Skills
129- `agentclash-hub`
130- `agentclash-cli-setup`
131- `agentclash-quickstart`
132- `agentclash-runtime-resources-setup`
133- `agentclash-eval-runner`
134
135## Related Docs
136- `/docs-md/getting-started/quickstart`
137- `/docs-md/reference/cli`
138- `/docs-md/reference/config`