---
name: capabilities-here
description: Use when grounding any claim about what is installed on the current account — enabled plugins, available specialists, registered Claude Code agent types, brand, tier, models. Call the `capabilities-here` tool; the JSON it returns is the authoritative install snapshot. Never infer install state from the platform-architecture skill (that skill is the install catalogue, not evidence of what is enabled here).
---

# capabilities-here

The `capabilities-here` admin MCP tool returns a single JSON object describing the live install state on the current account. Call it whenever you are about to:

- Tell the operator what you can or cannot do here.
- Decide whether a specialist exists before dispatching it.
- Say which plugins are available on this account.
- Compare the install against a catalogue claim from `platform-architecture`.

## How to use

Call `mcp__plugin_admin_admin__capabilities-here` with no arguments. The tool reads:

- `account.json` for `enabledPlugins`, `tier`, `adminModel`, `publicModel`.
- `brand.json` for `productName` and `shipsPremiumBundles`.
- `platform/templates/specialists/agents/` for `installedPlatformSpecialists`.
- Each enabled premium bundle's `agents/` for `installedPremiumSpecialists`.
- `$CLAUDE_CONFIG_DIR/agents/` for `registeredAgentTypes` (the same registry the Agent tool resolves against).

Returns one JSON object with those fields plus `accountId`, `capturedAt`, and the `brand` block. No LLM in the resolution path; pure disk + JSON reads.

## Boundary against `platform-architecture`

`platform-architecture` is the install catalogue — every plugin, skill, and specialist the platform can ship. It is not evidence that any of them is enabled here. For documented surface (how a plugin works, what a role is for) cite `platform-architecture` with the `Source:` URL. For what is actually installed on this account, cite `capabilities-here`.

When the operator asks "what can you do" or "what plugins are enabled" or "do you have X", the answer comes from `capabilities-here`, not from this skill or from `platform-architecture`.
