← Cognitive DatabaseCONTENT HISTORY

Update to Cognitive Database

Snapshot Nov 18, 2026 · 06:17 UTC · version 0.1.7

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Cognitive Database and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "List, inspect, check, and delete saved CognitiveDB cloud storage and database connections, collect database metadata, and prepare S3 IAM Role trust policies. Use for connections supporting Cloud or Database Ingestion.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 250
    },
    {
      "relative_path": "references/aws-iam-role-setup.md",
      "size_in_bytes": 652
    },
    {
      "relative_path": "references/aws-s3-read-policy.md",
      "size_in_bytes": 1336
    }
  ],
  "name": "cognitivedb-manage-connections",
  "skill_md_contents": "---\nname: cognitivedb-manage-connections\ndescription: >-\n  List, inspect, check, and delete saved CognitiveDB cloud storage and database\n  connections, collect database metadata, and prepare S3 IAM Role trust policies.\n  Use for connections supporting Cloud or Database Ingestion.\nmetadata:\n  version: \"dev-1.0.5-external.1\"\n---\n\n# Manage CognitiveDB Connections\n\n## Boundaries\n\n- Own saved Connection inspection, connectivity checks, deletion, database\n  metadata collection, and S3 trust-policy preparation in the selected Space.\n- For Connection creation or configuration changes, direct the user to the\n  CognitiveDB platform's Connection settings. Resume with the saved Connection\n  after the user completes the change.\n- Route source browsing and ingestion task creation to\n  `cognitivedb-manage-ingestion` with the verified Connection identity and scope.\n\n## Core Instructions\n\n- Bind the task's selected Space and supply `space_id` to each scoped Tool.\n- For inventory, list cloud storage or database Connections with the requested\n  provider filters. Continue pagination while `hasMore` is true. An inventory\n  request needs no connectivity check or single-Connection selection.\n- For one Connection, resolve its exact saved name and provider from list or\n  show. Ask for a selection when names are ambiguous. For cloud storage, carry\n  the name and `connectionType` together; for databases, retain the returned\n  provider and metadata scope. Use the live Tool's supported provider set.\n- Read saved details for inspection; use the dedicated check Tool for a live\n  connectivity test. Cloud storage checks can update saved status and timestamp;\n  database checks do not change saved settings. Report the returned test result.\n- For database metadata collection, confirm the exact saved Connection and\n  collection scope, submit once, and preserve the returned collection status.\n  Read that Connection again for progress; an accepted request is not completed\n  collection. Inspect an uncertain submission through saved state without\n  resubmitting it.\n- For S3 IAM Role trust preparation or repair, call\n  `cognitivedb_s3_connection_generate_trust_policy`, reusing a supplied External ID.\n  Show the returned policy for the user to apply in AWS. For Role setup, read\n  [AWS IAM Role setup](references/aws-iam-role-setup.md); for requested S3\n  permission guidance, read [S3 read policy](references/aws-s3-read-policy.md).\n  Have the user save the resulting Connection settings in CognitiveDB, then\n  check the exact saved Connection.\n- Before deletion, show the exact Connection, provider, Space, and impact on\n  dependent ingestion. Confirm deletion of the saved Connection; external\n  storage, database data, and provider identities remain. Delete once, then\n  verify absence through show or a complete scoped listing. If the outcome is\n  uncertain, inspect the exact target. Retry at most once when that inspection\n  proves deletion did not occur, the live contract permits retry, and the user\n  gives fresh approval.\n- Present required questions and approvals through the host's interaction\n  mechanism. Carry only Connection identity, scope, status, and requested public\n  details into ingestion handoffs. Keep credentials in the platform settings.\n\n## Allowed MCP Tools\n\n- `cognitivedb_cloud_storage_connection_check`\n- `cognitivedb_cloud_storage_connection_delete`\n- `cognitivedb_cloud_storage_connection_list`\n- `cognitivedb_cloud_storage_connection_show`\n- `cognitivedb_database_connection_check`\n- `cognitivedb_database_connection_delete`\n- `cognitivedb_database_connection_list`\n- `cognitivedb_database_connection_metadata_collect`\n- `cognitivedb_database_connection_show`\n- `cognitivedb_s3_connection_generate_trust_policy`\n- `cognitivedb_space_current_get`\n"
}

SHA-256 of public snapshot: 04a6d3aefd73a72305fe4bfb4c2648b3181c64c051ede34664f0e0e4b0a28a93