← PresetCONTENT HISTORY
WHAT CHANGED
Update to Preset
Snapshot Oct 24, 2026 · 13:46 UTC · version 0.1.4
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Preset and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Troubleshoot Superset MCP health, validation, permission, response-size, and bug-report workflows. Use only for MCP tool workflows; do not use for direct API work.",
"included_files": [
{
"relative_path": "references/troubleshooting.md",
"size_in_bytes": 942
}
],
"name": "preset-mcp-troubleshooting",
"skill_md_contents": "---\nname: preset-mcp-troubleshooting\ndescription: Troubleshoot Superset MCP health, validation, permission, response-size, and bug-report workflows. Use only for MCP tool workflows; do not use for direct API work.\n---\n\n# preset-mcp-troubleshooting\n\nUse when Superset MCP tools fail, return validation errors, return permission errors, or produce oversized responses.\n\n## Always\n\n- Stay on MCP troubleshooting; do not switch to direct APIs.\n- Use `health_check` first for service availability.\n- Use `generate_bug_report` when the user says MCP is broken or asks how to report an issue.\n- Treat permission denied as authoritative.\n- No permission workaround: do not search alternate tools, REST APIs, or direct APIs to expose restricted data.\n- Use live tool schemas to fix validation errors.\n\n## Decision Rules\n\n- Connection or availability issue: `health_check`.\n- Tool parameter/schema issue: inspect the live tool schema and retry only with corrected MCP arguments.\n- Permission issue: explain the denied operation and stop; do not search for alternate tools to expose restricted data.\n- Response too large: rerun with narrower filters, identifiers, page sizes, or row limits.\n- Repro/report request: `generate_bug_report`.\n\n## Workflow Order\n\n1. Classify the failure: availability, validation, permission, unsupported capability, oversized response, or unknown error.\n2. Use the smallest diagnostic MCP tool.\n3. Explain the failure in user terms.\n4. For permission denied, stop or generate bug report when requested.\n5. Stop before direct API or REST API calls.\n6. Retry only when the correction is clear and remains on MCP.\n\n## Retrieve\n\n- Troubleshooting guide: [references/troubleshooting.md](references/troubleshooting.md)\n"
}SHA-256 of public snapshot: fa18c46ce5d2884d3e68f043e71cb522a18ea5808cf8883131ac1151c90e48cf