What is staircase-team-manager?

A live team roster for customer-success leaders, built from Staircase data. It shows who owns each customer group, the size and risk of their workload, available capacity, and upcoming renewals or expansion opportunities.

Use it to review workload across the team, spot overloaded or underused capacity, and prepare for team check-ins. It also helps identify renewal and expansion work that needs attention.

It replaces separate dashboard checks and manual spreadsheets with one consistent view of team coverage. Leaders can see which teammates may need help and where the business is exposed.

staircase-team-manager — Skill for Claude Code by gs-bbluhm

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add gs-bbluhm/gainsight-mcp-plugins

Claude Code

/plugin install staircase

Made for: Claude Code.

Or install staircase, the plugin that ships this one along with the rest of its 14 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-team-manager/github.svg)](https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-team-manager)

Your own site

<a href="https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-team-manager"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-team-manager/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-team-manager"><img src="https://agentmods.dev/badge/skills/gs-bbluhm/gainsight-mcp-plugins/staircase-team-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 136 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,773 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00136	$0.03773
Opus 5.5	$0.00054	$0.01509
Sonnet 5.5	$0.00027	$0.00755
Haiku 4.5	$0.00014	$0.00377

Measured 25d ago against content hash a4d8c35bf10b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

staircase-team-manager scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 25d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/staircase/skills/staircase-team-manager/SKILL.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Staircase Team Manager (leader / across-team)

A manager does not need ten dashboards. They need one roster: who holds a book, how big it is, how exposed it is, who's stretched, and what's coming up, so they know who needs them this week. This skill builds that roster live from the Staircase MCP (user, customer, expansion_opportunity), ports a workload/coverage methodology validated internally (the overwhelmed test, the anti-libel under-utilization read, book rollup), and hands the crunching to a bundled script so the model spends its intelligence on interpretation, not re-deriving percentiles every run.

This is the across-team lens. To prep for a 1:1 with one teammate, use ../staircase-1on1-prep/. For portfolio risk independent of who's carrying it, use ../staircase-risk-radar/.

Foundation references (read BEFORE composing any query)

../staircase-mcp-expert/SKILL.md step 0 (the first-call contract): resolves the book-owner field per org. customer.owner is not always the CSM; use the resolved field for everything below.
../staircase-mcp-expert/references/report-recipes.md: team.rollup and scope.membership.
../staircase-mcp-expert/references/advanced-report-patterns.md: the argument system (§1), rollups with a discovered role field as the referenceField (§7), and teams via user.manager (§9). Prefer In for multi-value filters (anti-patterns.md R6).
../staircase-app-design/: the interactive-cockpit standard (see the visual section below).
../../_shared/staircase-output-best-practices.md: house style, evidence discipline, no CRM writes.
User profile (if present): ~/.staircase-mcp/user-profile.md carries the resolved book-owner field (scope.book_owner_field).

Scope (decide first)

Use the resolved book-owner field. Read scope.book_owner_field from the profile; if absent, run the foundation's first-call contract (scope.membership), which computes it and asks only when a person sits in two role fields. Never assume Owner.
Resolve the team. Try user.manager.full_name Equal "<manager's name>" first (a single Equal: clean, confirmed working, no fan-out). If the org's Manager field is sparse/unpopulated, fall back to an explicit roster the manager names, scoped with user.full_name In [...] (also confirmed working in one call).
Portable fields only. The confirmed book-owner field is a runtime parameter (from step 1); never hardcode a specific _c id.

Read the full file on GitHub · 149 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

experiences/team-roster.widget.html 16 KB

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

25d ago First seen · 149 lines · 136 tokens per session scan A a4d8c35bf10b

Subscribe to this mod's changes

staircase-team-manager is a skill published in the GitHub repository gs-bbluhm/gainsight-mcp-plugins (4 stars, last pushed 20d ago), licensed MIT. It adds 136 tokens to every session and 3,773 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-26.

Analytics and metrics

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens