What database does this skill target?

This skill specifically targets the v3_e-report database, focusing on tables related to reporting and data analysis alert configurations.

Can I review the SQL before it runs?

Yes, the skill is programmed to print the complete SQL statement for user review before utilizing the exec_sql tool to run the query.

Which table is primarily used for alert configurations?

The skill focuses on the analysis_config table, which contains fields for organization IDs, alert names, status, and JSON-based conditions.

How does the skill handle soft-deleted records?

All provided query templates automatically include the 'deleted_at = 0' condition to ensure only active, non-deleted records are retrieved.

Is the output format easy to read?

Instead of raw JSON data, this skill formats query results into structured tables or lists, including record counts and key field highlights.

E-Report Database Management

Name: E-Report Database Management
Author: SeSiTing

bySeSiTing

Database Management

Simplifies querying and managing the v3_e-report database for data analysis alert configurations and tenant statistics.

About

The E-Report Database Management skill provides Claude with specialized SQL templates and standardized procedures for interacting with the v3_e-report database. It streamlines the retrieval of data analysis alert configurations from the analysis_config table, allowing users to efficiently monitor tenant-specific rules, status updates, and reporting conditions. By enforcing structured data presentation and mandatory SQL previews, this skill ensures accuracy and transparency when auditing reporting infrastructure or troubleshooting alert triggers.

Key Features

Standardized SQL templates for the analysis_config table
Pre-execution SQL statement transparency for verification
0 GitHub stars
Automatic filtering of inactive records using deleted_at logic
Structured data visualization using tables and lists
Tenant-specific (org_id) query filtering

Use Cases

Auditing data analysis alert configurations across multiple organization IDs
Inspecting JSON-formatted alert conditions and triggered actions for debugging
Generating statistics on active versus inactive alert rules for a specific tenant

About

Key Features

Standardized SQL templates for the analysis_config table
Pre-execution SQL statement transparency for verification
0 GitHub stars
Automatic filtering of inactive records using deleted_at logic
Structured data visualization using tables and lists
Tenant-specific (org_id) query filtering

Use Cases

Auditing data analysis alert configurations across multiple organization IDs
Inspecting JSON-formatted alert conditions and triggered actions for debugging
Generating statistics on active versus inactive alert rules for a specific tenant