Automated summary
Inspects the ServerKit SQLite database (tables, schemas, row counts, ad-hoc queries) locally via WSL or in production through SSH MCP.
Strengths
- Covers the three common cases: full schema overview, per-table detail, or running an arbitrary SQL query
- Explicitly separates the local database (backend/instance/serverkit.db) from production (/opt/serverkit/backend/instance/serverkit.db via SSH MCP)
- Built-in guardrails: prints the query before running it, requires confirmation in production, and forbids writes by default
- Formatted column output (sqlite3 -header -column) that stays readable inside the chat
Limitations
- SQLite only: no support for PostgreSQL, MySQL, or other engines
- The database paths and SSH MCP setup are hardcoded to the ServerKit project, so the skill is hard to reuse elsewhere
- Protection against DELETE/DROP/UPDATE relies on prompt instructions rather than a technical enforcement mechanism
Use it to debug data inconsistencies or get a quick picture of ServerKit's schema and table contents.
Avoid it for schema migrations, bulk data changes, or inspecting any non-SQLite database.
Security analysis
CautionThis is a legitimate database inspection skill, but it uses powerful execution channels (Bash, SSH MCP, sqlite3) and accepts user-controlled SQL/table arguments with weak injection and read-only safeguards. It is not overtly malicious or exfiltrating, so caution rather than risky.
- •Executes shell commands via Bash and remote commands via mcp__ssh-mcp__exec, including against a production database.
- •User argument/table/query placeholders are inserted into sqlite3 shell commands without demonstrated quoting/escaping or validation, so crafted input could alter the shell command or SQL.
- •The skill permits arbitrary SQL ('If argument looks like a SQL query: Run it directly') and only warns against destructive statements; it does not enforce read-only mode, so DELETE/DROP/UPDATE could be run if supplied as the argument.
- •No explicit allowlist, query sanitization, or production read-only safeguard is defined.
Examples
/db-inspect schema/db-inspect users/db-inspect production — SELECT count(*) FROM orders WHERE created_at > '2025-01-01';name: db-inspect description: Inspect the ServerKit SQLite database — show tables, schemas, row counts, and run queries. Runs via WSL for local dev or SSH MCP for production. Use when debugging data issues or understanding the current database state. disable-model-invocation: true argument-hint: "[query or table-name]" allowed-tools: Bash, mcp__ssh-mcp__exec
Inspect the ServerKit database. Argument: $ARGUMENTS
Database Location
- Local dev:
backend/instance/serverkit.db(relative to project root) - Production:
/opt/serverkit/backend/instance/serverkit.db(access via SSH MCP)
If no argument or argument is "schema"
Show the full database schema:
sqlite3 backend/instance/serverkit.db '.schema'
And row counts for all tables:
sqlite3 backend/instance/serverkit.db "SELECT name FROM sqlite_master WHERE type='table' ORDER BY name;"
Then for each table, get the row count and present as a formatted table: Table Name | Row Count
If argument is a table name
Show the schema and last 10 rows:
sqlite3 -header -column backend/instance/serverkit.db 'PRAGMA table_info(<table>);'
sqlite3 -header -column backend/instance/serverkit.db 'SELECT * FROM <table> ORDER BY id DESC LIMIT 10;'
If argument looks like a SQL query
Run it directly:
sqlite3 -header -column backend/instance/serverkit.db '<query>'
If argument is "production" or "prod"
Run the schema/overview commands on the production server via SSH MCP instead, using /opt/serverkit/backend/instance/serverkit.db.
Safety
- NEVER run DELETE, DROP, UPDATE, or INSERT queries unless explicitly asked
- Always show the query before running it
- For production, double-check with the user before running any query
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/sqlite-database-inspector-mmio712g/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/sqlite-database-inspector-mmio712g' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/sqlite-database-inspector-mmio712g/download' --output '.skill-downloads/sqlite-database-inspector-mmio712g/SKILL.md.part' && mv '.skill-downloads/sqlite-database-inspector-mmio712g/SKILL.md.part' '.skill-downloads/sqlite-database-inspector-mmio712g/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash, mcp__ssh-mcp__exec
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/sqlite-database-inspector-mmio712g/SKILL.md' && test -s '.skill-downloads/sqlite-database-inspector-mmio712g/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/db-inspect' && cp -R '.skill-downloads/sqlite-database-inspector-mmio712g' '.claude/skills/db-inspect'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/sqlite-database-inspector-mmio712g'openskills read 'sqlite-database-inspector-mmio712g'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/sqlite-database-inspector-mmio712g/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.