Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kaelio/historic_sql_patterns
Identify recurring cross-table historic-SQL analytical intents from a bounded pattern shard and emit typed pattern evidence for deterministic wiki projection.
Passed 10 of 17 test cases with the skill, and 5 of 17 without it.
and 5 more in the full report
8 fixed5 passed either way7 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
If a column identifier mentioned in the raw SQL pattern fails verification against the warehouse schema during doc generation, how must it be formatted in text outputs?
| Checked | Without skill | With skill |
|---|---|---|
| Wraps the candidate identifier in square brackets with unverified and the raw file path reference | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when the WorkUnit raw file is a patterns-input/part-0001.json style shard from the historic-sql adapter. Older staged bundles may still provide root patterns-input.json; when that is the WorkUnit raw file, read it the same way.
rawFiles section.read_raw_file for that exact raw file path.pattern evidence object per durable cross-table intent by calling emit_historic_sql_evidence.Every join column mentioned in pattern descriptions must be verified via entity_details for both sides of the join.
Before writing a wiki page or SL source on any topic:
discover_data({query: "<topic>"}) - see what wikis, SL sources, and raw
tables already exist. Prefer updating existing pages over creating new ones.Before emitting any schema.table or schema.table.column into a wiki body,
SL source, tables: frontmatter, sl_refs, or emit_unmapped_fallback:
entity_details({connectionId, targets: [{display: "<identifier>"}]}) -
confirm the identifier resolves; inspect native types, FK/PK, and
sampleValues.entity_details sampleValues for the relevant
column. If sampleValues is short or the sample may have missed real values,
run a sql_execution probe with the same warehouse connection id:
sql_execution({connectionId, sql: "SELECT DISTINCT <col> FROM <ref> LIMIT 50"}).sql_execution({connectionId, sql: "SELECT 1 FROM <ref> LIMIT 0"}).
If it errors, the identifier is fictional.[unverified - from <rawPath>] in the wiki body,
citing the exact raw path that mentioned it.emit_unmapped_fallback with no_physical_table, includetest cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.