[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4FFP0KWVDA7CS3247Z2YJ":3,"skill-same:01M7F4FFP0KWVDA7CS3247Z2YJ":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7F4FFP0KWVDA7CS3247Z2YJ","data-model-design",null,"Design or review conceptual, logical, physical, relational, dimensional, Data Vault, or event models with explicit grain, identity, relationships, history, naming, and evolution. Use when defining a dataset schema or changing its business meaning.","cwik-tech\u002Foctopus","cwik-tech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54542292?v=4","01M7F42E123GEHVK6RWC5MSWJ9","Tomasz Cwik","01M7F42E1PD4P54MTG8PG32VCV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fdata-modeling-metadata-engineer\u002Fskills\u002Fdata-model-design\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: data-model-design\ndescription: >\n  Design or review conceptual, logical, physical, relational, dimensional, Data Vault, or event models with explicit grain, identity, relationships, history, naming, and evolution. Use when defining a dataset schema or changing its business meaning.\n---\n\n# Data Model Design\n\n## Method\n\n1. State the business process or subject area, consumers, authority, and one-sentence grain before naming fields.\n2. Choose the model layer and pattern from the consumer and change requirements. Do not mix conceptual, logical, and physical concerns silently.\n3. Define entities, facts, dimensions, events, relationships, cardinality, optionality, and lifecycle.\n4. Define natural, surrogate, composite, and foreign keys; identity resolution; reference data; and duplicate semantics.\n5. Define time and history, including effective time, recorded time, slowly changing dimensions, corrections, and late data.\n6. Define types, units, null semantics, defaults, constraints, normalization or denormalization, and derived values.\n7. Apply naming rules and attach business, technical, operational, classification, ownership, and lineage metadata.\n8. Define compatibility, migrations, backfills, deprecation, validation, and consumer impact for evolution.\n\n## Pattern checks\n\n- Relational models protect transactional integrity and update behavior.\n- Dimensional models begin with grain and consumer questions, then facts and dimensions.\n- Data Vault separates stable business identity from changing descriptive context and relationships.\n- Event models preserve the meaning, identity, ordering, and time of facts that occurred.\n\n## Shared resources\n\nLoad only the resources needed for the current task. The links resolve inside the current agent package.\n\n- `..\u002F..\u002Ftemplates\u002Fdataset-specification.md`\n- `..\u002F..\u002Ftemplates\u002Fdata-model-review.md`\n- `..\u002F..\u002Freferences\u002Fnaming-conventions.md`\n- `..\u002F..\u002Freferences\u002Fmetadata-minimum-standard.md`\n\n## Output\n\nReturn the grain, model diagram or structured definition, key and relationship rules, temporal behavior, constraints, metadata, quality implications, evolution plan, and open decisions.\n","# Data Model Design\n\n## Method\n\n1. State the business process or subject area, consumers, authority, and one-sentence grain before naming fields.\n2. Choose the model layer and pattern from the consumer and change requirements. Do not mix conceptual, logical, and physical concerns silently.\n3. Define entities, facts, dimensions, events, relationships, cardinality, optionality, and lifecycle.\n4. Define natural, surrogate, composite, and foreign keys; identity resolution; reference data; and duplicate semantics.\n5. Define time and history, including effective time, recorded time, slowly changing dimensions, corrections, and late data.\n6. Define types, units, null semantics, defaults, constraints, normalization or denormalization, and derived values.\n7. Apply naming rules and attach business, technical, operational, classification, ownership, and lineage metadata.\n8. Define compatibility, migrations, backfills, deprecation, validation, and consumer impact for evolution.\n\n## Pattern checks\n\n- Relational models protect transactional integrity and update behavior.\n- Dimensional models begin with grain and consumer questions, then facts and dimensions.\n- Data Vault separates stable business identity from changing descriptive context and relationships.\n- Event models preserve the meaning, identity, ordering, and time of facts that occurred.\n\n## Shared resources\n\nLoad only the resources needed for the current task. The links resolve inside the current agent package.\n\n- `..\u002F..\u002Ftemplates\u002Fdataset-specification.md`\n- `..\u002F..\u002Ftemplates\u002Fdata-model-review.md`\n- `..\u002F..\u002Freferences\u002Fnaming-conventions.md`\n- `..\u002F..\u002Freferences\u002Fmetadata-minimum-standard.md`\n\n## Output\n\nReturn the grain, model diagram or structured definition, key and relationship rules, temporal behavior, constraints, metadata, quality implications, evolution plan, and open decisions.\n",{"name":5,"description":7},"main","f0f0efe1d4c64b51a51f44427ad147750d29154e","agents\u002Fdata-modeling-metadata-engineer\u002Fskills\u002Fdata-model-design","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus","www.cuteoctopus.site","https:\u002F\u002Fgithub.com\u002Fcwik-tech","2026-10-27 06:12:19",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add cwik-tech\u002Foctopus --skill data-model-design",{"tool":37,"command":38},"bunx","bunx skills add cwik-tech\u002Foctopus --skill data-model-design",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cwik-tech\u002Foctopus --skill data-model-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fagents\u002Fdata-modeling-metadata-engineer\u002Fskills\u002Fdata-model-design\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7F5MQVQ3CHGM77Q51M4B1AC","twenty-year-land-plan","Apply the Bren discipline of evaluating every land and development decision on a twenty-year horizon, with a comprehensive plan for how the land, the community, and the surrounding public infrastructure evolve together. Deals optimized for a five-year exit are structurally different from deals that compound across generations; insist on knowing which kind you are making. Use when evaluating land, entitlements, master-planned development, or phasing decisions, and when separating five-year exit deals from generational holds.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Ftwenty-year-land-plan\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7F5MGQ8JSV27SFDQVVGFQE3","thematic-gut-check","Apply the Gray discipline of identifying the structural theme behind every real estate deal, testing where that theme sits in its capital-flow lifecycle, and insisting that deals without a named theme — or deals late in a crowded theme — clear a higher bar. A mediocre deal in a strong theme usually beats a clever deal in a weak one. Use when naming the structural thesis behind a deal, judging whether that theme is early or crowded, and setting the bar the deal must clear.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fthematic-gut-check\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7F5M8V64Y0ZD8PTPWEJQXJ9","supply-pipeline-gut-check","Apply the Zell discipline of grounding every real estate thesis in the local supply pipeline. Demand counts over adjectives — units under construction, units permitted, units proposed — and convert them into a forward absorption schedule. A deal that ignores the pipeline is a bet on a market you have not actually studied. Use when validating a market thesis, forecasting absorption and rent growth, or counting units under construction, permitted, and proposed.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fsupply-pipeline-gut-check\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7F5M3J2Q146BJC13TD3YCXF","ruin-scenario-mapping","Apply the Taleb discipline of identifying, for every real estate deal, the specific chain of events that produces ruin — permanent, unrecoverable capital loss — and verifying that no single such chain has non-trivial probability. Deals with any plausible ruin path must be restructured or abandoned. Use when sizing leverage, testing refinancing, covenant, and liquidity risk, or checking whether any single failure chain can permanently wipe out the position.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Fruin-scenario-mapping\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7F5KZDS0DYD172P6HS0WXEM","revenue-cost-architecture","Design a venture's revenue streams, pricing logic, cost structure, and unit economics so the business model has a coherent theory of value capture, not just value creation. Use after the value proposition and customer segment are set and before financial projections, when choosing a pricing model, calculating contribution margin or CAC payback, or checking whether the unit economics hold at scale.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Frevenue-cost-architecture\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7F5KP1CNQMYAVCDTV4EEW3J","replacement-cost-stress-test","Apply the Buffett discipline of pricing every real estate asset against the cost to rebuild it from scratch. The ratio of purchase price to replacement cost sets a ceiling on long-run downside: below replacement cost, new supply cannot profitably undercut you; at or above it, you are buying a liability disguised as an asset. Use when setting a purchase price, judging downside protection, or testing how exposed an asset is to newly built competing supply.","https:\u002F\u002Fgithub.com\u002Fcwik-tech\u002Foctopus\u002Fblob\u002Fmain\u002Fskills\u002Freplacement-cost-stress-test\u002FSKILL.md",[],[]]