← ExtractCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Extract
Snapshot Sep 30, 2026 · 22:57 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "control-extract-operations",
"description": "Use Control Extract for account health, connector inventory, pipeline listings, connection details, and run history.",
"included_files": [],
"skill_md_contents": "---\nname: control-extract-operations\ndescription: Use Control Extract for account health, connector inventory, pipeline listings, connection details, and run history.\n---\n\n# Control Extract Operations\n\nUse this skill when the user asks about Extract account status, configured\nconnectors, sources, destinations, pipelines, connection details, or recent run\nhistory.\n\nThe plugin exposes one MCP server:\n\n- `control-extract` at `https://api.extract.to/mcp-account`, displayed as Control Extract.\n\nExtract documentation: https://docs.extract.to/\n\n## Tools\n\nUse these `control-extract` tools:\n\n- `account_summary` - summarize account connectors and connections.\n- `list_connectors` - list all account connectors, sources, and destinations.\n- `search_connectors` - filter account connectors by name, type, or platform.\n- `get_connector` - inspect one configured connector.\n- `list_connections` - list pipelines.\n- `search_connections` - find pipelines by source, destination, or status.\n- `get_connection` - inspect one pipeline.\n- `list_connection_runs` - list recent runs for a pipeline.\n\n## Workflows\n\n### Account Health\n\nUse the `account_summary` tool on `control-extract` for account status, pipeline health,\nactive connections, disabled connections, and error counts.\n\n### Connector Inventory\n\nUse the `list_connectors` tool on `control-extract` for a broad source/destination inventory.\nUse the `search_connectors` tool on `control-extract` when the user provides a connector name,\ntype, or platform filter.\n\n### Pipeline Details\n\nUse the `list_connections` tool on `control-extract` for broad pipeline discovery. Use\nthe `search_connections` tool on `control-extract` when the user provides a source,\ndestination, status, or name filter. Then call the `get_connection` tool\non `control-extract`\nbefore answering detailed questions about one pipeline.\n\n### Run History\n\nUse the `list_connection_runs` tool on `control-extract` after identifying the connection.\n\n## Safety Rules\n\n- Do not expose credentials, tokens, secrets, or unnecessary PII.\n- Do not guess connector ids or connection ids.\n- If multiple connectors or connections match, ask the user to choose one.\n- Use the setup skill for creating sources, destinations, connections, schedule\n changes, stream selection, or sample data.\n- Do not use this plugin for SQL analysis, schema discovery, or metadata editing;\n this plugin is account-MCP-only.\n"
}SHA-256: f5d7cfcfc3cfc024a2b47fafdc5a49f65431e9938a24d1a417586b8a88b5fbb4