okf-enrich

name	okf-enrich
description	Guidance for an AI agent to enrich an Open Knowledge Format (OKF) bundle with high-quality concept descriptions using its own LLM — grounded in the bundle's schema, data profile, and samples — then optionally sync them back to the source. Use when an OKF bundle has missing, weak, or low-quality descriptions that should be improved before publishing or ingestion. Instructions-only; no binary required.
license	Apache-2.0
metadata	{"version":"0.3.0","author":"Yurii Serhiichuk","tags":"okf, enrichment, documentation, agent-guidance, prompt-engineering"}

OKF Bundle Enrichment Guidance Skill

This skill teaches an AI agent (Claude Code, Cursor, Gemini CLI, Copilot, …) how to enrich an Open Knowledge Format (OKF) bundle — adding or improving the human-readable description of each concept (table, dataset, file, directory) — using the agent's own LLM.

There is deliberately no binary and no embedded model here. Generating a good description is a judgment task, and the harness driving the project already has a capable LLM in the loop. Embedding a second one would mean a model calling a tool that calls another model: redundant cost, an extra API key to manage, and usually a worse result than the model already doing the work. So enrichment is delivered as guidance — the procedure and the quality bar — for whatever LLM is present, exactly as okf-reader is guidance for reading a bundle.

When to Use

Load this skill when asked to enrich, document, describe, annotate, or "improve the descriptions in" an OKF bundle — typically after a connector has produced the bundle and before syncing descriptions back to the source.

Pairs with:

• okf-reader — follow its rules to read and navigate the bundle efficiently (index-first, frontmatter-only when possible, grep for targeted lookups).
• the connectors (okf-sqlite, okf-mysql, okf-postgresql, okf-bigquery, okf-fs, okf-git) — the producers and the sync target. Enrichment is far better when the bundle was produced with --profile and --sample (the four SQL connectors), and the descriptions you write can be pushed back to the origin with the connector's ingest --sync.

The OKF concept document

Each concept is a markdown file with YAML frontmatter:

---
type: SQLite Table
title: orders
description:                       # <- the field you write
resource: sqlite:///.../orders
tags: [sqlite, table]
timestamp: 2026-06-13T12:00:00Z
---
# Columns

| Name | Type | Primary Key | Nullable | Default |
| ---  | ---  | ---         | ---      | ---     |

## Data Profile                    # present only when produced with --profile

| Column | Non-Null | Null | Distinct | Min | Max |
| ---    | ---      | ---  | ---      | --- | --- |

## Sample                          # present only when produced with --sample

| id | customer_id | total | status |
| ...

