agentsclimarketplace

Authoring meta context

Skill keithbinkly/dbt-meta-context/skills/authoring-meta-context

Context cards for dbt metrics — 5-layer meta: schema, validator CLI, and installable agent skill so AI agents answer analytical questions accurately

Install
npx -y skills add keithbinkly/dbt-meta-context --skill authoring-meta-context

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Authors and extracts dbt MetricFlow meta context — structured YAML `meta:` blocks that encode business knowledge (thresholds, investigation paths, SLAs, relationships) alongside metric definitions so AI agents answer analytical questions accurately. Use when user asks about context cards, meta context blocks, dbt metric meta blocks, semantic layer context, distilling runbooks into YAML, authoring meta context, validating meta context, or improving AI agent analytical accuracy on dbt metrics.

SKILL.md

4.2 KB, as published. Nobody here has run it

Authoring Meta Context

Quick start

  1. Gather source docs (runbooks, wikis, SLA contracts, post-mortems) for your target metric.
  2. Run the distillation prompt against them: see guides/distillation-prompt.md.
  3. Paste the draft meta: block into your semantic model YAML.
  4. Validate: dbt-mc validate path/to/semantic_model.yml
  5. Fill # NEEDS REVIEW and # NOT FOUND gaps from the output.

Start with Bronze tier (13 Core fields, ~45 min/metric) on your 5–10 most-questioned metrics.

Authoring workflow

  • Collect source docs (see guides/sourcing.md for field-by-field source map)
  • Run distillation prompt — fills 60–70% of schema from existing docs
  • Review output: verify # NEEDS REVIEW items; fill # NOT FOUND gaps with the metric owner (see guides/interview.md for the domain-expert interview questions)
  • Add business_rules (Layer 5) for any metric tied to a customer or regulatory SLA — absence creates false confidence
  • Validate with dbt-mc validate — check for type errors and false-confidence risk
  • Set last_validated to today's date

The 5 layers

LayerQuestionFailure it closes
1. ContextWho cares and why does this exist?Interpretation
2. ExpectationsWhat does good look like?Calibration
3. InvestigationWhen it breaks, where do I look?Framing
4. RelationshipsWhat else moves when this moves?Reasoning
5. DecisionsWhat do I do about it?Action + false confidence

Critical: Layers 2–4 without Layer 5 create false confidence. An agent that knows healthy ranges but not business rules will give confidently wrong answers on SLA and compliance questions.

Authoring principles

Follow the five principles in guides/authoring.md:

  1. Write for the worst-case consumer — no jargon, no assumed knowledge
  2. Encode reasoning, not just facts (include the why in seasonality, investigation paths)
  3. Use specific relationship types with direction, magnitude, and lag
  4. Include magnitude in thresholds and seasonality
  5. Write investigation paths as conditional logic (IF/THEN trees), not flat lists

Validator

pip install "git+https://github.com/keithbinkly/dbt-meta-context.git#subdirectory=validator"
dbt-mc validate models/semantic_models/         # tier report + false-confidence risk
dbt-mc validate models/ --format json           # CI integration

Exit code 2 = false-confidence risk (expectations populated without business_rules). See validator/README.md for CI and pre-commit setup.

Reference

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.