sqlite-inspector
Checks database consistency and API results for MikoPBX.
Install
mkdir -p .claude/skills/sqlite-inspector && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/375" && unzip -o skill.zip -d .claude/skills/sqlite-inspector && rm skill.zipInstalls to .claude/skills/sqlite-inspector
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Проверка консистентности данных в SQLite базах данных MikoPBX после операций REST API. Использовать при валидации результатов API, отладке проблем с данными, проверке связей внешних ключей или инспектировании CDR записей для тестирования.Key capabilities
- →Queries MikoPBX SQLite databases for data validation
- →Verifies foreign key relationships and integrity
- →Inspects Call Detail Records (CDR) for routing
- →Validates REST API persistence
- →Checks schema consistency across MikoPBX tables
How it works
Runs targeted SQL queries via `docker exec` against the containerized MikoPBX database.
Inputs & outputs
When to use sqlite-inspector
- →Verifying data after API calls
- →Debugging database inconsistencies
- →Validating foreign key relationships
About sqlite-inspector
Inspects SQLite databases to verify data persistence after API operations. Validates foreign key relationships and call history records.
Проверка консистентности данных в SQLite баз данных MikoPBX после операций REST API. Использовать при валидации результатов API, отладке проблем с данными, проверке связей внешних ключей или инспектировании CDR записей для тестирования.
When not to use it
- →Modifying database schema directly without API
- →General database management outside of MikoPBX
- →Performance tuning for high-traffic databases
Prerequisites
Limitations
- →Limited to MikoPBX container environments
- →ReadOnly operations recommended for consistency checks
- →Requires knowledge of MikoPBX database structure
How it compares
Provides a specialized interface for MikoPBX-specific table schemas and CDR record verification rather than generic SQL inspection.
Compared to similar skills
sqlite-inspector side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| sqlite-inspector (this skill) | 5 | 10mo | Review | Intermediate |
| redis-inspect | 6 | 8mo | Review | Beginner |
| write-script-duckdb | 3 | 5mo | No flags | Intermediate |
| linear-data-handling | 1 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mikopbx
View all by mikopbx →You might also like
redis-inspect
civitai
Inspect Redis cache keys, values, and TTLs for debugging. Supports both main cache and system cache. Use for debugging cache issues, checking cached values, and monitoring cache state. Read-only by default.
write-script-duckdb
windmill-labs
MUST use when writing DuckDB queries.
linear-data-handling
jeremylongshore
Data synchronization, backup, and consistency patterns for Linear. Use when implementing data sync, creating backups, or ensuring data consistency across systems. Trigger with phrases like "linear data sync", "backup linear", "linear data consistency", "sync linear issues", "linear data export".
local-cluster-manager
multigres
Manage local multigres cluster components (multipooler, pgctld, multiorch, multigateway) - start/stop services, view logs, connect with psql, test S3 backups locally
differential-fuzzer
tursodatabase
Information about the differential fuzzer tool, how to run it and use it catch bugs in Turso. Always load this skill when running this tool
supabase-incident-runbook
jeremylongshore
Execute Supabase incident response procedures with triage, mitigation, and postmortem. Use when responding to Supabase-related outages, investigating errors, or running post-incident reviews for Supabase integration failures. Trigger with phrases like "supabase incident", "supabase outage", "supabase down", "supabase on-call", "supabase emergency", "supabase broken".