Your enrichment target is the frontmatter description field. For sources that carry per-column comments (MySQL, PostgreSQL, BigQuery — their # Columns table includes a Comment/Description column), you may also fill the empty cells in that column.

Procedure

1. Discover concepts (index-first)

Follow the okf-reader rules: read index.md first and use it to locate concept files; route directly to the files you need. Do not recursively read the whole bundle.

To see exactly what still needs work — and to re-measure after enriching — run the deterministic, no-LLM coverage report: okf-viz coverage --bundle <dir> (add --json for machine output, --min <pct> to gate in CI). It reports the percentage of non-placeholder descriptions, columns commented, broken cross-links, concepts missing a type, and orphan nodes.

2. Decide what to enrich

Enrich a concept when its description is empty or a generic placeholder the connector inserted (e.g. "SQLite table orders", "File config.yaml", "No description available", "Git file main.go"). Do not overwrite a substantive, human- or source-authored description unless the user explicitly asks you to regenerate. This keeps the operation idempotent and safe to re-run.

3. Gather grounding (never guess)

Base every claim on evidence in the document. Read only what you need:

• Schema (# Columns): names, types, keys, nullability → the shape of the concept.
• ## Data Profile (if present): per-column non-null / null / distinct / min / max. Signals: a 2–3-distinct column is likely a flag, enum, or status; min/max timestamps reveal the time span the data covers; a high null ratio flags optional fields.
  • Semantic column and Values: set (when present): the connector now detects a column's semantic type deterministically (email, uuid, iso-timestamp, monetary, boolean, enum, fk-ish) and, for low-cardinality columns, lists the literal distinct values as col ∈ {…}. Treat these as primary, near-mechanical grounding — an enum column with its Values set is almost a description on its own; restate it rather than re-deriving it from samples.
• ## Sample (if present): real example rows — the strongest signal for what the data actually means.
• Relationships: links in the body to other concept files → how this concept connects to others.

If the profile/sample sections are absent, enrich from the schema alone — but prefer to (re)produce the bundle with --profile --sample first when you can; it yields markedly better descriptions.

4. Write the description

• Grain first: state what one row / record / file represents, then its purpose — e.g. "One row per customer order, capturing line-item totals, payment status, and the placing customer."
• Length: one sentence for a table / dataset / file; a short noun phrase for a column.
• Ground every claim in the schema/profile/sample. Do not invent business meaning the evidence doesn't support. If the purpose is genuinely ambiguous, describe the structure and note what's uncertain rather than fabricating.
• Add meaning, don't restate: don't just list the columns the reader can already see — convey what the schema alone doesn't tell them.

4a. Explain relationships (optional — only when a # Relationships section exists)

The connector emits deterministic foreign-key edges as a # Relationships section (links to other concept files); SQL FKs and git co-change both land here. The edge is a fact; the meaning is missing — and supplying it is exactly the judgment the LLM is good at. For each edge, add one line of semantics grounded in the schema:

• Read the # Relationships links, the local # Columns (which column carries the FK), and the target concept's grain.
• Write a one-line gloss stating cardinality and meaning, e.g. "customer_id → customers: each order is placed by exactly one customer; a customer may have many orders."
• Ground cardinality in keys/uniqueness (a unique FK column → one-to-one; a non-unique one → many-to-one). If the direction is genuinely ambiguous, state the link factually and note the uncertainty — never invent a cardinality.
• Only describe edges the connector emitted — never fabricate a relationship the schema does not support.
• Surgical & idempotent: add prose only for edges that lack a gloss; preserve the deterministic link list (the connector owns it) and every existing human line. Do not reorder or rewrite edges. Safe to re-run.

4b. Suggest tags (optional)

Layer classification tags onto the connector's existing tags (e.g. [sqlite, table]):

• PII — combine the Semantic type (email, uuid) with column-name heuristics (email, phone, ssn, dob, first_name/last_name, address, ip). A confident match suggests a pii tag on the concept. Keep the catalog conservative — over-tagging pii erodes trust.
• Structural — natural, well-supported classifications (e.g. a table that is all FKs + a PK → join-table). Keep these advisory and few.
• Idempotent don't-clobber: add tags to the existing set (union, deduplicated, sorted for byte-stability); never remove or reorder connector- or human-set tags. Re-running yields the same set.

5. Write back surgically

• Set only the frontmatter description field. Preserve type, title, resource, timestamp, and (apart from the additions in §4a/§4b) the markdown body — including the Columns, Data Profile, and Sample sections — unchanged.
• Relationship prose (§4a): write glosses into the existing # Relationships section alongside the connector's links; never touch the link list itself, and never create the section when the connector did not.
• Tags (§4b): edit only the frontmatter tags field as a sorted, deduplicated union; never reorder or drop existing tags.
• Where the source carries per-column comments (see the Source variations table below), fill only the empty cells in that column; leave populated cells and every other cell untouched.
• Never modify index.md or log.md.

6. Close the loop (optional)

To persist enriched descriptions back to the origin system, run the matching connector's ingest --sync. See the Source variations table below for exactly what each connector writes back — and note that SQLite has no comment mechanism, so SQLite enrichment stays in the bundle (the descriptions still serve the catalog and any agent reading it).

The full flow:

<connector> produce --profile --sample   →   enrich (this skill)   →   <connector> ingest --sync

Cost & consistency

The model in the loop is the cost center. These four strategies make each token count and keep wording stable across runs. They turn re-enrichment from O(bundle) into O(changes).

Triage — enrich the valuable hubs first

Before spending tokens, rank the unenriched concepts and work the top of the list; a partial pass is a valid, resumable state (coverage is re-measurable). Rank by deterministic signals, highest first:

• Graph degree / downstream FK references — a concept many others link to (or point a foreign key at) is read most and deserves a good description first. The coverage report (run okf-viz coverage) can emit this ranked "enrich these first" list so you don't recompute it.
• Row count — large tables (from ## Stats / ## Data Profile) are usually core entities.
• Missing / placeholder description — only unenriched concepts are candidates.

Glossary reuse — define a recurring term once

A term like customer_id, created_at, or tenant_id recurs across dozens of concepts. Define it once and reuse it for consistency and token savings.

• The bundle may carry a glossary at its root: .okf-glossary.yaml, a flat term: definition map (kept out of the rendered graph and trivially diffable).
• Rule: before writing a column/description, check the glossary. If the term is known and the local usage matches the canonical meaning, reuse the glossary definition verbatim. Only write a fresh description when the term carries a genuinely novel meaning here — and consider proposing it as a new glossary entry.
• Reuse never overwrites a substantive existing description (don't-clobber holds).

Batching — one grounded pass per directory

Enrich a whole directory in one pass: read the index plus the frontmatter of that directory's concepts (per okf-reader), then write all their descriptions — rather than file-by-file round-trips that reload context each time. This cuts redundant context loading and keeps wording consistent within a related group.

Idempotency markers — skip what hasn't changed

Each concept carries a structural content_hash in its frontmatter (set by the connector). Record which hash a description was written against using the enriched_against frontmatter field:

• Skip a concept when enriched_against == content_hash and its description is non-placeholder — its structure is unchanged and its description is current.
• After writing a description, set enriched_against to the concept's current content_hash.
• A structural change (new column, type change) bumps content_hash, so enriched_against no longer matches and the concept automatically re-enters the candidate set — no full-bundle re-run needed. (produce preserves enriched_against across re-runs, so the marker survives.)

Writing the marker is a surgical frontmatter edit (never a body rewrite), exactly like the description write in §5 — so it stays byte-stable.

Source variations

Enrichment is the same procedure for every source — only three things differ per connector: where a description can live, what ingest --sync persists it to, and what to lean on when writing it. This table is the single place that per-source knowledge lives; the connectors themselves stay deterministic extract/sync tools.

Connector	Concept type	Description target(s)	ingest --sync writes to	Grounding signal
okf-sqlite	SQLite Table	frontmatter description only	schema only — no description sync (SQLite has no comments); enrichment stays in the bundle	# Columns + ## Data Profile + ## Sample
okf-mysql	MySQL Table	frontmatter description + Comment column	table & column comments (ALTER TABLE … COMMENT)	# Columns + profile + sample
okf-postgresql	PostgreSQL Table	frontmatter description + Comment column	table & column comments (COMMENT ON …)	# Columns + profile + sample
okf-bigquery	BigQuery Table	frontmatter description + Description column	table & field descriptions (BigQuery API)	# Columns + profile + sample
okf-fs	File / Directory	frontmatter description only	.okf-metadata.yaml	path, extension, size — infer role from name/type (no data content)
okf-git	Git File / Git Directory	frontmatter description only	.okf-metadata.yaml	path + last commit author/date/message in the body

Evaluating descriptions (optional)

Coverage (okf-viz coverage) counts how much is enriched; it cannot judge how well. For quality, an optional LLM-as-judge workflow lives in eval/: score a description's grounding, specificity, and conciseness against the rubric, using labelled fixtures as a regression baseline. It is run by your own model (no binary, no embedded model) and is advisory — use it to regression-test SKILL.md guidance changes and to flag low-confidence descriptions for human review.

Quality rules (summary)

1. Ground, don't guess — evidence in the document backs every word you write.
2. One field, surgical edits — touch description (and empty comment cells); preserve everything else byte-for-byte.
3. Concise and purposeful — grain plus purpose, never a restated schema.
4. Idempotent — don't clobber real descriptions; the procedure is safe to re-run.
5. Spend tokens deliberately — triage the hubs first, reuse the glossary instead of re-deriving a recurring term, batch per directory, and skip concepts whose enriched_against still matches their content_hash.
6. Enrich more than the description — gloss the connector's relationship edges with grounded cardinality and suggest conservative tags (pii, join-table), always as surgical, idempotent, union-only edits that describe only what the evidence supports.