ClaudeSuperPower

aidp-table-management

Skill

Control-plane lifecycle for AIDP catalog objects — create/update/delete/refresh tables, views, schemas, and catalogs, and register an EXTERNAL catalog/connection (ALH/ADW/object-storage) as a persistent catalog object. Use when the user wants to create or drop a table/view/schema/catalog via the con

Install

git clone https://github.com/oracle-samples/oracle-aidp-samples.git ~/.claude/skills/aidp-table-management

What is aidp-table-management?

Control-plane lifecycle for AIDP catalog objects — create/update/delete/refresh tables, views, schemas, and catalogs, and register an EXTERNAL catalog/connection (ALH/ADW/object-storage) as a persistent catalog object. Use when the user wants to create or drop a table/view/schema/catalog via the control plane (not a SELECT), register an external data source as a catalog, refresh catalog metadata, or test a connection. For SQL-native CREATE/ALTER/DROP use aidp-sql-ddl; for file→table ingestion use aidp-ingest-file-to-table; for browsing use aidp-catalog-explore.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~142 tokens of context used while enabled, before you invoke anything

Documentation

README · ~2 min read

aidp-table-management — catalog/schema/table/view lifecycle + external-catalog registration

Manage the metadata objects of the AIDP catalog through the control plane. Two equivalent paths for table DDL — the SQL-native path (aidp-sql-ddl, CREATE/ALTER/DROP …) and this control-plane path (CLI/REST create-table/create-view/create catalog) — plus the one thing only the control plane does: registering an external catalog/connection as a persistent object.

Engine precedence: official aidp CLI catalog/schema groups (preferred) → oci raw-request REST fallback (see references/oci-raw-request.md). Use --auth api_key --profile DEFAULT. Live-verified 2026-06-10: GET …/catalogs → 200, …/schemas?catalogKey=<key> → 200; …/tables?catalogKey=&schemaKey= and …/views?… → 400 InvalidParameter (routes exist, need the real schema key, not the name).

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills