// List all AI API keys for the current team. Shows key aliases, masked key values, and spend per key. Use when a team member asks about their API key or wants to see who has access.
Use when the user wants to fix a Sentry issue, auto-repair a bug from Sentry, or create a fix PR for a Sentry error. Triggers on "修复 sentry", "fix sentry issue", "sentry 修复", "sentry fix".
Use when the user wants to check Sentry issues, run a Sentry daily report, or monitor error trends. Triggers on "sentry 监控", "sentry 日报", "查看 sentry", "sentry report", "sentry monitor".
Create a workspace role that follows the ROLE.md specification. Use when the user wants to create a new role, refine a role definition, or turn repeated responsibilities into a reusable routed role.
Control Windows desktop applications: open/operate apps, click controls, type text, scroll, keyboard shortcuts, window management, toggle options, lists and combos, etc. Note: NEVER invoke this skill for opening web pages/visiting websites — use browser-related tools instead. Trigger words: open app, operate app, control computer, click, type, scroll, switch, dropdown, select, modify, change to, set, check, uncheck, app-control, toggle.
Manage AI API keys and budget for the current team. Owner-only operations include adding/removing member keys and setting budget limits. Use when the team owner wants to manage AI access.
Check AI usage and spend for the current team or individual member. Shows total spend, per-member breakdown, or personal usage. Use when someone asks about costs, budget, or how much has been used.
| name | ai-keys |
| description | List all AI API keys for the current team. Shows key aliases, masked key values, and spend per key. Use when a team member asks about their API key or wants to see who has access. |
List all AI API keys for the current team via the FC /ai/keys endpoint.
/ai/setup-team called during team creation)Read the team config from .teamclaw/teamclaw.json to get oss.team_id and oss.team_endpoint, then load the team secret from the system keyring.
# Read team config
TEAM_ID=$(cat .teamclaw/teamclaw.json | jq -r '.oss.team_id')
TEAM_ENDPOINT=$(cat .teamclaw/teamclaw.json | jq -r '.oss.team_endpoint')
# The team secret is stored in the system keyring under service "teamclaw-team" account "{team_id}"
# It should be retrieved programmatically by the client
curl -s -X POST "${TEAM_ENDPOINT}/ai/keys" \
-H "Content-Type: application/json" \
-d "{\"teamId\": \"${TEAM_ID}\", \"teamSecret\": \"${TEAM_SECRET}\"}"
{
"teamId": "tc-abc123",
"keys": [
{
"key": "sk-tc-abcd...",
"alias": "alice-abcdef01",
"spend": 0.0387,
"created_at": "2026-03-25T12:00:00Z"
}
]
}
Present the keys in a readable table format:
| Member | Key (masked) | Spend |
|---|---|---|
| alias | sk-tc-xxxx... | $0.04 |