scenario-team-admin SKILL.md skillA
scenario-team-admin from scenario-labs/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add scenario-labs/skills/scenario-team-admin@git:20260915.8d41021Pins git:20260915.8d41021 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- scenario-labs/skills
- Path
skills/scenario-team-admin/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260915.8d41021, committed Sep 15, 2026
- Size
- 13,294 bytes
- Repository stars
- 1,063
- License
- MIT
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, 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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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` skill. If a sibling skill named here is missing from your available skills, ask the user to install it (`npx skills add scenario-labs/skills --skill <name>`)…
…Read the whole file at its exact version.
How to install
mdr add scenario-labs/skills/scenario-team-admin@sha256:6b9c8558a03edab5The line at the top of this page pins the label git:20260915.8d41021, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qnmzvrvtol27lktq)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 15, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13294 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
scenario-labs/skills · 1,063 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qnmzvrvtol27lktq GET https://markdownregistry.com/api/v1/resolve?ref=scenario-labs/skills/scenario-team-admin GET https://markdownregistry.com/api/v1/blob/6b9c8558a03edab5461a1c8349c176a3004fc9e3b7b1aaa99b11d0cbcf78a2e7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.