Index of every page on this site: llms.txt
All skills
nimrodfisher avatar

/data-catalog-entry

@9449d36
Run it yourself

Create standardized metadata for data assets. Use when documenting new datasets, building data catalogs, improving data discoverability, or creating data dictionaries for teams.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/data-catalog-entry

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈49 tokens for metadata: the name and description. ≈564 when used: this file. ≈1.2k more on demand in 2 files.

Description uses 2.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈198 characters, or 2.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Data Catalog Entry

When to use

  • A new table, view, or dataset has been created and needs to be discoverable
  • Analysts keep asking the same questions about a table's meaning or ownership
  • A compliance or audit requirement mandates documentation of sensitive data
  • Onboarding new team members who need to understand available data assets
  • Auditing catalog completeness to find undocumented tables

Process

  1. Extract technical metadata — pull schema, column names, types, primary keys, foreign keys, and row count from INFORMATION_SCHEMA or the source system. Use scripts/catalog_extractor.py to automate this for database tables.
  2. Collect business context — interview the data owner to capture the business purpose, owning team, criticality (critical / high / medium / low), and known use cases. Record the business-friendly display name.
  3. Write column descriptions — for each column, write a one-sentence plain-language description, note example values, and document any business rules (valid values, constraints, format requirements).
  4. Assess data quality — calculate or estimate completeness, freshness (hours since last update), and duplicate rate. Document known issues and how they affect downstream use.
  5. Document lineage — record upstream sources (where the data comes from) and downstream consumers (dashboards, models, reports that depend on it).
  6. Add governance details and publish — specify access level (public/restricted/confidential), sensitivity (PII, financial, health), compliance tags, retention policy, and access instructions. Complete assets/catalog_entry_template.md and submit to the catalog.

Inputs the skill needs

  • Connection or export from the database/source system for technical metadata
  • Data owner contact for business context interview
  • Knowledge of upstream sources and downstream consumers
  • Applicable governance policies (PII classification, retention rules)
  • Any existing partial documentation or data dictionary

Output

  • scripts/catalog_extractor.py — extracts schema and basic stats from a database table
  • assets/catalog_entry_template.md — completed catalog entry with technical, business, quality, lineage, and governance sections

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo4 checks · Risk MEDIUM
  • Gen Agent Trust Hub2mo

    The skill includes a Python automation script that is vulnerable to SQL injection and encourages insecure credential handling by passing database passwords in plain text via command-line arguments.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9449d36. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 7 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/data-catalog-entry