des-persona-analytics-engineer

Design semantic model serving and consumer-facing interfaces for analytics metrics.

2|Updated May 20, 2026
One-click install
npx skills add https://github.com/DKSang/DES-SKILL --skill des-persona-analytics-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: des-persona-analytics-engineer
Source: https://github.com/DKSang/DES-SKILL/tree/main/skills/des-persona-analytics-engineer
Command: npx skills add https://github.com/DKSang/DES-SKILL --skill des-persona-analytics-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents metric and access inconsistencies by helping agents design consumer-ready serving and semantic layers that are performant, governed, and aligned with certified metric authority.

Core Features & Use Cases

  • Semantic + serving alignment: Define metric authority and serving interfaces so consumers use one consistent definition.
  • Access and trust controls: Specify RLS/access behavior and governance handoffs for sensitive or audit-bound data.
  • Performance and freshness planning: Choose caching/materialization strategies with explicit freshness expectations and consumer SLAs.
  • Use Case: When building a BI-facing dataset with certified KPIs, design RLS, caching, and query ergonomics so dashboards and APIs share the same metric meanings without duplicating logic.

Quick Start

Use des-persona-analytics-engineer to design the semantic metrics authority and serving layer for a consumer-facing analytics dataset with defined RLS and caching freshness expectations.

Frequently Asked Questions about des-persona-analytics-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a semantic model serving layer for consistent BI metrics?

Design a semantic model serving layer by defining certified metric authority and serving interfaces so BI dashboards and APIs share consistent metric meanings without duplicating logic. This ensures consumers access one trusted definition across all interfaces.

What is the best way to implement row-level security for consumer-facing analytics datasets?

Implement row-level security (RLS) by specifying explicit access behavior and testable governance handoffs for sensitive or audit-bound data. This ensures access controls remain trusted and enforceable when PII obligations exist within the serving layer.

How do I choose caching and materialization strategies for analytics serving layers?

Choose caching and materialization strategies by defining explicit freshness expectations and consumer SLAs for the analytics serving layer. This balances query performance against data freshness so dashboards remain responsive and trustworthy.

How does reverse ETL enablement work with a certified metrics layer?

Reverse ETL enablement works with a certified metrics layer by routing governed, consistent semantic definitions back into operational systems. This requires clear metric authority ownership and explicit SLA expectations to maintain trust across consumer access points.

How do I govern metric definitions across BI consumption and API access?

Govern metric definitions across BI consumption and API access by establishing one certified metric authority within the serving layer. This prevents metric inconsistencies by ensuring all consumer-facing interfaces apply the same tested logic and access rules.

When do I need a certified metric layer for my analytics dataset?

You need a certified metric layer when building consumer-facing analytics datasets requiring consistent KPIs, RLS policies, and caching freshness. It prevents logic duplication and access inconsistencies across BI dashboards, APIs, and operational access points.