Which database does the db-openapi skill target?

This skill is specifically designed to query the v3_openapi database, focusing on tables like integrated_connector and integrated_connector_api.

Does the skill handle deleted records?

Yes, all provided SQL templates automatically include a 'deleted_at = 0' condition to ensure only active records are retrieved.

Can I query field-level configurations?

Yes, the skill includes specific templates for querying the integrated_connector_api_field table by interface ID or connector ID.

How are queries executed within this skill?

Queries are executed using the exec_sql MCP tool. The skill first prints the target SQL statement and then displays the results in a structured table or list format.

Blacklake OpenAPI Database Query

Name: Blacklake OpenAPI Database Query
Author: SeSiTing

bySeSiTing

API Development

Queries and manages integrated connectors and API configurations within the v3_openapi database using structured SQL templates.

About

The db-openapi skill enables Claude to efficiently navigate and retrieve data from the v3_openapi database, specifically focusing on integration connectors, API interfaces, and field configurations. It streamlines the developer workflow by providing pre-defined SQL templates that handle tenant-specific filtering and soft-deletion logic automatically. This skill is essential for debugging integration mappings, auditing connector setups, and inspecting API schemas directly through the Claude Code interface.

Key Features

Structured data presentation using tables and lists for query results
Automated SQL generation for connector and API lookups
Standardized soft-deletion handling (deleted_at = 0) across all queries
Detailed inspection of API request and response field configurations
Tenant-based filtering using organization IDs
0 GitHub stars

Use Cases

Retrieving all active API interfaces for a specific tenant and connector
Inspecting request/response field mappings for a specific API ID
Auditing integrated connector configurations across different organizations

About

Key Features

Structured data presentation using tables and lists for query results
Automated SQL generation for connector and API lookups
Standardized soft-deletion handling (deleted_at = 0) across all queries
Detailed inspection of API request and response field configurations
Tenant-based filtering using organization IDs
0 GitHub stars

Use Cases

Retrieving all active API interfaces for a specific tenant and connector
Inspecting request/response field mappings for a specific API ID
Auditing integrated connector configurations across different organizations