Menu

Individual skill

scenario-team-admin

0upvotes

Use when administering a Scenario team from an agent through MCP: restricting which models a team or project can run (model access control, allowlist, blocklist), inviting or removing team and project members, changing roles, capping a member's Creative Unit spend, creating or deleting projects, auditing API keys and their roles or scopes, or attributing consumption per user or model. Keywords: governance, model control, consumption cap, spend limit, API key hygiene, team admin, enterprise.

skills/scenario-team-admin/SKILL.md

Read pinned source

Source commit f29bf06ab89088695ed3431ac99d20a090441a2f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,670
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Scenario Team Administration

## Overview

Enterprise teams govern Scenario from the same agent that generates on it: which models anyone may
run, who is on the team and in which projects, how much each member may spend, and which API keys
exist with which roles. Every tool here is catalog-only: `scenario_tools_search` returns the schema
and lane, and `scenario_tool_execute_read` / `write` / `delete` runs it with `{name, parameters}`,
scope ids inside `parameters` (see the `scenario` skill). Two facts decide most failures before any
argument does: the identity behind the call, since team-level writes need a human team admin over
OAuth and refuse API keys, and the list mode the team runs, since the same model-access edit means
the opposite thing in blocklist and allowlist mode. `teams_list` already tells you both: each team
row carries `modelsManagement`, its model lists, `plan`, and `context.userRole`. A credential that
reaches one team and one project has its scope; more than one is a stop-and-list, per the `scenario`
Back to top