database-designer
Use when the user asks to design database schemas, plan data migrations, optimize queries, choose between SQL and NoSQL, or model data relationships.
Repository SourceNeeds Review
data-architecture-frameworks
Pick and apply data architecture frameworks: TOGAF, DAMA-DMBOK, AWS Well-Architected (six pillars), Google's Five Cloud-Native Principles, Lambda vs Kappa, Modern Data Stack vs Live Data Stack, Data Mesh, Strangler Fig, FinOps, plus build-vs-buy and the four tech-selection axes (size, speed, cost, integration). Use when designing or evaluating a data platform's high-level architecture, deciding monolith vs modular vs serverless, or choosing between Lambda and Kappa for streaming workloads. Triggers: "Lambda or Kappa", "Modern Data Stack vs Data Mesh", "build vs buy data tooling", "evaluate our data architecture", "AWS Well-Architected for data", "Strangler Fig migration", "FinOps approach". Produces a chosen framework + reasoned technology selection.
Safety Notice
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Copy this and send it to your AI assistant to learn
Install skill "data-architecture-frameworks" with this command: npx skills add AlexYedi/skillsmp-alexyedi-alexyedi-data-architecture-frameworks
No markdown body
This source entry does not include full markdown content beyond metadata.
Source Transparency
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related Skills
Related by shared tags or category signals.
data-quality-auditor
Audit datasets for completeness, consistency, accuracy, and validity. Profile data distributions, detect anomalies and outliers, surface structural issues, and produce an actionable remediation plan.
Repository SourceNeeds Review
mdm-and-federated-data-governance
Apply Master Data Management (MDM) styles (Consolidation, Registry, Centralized, Coexistence), federated governance via data contracts and policy automation, data catalog + metalake architecture, knowledge graphs for metadata, semantic layers, and access control models (ACL, RBAC, ABAC + PEP/PDP/PIP/PAP). Use when scoping MDM, choosing an MDM style, designing a data catalog, building governance automation, defining data contracts, or implementing fine-grained access control on data products. Triggers: "MDM strategy", "consolidation vs registry vs centralized vs coexistence", "data contract", "data catalog", "knowledge graph for metadata", "ABAC for data", "semantic layer for governance", "metalake". Produces a chosen MDM style + governance architecture with policy automation.
Repository SourceNeeds Review
knowledge-graph-applications
Apply knowledge graph patterns for real applications: identity resolution (strong vs weak identifiers, Connected Components, SIMILAR), fraud detection (fraud rings, legitimate households), organizational graphs (org charts, expertise/skills graphs), dependency analysis (chains, multidependencies, redundant, SPOF, root cause), entity-based search, document similarity, and natural-language query/generation. Use when solving fraud detection, organizational analytics, dependency analysis, semantic search, or natural-language interfaces over a knowledge graph. Triggers: "fraud ring detection", "expertise graph", "single point of failure analysis", "root cause analysis with graphs", "entity-based search", "semantic search", "natural language to Cypher". Produces a pattern + query approach.
Repository SourceNeeds Review