{"id":80805,"plugin_id":"plugin_asdk_app_6ad755ddd8708191a403476ad8de769e","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T12:09:49.211Z","digest":"623ba9bcdd6623fbf88e9b66eec19514950c2c005957c902a20bb15df616dff0","against":null,"payload":{"description":"Diagnose Extract failed syncs, run errors and stale ingestion. Hand off approved configuration fixes to setup, requested reruns to operations and business metric explanations to analysis.","included_files":[],"name":"control-extract-diagnostics","skill_md_contents":"---\nname: control-extract-diagnostics\ndescription: Diagnose Extract failed syncs, run errors and stale ingestion. Hand off approved configuration fixes to setup, requested reruns to operations and business metric explanations to analysis.\n---\n\n# Control Extract Diagnostics\n\nUse this skill when the user asks why an Extract pipeline failed, wants failed\nor unhealthy connections, or asks for run diagnostics. Inventory-only requests\nand manual run requests belong to operations.\n\nAll skills share the unified Extract MCP server:\n\n- `extract` at `https://api.extract.to/mcp`, displayed as Extract.\n\nExtract documentation: https://docs.extract.to/\n\n## Tools\n\nUse these `account_*` tools:\n\n- `account_search_connections` - find failed, unhealthy, or matching pipelines.\n- `account_get_connection` - inspect one pipeline before diagnosis or run control.\n- `account_list_connection_runs` - inspect recent run history.\n- `account_diagnose_connection` - read failure diagnostics from recent run logs.\n- `account_trigger_run` - trigger a manual run only after explicit user confirmation.\n\n## Workflows\n\n### Find Failed Connections\n\nUse the `account_search_connections` tool on `extract` with `status=\"ERROR\"` when the user\nasks for failed, failing, broken, or unhealthy pipelines.\n\nIf the user asks why a pipeline failed, identify the exact connection first,\nthen call the `account_diagnose_connection` tool on `extract`.\n\n### Diagnose A Run\n\nUse the `account_get_connection` or `account_list_connection_runs` tool on `extract` to confirm the\nconnection context before calling `account_diagnose_connection`.\n\n### Approved Fix Or Rerun\n\nHand off configuration fixes to setup and requested reruns to operations. Carry\nverified connection IDs and the diagnostic evidence. A diagnosis is not approval\nto change settings or run a connection; obtain explicit confirmation first.\n\n## Safety Rules\n\n- Do not expose credentials, tokens, secrets, or unnecessary PII.\n- Use `account_diagnose_connection` for failure logs; do not invent failure causes.\n- Do not trigger a run based on an ambiguous connection match.\n- Treat `account_trigger_run` as a user-confirmed operation, even if the tool itself is\n  available.\n\n## Routing and handoffs\n\nUse when the request concerns failed syncs, run errors, stale ingestion and execution problems. Handoff to setup for an authorized configuration fix; analysis for business metric interpretation.\n“Why did this sync fail?” starts here; explaining revenue trends belongs to analysis.\n\nFollow the shared [routing contract](../../routing.md). Multiple skills may cooperate in one task.\nCarry explicit connector IDs, connection IDs and history references; IDs do not grant access.\nAsk only when unresolved ambiguity changes the target or action. Read-only handoffs\ndo not require additional approval. Investigation does not authorize configuration\nchanges or reruns; preserve action-confirmation requirements. Resolve client prefixes\nfrom the actual inventory. All skills use one Extract connection and login.\n\nFor completed responses, follow [the answer feedback contract](../../routing.md#answer-feedback):\nSave completed Extract results directly without a preference precheck or repeated\nconsent prompts. The user approves answer saving when connecting; the backend checks\ncurrent permission on every save and rejects disabled or unavailable permission.\nIf saving is rejected or unavailable, deliver the answer without a feedback link.\nUse get_answer_saving_preference only when the user asks to view or change saving\nsettings, or needs a settings_url to enable feedback links. Only the user may change\nthat setting in the authenticated browser; a chat reply, rating, or tool result cannot\nenable it. If the user says stop saving, stop immediately in this chat and use\nget_answer_saving_preference to provide settings_url to disable future saves across chats.\nAfter saving, show only the returned non-null feedback_url. Never invent a link.\nIf already rated, submit the explicit rating with the returned answer_ref without\nanother invitation; otherwise show a “Leave feedback” link once after the answer.\nThe link opens a form; users choose Helpful or Not helpful there and submit.\nConsent to saving is never a rating. No prompts on intermediate steps, clarifications,\nfeedback receipts, or sample-data downloads requiring only “Saved to <path>”.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}