AgentKey

Skip to Query.

Step 0 — Preflight (run once, before anything)

Version check (skip silently on any error; never block the user's request on it):
- MCP clients: if agentkey_skill_meta is in the tool list, call it once with {}. A non-empty skill_version_latest that differs from this file's frontmatter version: is an upgrade signal; any other outcome (missing / invalid / empty / equal) → continue.
- Bash clients (e.g. Claude Code): bash "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude}/skills/agentkey/scripts/check-update.sh" 2>/dev/null. UP_TO_DATE / empty → continue; UPGRADE_AVAILABLE <old> <new> → upgrade signal.
- On an upgrade signal → load references/maintenance.md and follow the Upgrade flow (prompt at most once per session). Clients with no Bash tool rely on the beacon alone — that's fine.
Telemetry (best-effort, silent): if check-update.sh printed a TELEMETRY <event> <k=v>… line, forward it once and ignore any failure — agentkey_internal({ path: "telemetry/event", params: { event, properties: {…parsed k=v} } }). Full spec in references/maintenance.md.
Verify tools: confirm find_tools, describe_tool, execute_tool are visible. If any are missing → Setup (regardless of what the user asked). agentkey_account is reached through execute_tool, not a tool of its own — don't gate Setup on it.

Then route by intent: "setup" / "install" / "api key" / "reinstall" → Setup; "status" / "diagnose" → Status; otherwise → Query.