Create structured Markdown notes documenting data assets and their metadata.
npx skills add https://github.com/DavidROliverBA/ArchitectKB --skill dataasset
Please help me install this Agent Skill. Skill: /dataasset Source: https://github.com/DavidROliverBA/ArchitectKB/tree/main/.claude/skills/dataasset Command: npx skills add https://github.com/DavidROliverBA/ArchitectKB --skill dataasset
This Skill streamlines the process of documenting data assets, ensuring that critical information about data entities is captured and discoverable for AI and human collaborators.
Use the /dataasset skill to create a new entry for the 'Customer Orders' data asset.
High-intent search queries and answers about installing and using this skill.
To document data assets for AI discovery, you create structured Markdown notes capturing technical metadata like asset ID, data type, storage location, format, and ownership. This maintains a detailed inventory of data entities and their interdependencies, making critical information easily discoverable for both AI and human collaborators.
When documenting a database or API, capture technical metadata including asset ID, data type, domain, classification, storage location, and format. You should also record ownership details, consumer relationships, and governance information like GDPR applicability and PII fields to ensure comprehensive data lineage tracking.
Tracking data lineage for an event stream involves recording what the asset is derived from and what it feeds into. You also map current, planned, and deprecating consumers, alongside schema details and refresh frequency, to maintain clear interdependencies between data entities.
Yes, this data documentation approach works for both AI and human collaborators. By creating structured Markdown notes with standardized technical metadata and relationship mapping, it ensures that data assets are easily understandable for data engineers, analysts, and AI-driven data discovery systems alike.
The best way to maintain a data catalog of entities and their interdependencies is to systematically document each data asset using structured Markdown. This captures essential governance details, ownership, and lineage relationships, facilitating a detailed inventory that stays updated as systems evolve.
Yes, you can record data ownership and governance details like PII fields in your data documentation. The documentation process specifically accommodates recording data owners, stewards, and governance-related information, ensuring compliance and clear accountability for each data asset.
hsigstadGenerate a new data pipeline directory structure with boilerplate documentation.
aaronachermannQuery Unity Catalog system tables and volumes for governance metadata and lineage.
Ethical-AI-SyndicateManages a centralized registry of AI/ML models with metadata, risk, and compliance status.
crazymsnCatalog scientific datasets, models, and demos across 17 domains.
