sql-analyst
Skill97 starsChanged 32 days agoApache-2.0View on GitHub
Answer a bounded data question from one declared governed read; use the explicit plan runner when only a schema-validated analysis plan is wanted.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Suryanandx/qvac-uitheir own version, first seen Nov 1, 2026
- darker2016/WorkbuddySkillGroups4DSHtheir own version, first seen Aug 14, 2026
- xcrrr/claude-skillstheir own version, first seen Mar 19, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- darker2016/WorkbuddySkillGroups4DSH★ 6same name
- xcrrr/claude-skills★ 6same name
- Suryanandx/qvac-ui★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository94 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- runxSkill
- adopt-skillSkill
- agencySkill
- answer-from-docsSkill
- attention-reviewSkill
- audit-receiptSkill
- brand-voiceSkill
- business-opsSkill
- chargeSkill
- chief-of-staffSkill
- cold-outreachSkill
- content-pipelineSkill
- contract-drafterSkill
- conversation-replySkill
- conversation-reviewSkill
- crm-cleanupSkill
- cve-auditSkill
- data-storeSkill
- data-subject-requestSkill
- deep-researchSkill
- diagnose-skill-runSkill
- dispute-respondSkill
- ecosystem-briefSkill
- extractSkill
- ghostwriteSkill
- github-pr-commentSkill
- github-pr-reviewSkill
- github-syncSkill
- google-analyticsSkill
- google-calendarSkill
- google-search-consoleSkill
- governed-outboundSkill
- helpdeskSkill
- incident-commanderSkill
- issue-intakeSkill
- issue-to-prSkill
- issue-triageSkill
- knowledge-routerSkill
- lead-enrichmentSkill
- lead-qualifySkill
- least-privilegeSkill
- ledgerSkill
- list-hygiene-judgeSkill
- marketplace-invokeSkill
- meeting-followupSkill
- mock-chargeSkill
- mock-paySkill
- mock-refundSkill
- moltbookSkill
- n8n-handoffSkill
- nitrosendSkill
- nws-weather-forecastSkill
- open-meteo-weather-forecastSkill
- operator-inboxSkill
- ops-deskSkill
- organic-growthSkill
- policy-authorSkill
- The first 60 shown.
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 8
Use this skill to answer a bounded data question from one declared, typed data source operation.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
SQL Analyst
Use this skill to answer a bounded data question from one declared, typed data
source operation. The default validates the plan, performs the exact
data-store read, and interprets only that returned evidence. The explicit
plan runner stops at a reviewable read-only plan.
The schema and optional sample snapshot must carry stable upstream SHA-256 digests and observation times. Runx treats them as caller-supplied provenance, not provider verification. Deterministic admission rejects stale or malformed sources, write intent, invalid identifiers or dialects, unknown allowed tables, and unbounded row requests before the model runs. The model designs a plan against a normalized table/field index. A deterministic finalizer then rejects invented tables and fields, untyped joins, unstructured filters, literal filter values, invalid limits, incomplete interpretation, and write tokens.
This skill never emits or executes raw SQL. The default requires a validated
execution_context for data-store.read_projection, read_events, or
list_stream_heads; it performs that read and returns an interpretation. The
explicit plan runner may omit the context and returns planned_only.
Composes
<!-- Generated from the native execution closure; run pnpm core-skills:composes:generate. -->data-store#list_stream_headsdata-store#read_eventsdata-store#read_projection
Inputs
question: bounded analysis question.schema_summary: source-bound available tables and fields.dialect:postgres,sqlite, ormysql.as_ofandmax_schema_age_days: deterministic source-freshness boundary.sample_rows: optional source-bound snapshot containing at most 20 non-sensitive rows.constraints: allowed tables, maximum rows, and privacy limits.execution_context: required for the default; an exact governed data-store read runner and bounded resource inputs. It is optional only forplan.
Output
The default returns analysis_result from the validated plan and actual
runx.data.operation_result.v1 evidence. plan returns the existing
runx.data.sql_analysis_plan.v1 packet.
Agent task contracts
sql-plan
Produce sql_plan_draft using only analysis_context tables and qualified fields. Return decision, query_plan, validation_checks, interpretation, and residual_risks. The plan is read-only and does not execute. Use the declared dialect and bounded limit. Do not invent schema, request credentials, expose PII, or emit write SQL.
sql-interpret
Answer the supplied question using only validated_plan and governed_data.
Return analysis_result with a direct answer, material observations, caveats,
and the data operation evidence reference. Never claim access to rows, fields,
or freshness not present in the governed result.
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.

