archaeology skillA
archaeology is agent-read markdown (skill) from ai-analyst-lab/ai-analyst: Retrieve proven SQL patterns, table cheatsheets, and join patterns from .knowledge/query-archaeology/ so past work gets reused. Fire as a pre-flight step before writing ANY SQL. Also trigger on "do we have a known query for X", "how do we usually join these tables", "have we computed this metric before". If the store is empty or missing, exit silently. Also owns the writer convention: after a validated analysis, curate the final SQL here..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Skill: Query Archaeology ## Purpose Retrieve proven SQL patterns, table cheatsheets, and join patterns from the query archaeology store so agents reuse validated work instead of writing SQL from scratch. The skill also defines the store's local write path: after a validated analysis, the final SQL is curated back into the store (the Writer Convention below), which is what makes the retrieval loop close. ## When to Use - **Automatically** before any analysis agent writes SQL (pre-flight step) - **Manually** when the user asks about known patterns for a table or join - **After a validated analysis**, to curate the proven SQL (Writer Convention) ## Instructions ### Step 1: Check the Index Read `.knowledge/query-archaeology/curated/index.yaml`. Parse counters: `cookbook_entries`, `table_cheatsheets`, `join_patterns`. **If all three are zero (or the file is missing), stop here.** Return nothing and do not mention archaeology to the user. ### Step 2: Identify Search Terms From the current analysis context, extract: - **Table names** the agent is about to query (e.g., `orders`, `events`) - **Query intent tags** (e.g., `funnel`, `retention`, `revenue`, `cohort`) …
Read the whole file at its exact version.
How to install
mdr add ai-analyst-lab/ai-analyst/archaeology@git:20260827.7ff2e25mdr add ai-analyst-lab/ai-analyst/archaeology@sha256:2ced0eccef8e868fPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_lxgnlm2nhruv3nxs)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5305 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ai-analyst-lab/ai-analyst · 302 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lxgnlm2nhruv3nxs GET https://markdownregistry.com/api/v1/resolve?ref=ai-analyst-lab/ai-analyst/archaeology GET https://markdownregistry.com/api/v1/blob/2ced0eccef8e868f1aab01548f62687229d9952119e2637b2ff47a19faf2143b
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from ai-analyst-lab/ai-analyst
Every file in ai-analyst-lab/ai-analyst