← Files ExtractARCHIVED FILE

SKILL.md

2 KB · Sep 30, 2026 · 22:57 UTC

↓ Download file

---
name: control-extract-diagnostics
description: Diagnose failed Control Extract connections, inspect recent failed runs, and trigger manual runs only after explicit user confirmation.
---

# Control Extract Diagnostics

Use this skill when the user asks why an Extract pipeline failed, wants failed
or unhealthy connections, asks for run diagnostics, or asks to manually trigger
a connection run.

The plugin uses only the Control Extract MCP server:

- `control-extract` at `https://api.extract.to/mcp-account`, displayed as Control Extract.

Extract documentation: https://docs.extract.to/

## Tools

Use these `control-extract` tools:

- `search_connections` - find failed, unhealthy, or matching pipelines.
- `get_connection` - inspect one pipeline before diagnosis or run control.
- `list_connection_runs` - inspect recent run history.
- `diagnose_connection` - read failure diagnostics from recent run logs.
- `trigger_run` - trigger a manual run only after explicit user confirmation.

## Workflows

### Find Failed Connections

Use the `search_connections` tool on `control-extract` with `status="ERROR"` when the user
asks for failed, failing, broken, or unhealthy pipelines.

If the user asks why a pipeline failed, identify the exact connection first,
then call the `diagnose_connection` tool on `control-extract`.

### Diagnose A Run

Use the `get_connection` or `list_connection_runs` tool on `control-extract` to confirm the
connection context before calling `diagnose_connection`.

### Trigger A Manual Run

Never call `trigger_run` until the user explicitly confirms the exact
connection to run. Before asking for confirmation, show the connection name,
source, destination, and current status with `get_connection`.

## Safety Rules

- Do not expose credentials, tokens, secrets, or unnecessary PII.
- Use `diagnose_connection` for failure logs; do not invent failure causes.
- Do not trigger a run based on an ambiguous connection match.
- Treat `trigger_run` as a user-confirmed operation, even if the tool itself is
  available.

SHA-256: 12235dce4a1537afe63607e0b2ce627f0c09227737f33f96236b0bdc5945ac82