database-access
Skill0 starsChanged 35 days agoMITView on GitHub
Explore and query databases on the user's servers (Postgres, MySQL/MariaDB, Redis, MongoDB, SQLite) through Termalin without credentials in the chat. Use when the user asks what is in a database, wants a query, a count, a schema, a slow query check or a data fix on a server.
In this repository4 other files it gives its agents.
- deploy-checkSkill
- incident-triageSkill
- run-commandsSkill
- server-healthSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Always add LIMIT (default 50, at most 500) to row-returning queries.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Termalin's data_* tools connect to the database on the server through the Connector, so no password is ever pasted here. The default is read-only.
Order of work:
hosts_listto pick the server, thendata_tableswith theengineanddatabaseto see what exists. Do not guess table names.data_schemafor each table the question touches: columns, types, keys, indexes, row estimate. Use the real column names in the query.data_queryfor the actual question. Rules:- Always add
LIMIT(default 50, at most 500) to row-returning queries; aggregate withCOUNT,GROUP BY,date_truncinstead of pulling rows and counting in the chat. - Read-only unless the user explicitly asks for a change. A write (
INSERT,UPDATE,DELETE,ALTER,DROP, RedisSET/DEL, Mongo updates) needsallowWrites: true, a connection with full access, and the user's yes to the exact statement; show the statement first, with aWHEREthat matches what they described, and prefer aSELECT COUNT(*)with the sameWHEREbefore theUPDATE/DELETE. - Wrap risky writes in a transaction when the engine supports it, and report the affected-row count after.
- Long analytical queries (over a minute) time out; narrow the date range or run them as a background job on the server with
job_startand the engine's CLI.
- Always add
- Present results as a compact table or a sentence with the number; name the database and server the answer came from.
Privacy: do not dump whole tables of personal data (emails, names, addresses, payment fields) into the chat. Aggregate, or select only the columns the question needs, and mask identifiers when the user only needs a count or a pattern.
Slow database: data_query with the engine's own views — Postgres pg_stat_activity (running queries, waits), pg_stat_user_tables (seq scans), pg_stat_statements if installed; MySQL SHOW FULL PROCESSLIST, SHOW ENGINE INNODB STATUS; Redis INFO memory, SLOWLOG GET 10. Pair with server_metrics to see whether the host is CPU-, memory- or disk-bound.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

