{"id":18364,"plugin_id":"plugins_6a88e6256bb48191a343d39dace5e05c","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:14:47.624Z","digest":"7b9ae62f87fd086c1b33f12007bf23e52b73e8f667379c8a3bc44f7915e2cd0f","against":null,"payload":{"description":"Diagnose MCP connector failures by separating stored connection state from live upstream tool evidence.","included_files":[],"name":"mcp-debugging","skill_md_contents":"---\nname: mcp-debugging\ndescription: Diagnose MCP connector failures by separating stored connection state from live upstream tool evidence.\nallowed-tools: Read Glob Grep Bash\nargument-hint: '[--connector <name>]'\neffort: medium\n---\n\n# MCP Debugging\n\nUse when an MCP connector, tool, token, or upstream integration appears connected but behavior fails.\n\n## Principles\n\n- Stored connection state is not proof that the upstream service accepts the token/session.\n- Prefer a live tool call or minimal endpoint check that exercises the failing capability.\n- Capture exact error codes, tool names, timestamps, and sanitized payloads.\n- Never expose secrets, tokens, cookies, or auth headers.\n\n## Output\n\n```markdown\n## MCP Debug Report\n\n**Connector:** <name>\n**Claimed state:** <configured/active/unknown>\n**Live check:** <command/tool and result>\n**Root cause:** <best-supported cause or unknown>\n**User action needed:** <reconnect, grant permission, rotate token, none>\n**Evidence:** <sanitized snippets>\n```\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}