yonglun/dama-skill / skills/managing-metadata
managing-metadata
VerifiedUse when data assets, business terms, technical schemas, operational runs, ownership, lineage, or usage must be discovered and kept current across systems; when building a catalog or metadata repository, recording and propagating approved definitions or surfacing conflicts for authoritative resolution, proving report provenance, or assessing downstream change impact.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.8 KB |
| agents/openai.yaml | config | 284 B |
| references/playbook.md | markdown | 13.1 KB |
| templates/delivery-pack.en.md | markdown | 3.1 KB |
| templates/delivery-pack.zh.md | markdown | 2.8 KB |
| templates/register.en.xlsx | binary | 8.6 KB |
| templates/register.zh.xlsx | binary | 9.1 KB |
| templates/report.en.docx | binary | 37.5 KB |
| templates/report.zh.docx | binary | 38.0 KB |
templates/delivery-pack.en.md
View on GitHub# Metadata Management Pack
Skill: `managing-metadata`
[Word report](report.en.docx) · [Excel register](register.en.xlsx)
## Record details
| ID | Field | Project value |
| --- | --- | --- |
| `artifact_id` | Artifact ID | |
| `project` | Project | |
| `skill` | Skill | |
| `version` | Version | |
| `date` | Date | |
| `status` | Status | |
| `author` | Author | |
| `owner` | Owner | |
| `approver` | Approver | |
| `purpose` | Purpose | |
| `business_outcome` | Business outcome | |
| `scope` | Scope and exclusions | |
| `source_inputs` | Inputs and sources | |
| `assumptions` | Assumptions and constraints | |
| `decisions` | Decisions | |
| `rationale` | Rationale | |
| `risks` | Risks | |
| `exceptions` | Exceptions | |
| `open_items` | Open items | |
| `due_date` | Due date | |
| `acceptance_criteria` | Acceptance criteria | |
| `evidence_location` | Evidence location | |
| `reviewer_decision` | Reviewer decision | |
| `next_gate` | Next stage gate | |
## Domain analysis and decisions
### Minimum metadata product (`metadata_product`)
Define minimum useful capabilities from discovery, understanding, and impact-analysis tasks.
> Enter project evidence, conclusion, and owner.
### Sources and consumers (`source_inventory`)
List technical, business, and operational metadata sources and users.
> Enter project evidence, conclusion, and owner.
### Metamodel and architecture (`metamodel`)
Choose centralized, distributed, or hybrid design with IDs, relationships, and sync ownership.
> Enter project evidence, conclusion, and owner.
### Business glossary (`glossary`)
Record definition approval, synonyms, disputes, versions, and effective dates.
> Enter project evidence, conclusion, and owner.
### Designed and actual lineage (`lineage`)
Separate designed mappings from observed runs and trace fields to consuming outputs.
> Enter project evidence, conclusion, and owner.
### Quality freshness and coverage (`freshness`)
Define refresh deadlines, coverage denominators, quality rules, and adoption measures.
> Enter project evidence, conclusion, and owner.
### Impact analysis and change gate (`impact_analysis`)
Trace schema or term changes downstream and set review gates.
> Enter project evidence, conclusion, and owner.
### Permissions and acceptance (`acceptance_evidence`)
Verify sensitive-metadata access, discovery tasks, and lineage evidence.
> Enter project evidence, conclusion, and owner.
## Working registers
### Business Glossary (`glossary`)
Maintain term definitions and approval ownership.
| Term (`term`) | Definition (`definition`) | Source (`source`) | Owner (`owner`) | Approver (`approver`) | Version (`version`) | Status (`status`) |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |
### Field Lineage (`lineage`)
Trace field source, consumers, and implementation evidence.
| Source field (`source_field`) | Target field (`target_field`) | Transformation (`transformation`) | Consumer (`consumer`) | Owner (`owner`) | Evidence (`evidence`) | Review date (`review_date`) |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |