SkillAgentSearch skills...

historic_sql_table_digest

Convert one changed historic-SQL table usage bucket into typed table usage evidence for deterministic _schema projection.

Install / Use

npx skills add Kaelio/ktx --skill historic_sql_table_digest

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

84/100

Category

Automation

Supported Platforms

Universal

Our assessment of historic_sql_table_digest

historic_sql_table_digest scores 84/100 on our quality scale, 2073rd of 2,780 Automation skills we index.

Its SKILL.md is 3.7 KB long, split into 6 sections with 1 code example: a solid amount of guidance for an agent.

With 1,601 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so historic_sql_table_digest is actively maintained.
  • Our last check on 2026-10-14 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-08. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

historic_sql_table_digest compared with similar skills

All 4 of these similar skills score higher than historic_sql_table_digest; compare them before choosing.

SkillScoreStarsUpdatedFormat
historic_sql_table_digest (this skill)by Kaelio841.6k2mo agoSKILL.md
claude-memby thedotmack100117.6ktodayCLAUDE.md
Agent-Reachby Panniantong100112.3k9d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install historic_sql_table_digest?
Run npx skills add Kaelio/ktx --skill historic_sql_table_digest. The install tabs above show the steps for each supported agent.
Which AI agents does historic_sql_table_digest work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is historic_sql_table_digest safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is historic_sql_table_digest still maintained?
The repository was last updated about 2 months ago, so historic_sql_table_digest is actively maintained.

name: historic_sql_table_digest description: Convert one changed historic-SQL table usage bucket into typed table usage evidence for deterministic _schema projection. callers: [memory_agent]

Historic SQL Table Digest

Use this skill when the WorkUnit raw file is one tables/<schema>.<name>.json file from the historic-sql adapter.

Required Workflow

  1. Read the WorkUnit notes first.
  2. Call read_raw_file for the single tables/<schema>.<name>.json raw file.
  3. Read manifest.json only if the table JSON omits the dialect or the WorkUnit notes are unclear.
  4. Produce one concise usage narrative for this table from the staged table JSON.
  5. Call emit_historic_sql_evidence exactly once with kind: "table_usage".
  6. Stop after the evidence tool succeeds.

Identifier Verification Protocol

Before writing a wiki page or SL source on any topic:

  1. 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:

  1. entity_details({connectionId, targets: [{display: "<identifier>"}]}) - confirm the identifier resolves; inspect native types, FK/PK, and sampleValues.
  2. For literal values from the source, such as status codes or plan tiers, check whether they appear in 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"}).
  3. If the candidate identifier still does not resolve, do one of:
    • Use sql_execution({connectionId, sql: "SELECT 1 FROM <ref> LIMIT 0"}). If it errors, the identifier is fictional.
    • Wrap the identifier in [unverified - from <rawPath>] in the wiki body, citing the exact raw path that mentioned it.
    • When recording emit_unmapped_fallback with no_physical_table, include the failing probe error in clarification.
  4. Never copy <schema>.<table> placeholder strings from these instructions into output.

Evidence Shape

Call emit_historic_sql_evidence with this shape:

{
  "kind": "table_usage",
  "table": "public.orders",
  "usage": {
    "narrative": "Orders are repeatedly queried for paid/refunded lifecycle analysis and customer-level rollups.",
    "frequencyTier": "high",
    "commonFilters": ["status", "created_at"],
    "commonGroupBys": ["status"],
    "commonJoins": [{ "table": "public.customers", "on": ["customer_id"] }],
    "staleSince": null
  }
}

The usage object must match tableUsageOutputSchema.

Interpretation Rules

  • Treat columnsByClause.where as common filters.
  • Treat columnsByClause.groupBy as common group-bys.
  • Treat observedJoins as common joins.
  • Use stats.executionsBucket, stats.distinctUsersBucket, and stats.recencyBucket to choose frequencyTier.
  • Use frequencyTier: "high" only when executions and distinct users are both broad.
  • Use frequencyTier: "mid" for repeated team usage that is not broad enough for high.
  • Use frequencyTier: "low" for low-volume but present usage.
  • Use frequencyTier: "unused" only when the table input explicitly says the table is stale or has no recent templates.
  • Keep narrative short and concrete.

Boundaries

  • Do not call wiki_write.
  • Do not call sl_write_source.
  • Do not call sl_edit_source.
  • Do not call context_candidate_write.
  • Do not emit more than one table usage evidence object.
  • Do not invent columns, joins, or tables that are absent from the staged JSON.

Related Skills

View on GitHub
GitHub Stars1.6k
CategoryAutomation
Updated2mo ago
Forks107

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions