datacoolie

@datacoolie source repo

13 skills
0 followers
11 hours ago last updated

▌
Datacoolie Build · datacoolie bundle
Build, modify, materialize, run, and verify DataCoolie projects. Use for workspace bootstrap, metadata authoring, environment overlays, capability checks, runners, notebooks, custom functions, narrow unsupported adapters, local tests, immutable builds, and project-owned build/CI automation. This is the sole implementation skill for pipeline and build artifacts; it does not discover sources, make material design decisions, provision infrastructure, or deploy releases.

0
installs
▌
Datacoolie Design · datacoolie bundle
Design or materially revise a DataCoolie project's stage graph, transition contracts, model grain, keys, load strategy, platform intent, quality/recovery policy, infrastructure requirements, or release policy. Use for new projects and architecture-affecting changes; skip it for implementation-only metadata, runner, function, test, or release work that preserves the current design.

0
installs
▌
Datacoolie Release · datacoolie bundle
Plan, preflight, deploy, promote, roll back, or author consume-only release automation for an exact verified DataCoolie build. Use for explicit deployment-lifecycle work; read-only planning may precede authorization, while target mutation requires exact authorization. This skill consumes immutable build artifacts and never authors metadata or pipeline code, generates runners, rebuilds functions, provisions resources, or changes pipeline behavior.

0
installs
▌
Datacoolie Discover · datacoolie bundle
Inspect data sources and produce verified source evidence for DataCoolie design or build work. Use for every new DataCoolie project before design, for every declared source type, and when an existing source is new, changed, missing evidence, or contradictory. Discovery is read-only evidence and never creates runtime metadata, workspace code, infrastructure, or releases.

0
installs
▌
Datacoolie Provision · datacoolie bundle
Plan, validate, create, update, reconcile, or remove infrastructure required by a DataCoolie environment. Use only for an explicit infrastructure request or an evidenced resource gap from build or release. Inventory and preview are allowed without mutation approval; every apply requires approval bound to the exact environment and persisted plan. Never use this skill to change pipeline behavior, build artifacts, or releases.

0
installs
▌
Power Bi Management · datacoolie bundle
Manage and deploy Power BI report items in Microsoft Fabric workspaces via a tested Fabric REST helper (`az rest`). Use this skill for CLOUD TRANSPORT and lifecycle operations — NOT for authoring local content. Triggers: publish/upload/push/deploy a report to Fabric, download/get a report definition from Fabric, list workspace reports, update report properties, delete a report, publish a local `.pbip` to a workspace. For editing local PBIR content (pages, visuals, filters, themes, formatting) use `power-bi-report-authoring`. For building/deploying the semantic model use `power-bi-semantic-model`. This is the `az rest` Tier-2 lane: Power BI authoring stays MCP/local-first; only cloud transport (which has no MCP path) lives here.

0
installs
▌
Power Bi Report Design · datacoolie bundle
Design Power BI report layouts, select chart types, plan page structures, choose themes, and apply data storytelling principles BEFORE generating PBIR JSON files. Use this skill whenever the user asks to design a report, plan a dashboard layout, choose visualizations, decide on chart types, apply storytelling to data, select a theme or color palette, plan page navigation, or structure report pages for a Power BI project. Also use when the user provides requirements and needs a report design spec before generation, or when reviewing/improving an existing report's visual design, layout, or UX. This skill produces a Design Spec — a structured plan of pages, visuals, layout, theme, and navigation — that feeds into the `power-bi-report-authoring` skill for JSON generation. Do NOT use for generating PBIR JSON files, validating report structure, or building the semantic model. For JSON generation, use `power-bi-report-authoring`.

0
installs
▌
Power Bi Semantic Model · datacoolie bundle
Design and build Power BI semantic models using star schema principles and the PowerBI Modeling MCP tools. Use this skill whenever the user wants to build a semantic model, create a data model, design a star schema, add tables or columns, create or modify relationships, configure storage modes (Import, DirectQuery, DirectLake, Composite), implement RLS (Row-Level Security), optimize model performance, or explore existing data sources for modeling. Triggers include: "build semantic model", "create data model", "star schema", "add table", "create relationship", "storage mode", "DirectLake", "composite model", "RLS", "optimize model", "model review", "explore data", "connect to gold layer", "extend model", "add dimension", "add fact table". Do NOT use for DAX measure creation (use power-bi-dax-development) or report generation (use power-bi-report-authoring).

0
installs
▌
Power Bi Dax Development · datacoolie bundle
Develop, optimize, and validate DAX measures, calculation groups, visual calculations, field parameters, dynamic format strings, time intelligence, semi-additive logic, virtual relationships with TREATAS, DAX window functions, and user-defined functions for Power BI semantic models. Use for requests to write or optimize DAX, create measures, explain CALCULATE or evaluation context, build YTD/YoY/WTD logic, use RUNNINGSUM or MOVINGAVERAGE, rank with RANK/ROWNUMBER/OFFSET/INDEX/WINDOW, or apply advanced DAX patterns. Research Microsoft Learn MCP before recommending patterns.

0
installs
▌
Power Bi Report Authoring · datacoolie bundle
Create and modify Power BI report files in PBIR/PBIP format using the `powerbi-report-author` and `powerbi-desktop` CLIs. Use when the user wants to: (1) implement an approved report spec or design brief, (2) add or edit pages, visuals, filters, slicers, bookmarks, themes, or formatting, (3) validate PBIR and verify rendering in Power BI Desktop. For open-ended visual design, use `power-bi-report-design` first. For end-to-end requirements and approval workflow, use `powerbi-report-planning` first. Triggers: "edit PBIR", "create Power BI report page", "add visual to PBIP", "format report visual", "validate Power BI report", "reload Desktop screenshot", "implement an approved PBIP report spec", "edit PBIR pages/visuals".

0
installs
▌
Power Bi Business Analysis · datacoolie bundle
Analyze business requirements and define BI strategy for Power BI projects. Use this skill whenever the user wants to analyze business requirements, identify KPIs, define what insights a report should deliver, propose dashboard structure for a business domain, or gather requirements before building a Power BI report or semantic model. Triggers include: "analyze business requirements", "what KPIs should we track", "what insights can we get", "business domain analysis", "requirements gathering", "what should we measure", "what problems can we solve", "propose a dashboard", "what reports do we need", "BI strategy", "define metrics". Do NOT use for actual model building (use power-bi-semantic-model), DAX writing (use power-bi-dax-development), or report generation (use power-bi-report-authoring).

0
installs
▌
Power Bi Feedback Iteration · datacoolie bundle
Reference kit for the feedback and iteration phase of a Power BI project. Provides classification taxonomy, prioritization matrix, intake template, change-impact scoping, post-change validation checklist, A/B variant testing workflow, formal UAT workflow, PBIP Git diff guide, changelog template, and a performance quick-check pointer. Use this skill whenever the user provides feedback on an existing Power BI report, requests iteration, wants to run UAT, or needs to document changes. Routing (feedback → correct downstream skill) is owned by the power-bi-developer agent, not by this skill. Triggers include: "user feedback", "improve report", "fix report", "iterate on the report", "report review", "rebuild report", "UAT", "changelog", "release notes", "users are complaining", "performance issue", "add/remove/modify a page/measure/visual on an existing report". Do NOT use this skill for brand-new projects (use power-bi-business-analysis to start from scratch).

0
installs
▌
Power Bi Performance Troubleshooting · datacoolie bundle
Diagnose and resolve Power BI performance issues across models, DAX queries, report visuals, and data refresh. Use this skill whenever the user reports slow report loading, slow visual interactions, long refresh times, high memory usage, query timeouts, or capacity bottlenecks. Triggers include: "report is slow", "performance issue", "optimize report", "slow loading", "query timeout", "refresh takes too long", "high memory", "report performance", "visual is slow", "optimize model", "reduce model size", "aggregation table", "incremental refresh", "Performance Analyzer", "DAX Studio", "server timings", "capacity metrics". Do NOT use for initial model design (use power-bi-semantic-model), initial DAX development (use power-bi-dax-development), or report design decisions (use power-bi-report-design). This skill is for diagnosing and fixing performance problems in existing solutions.

0
installs

13 published skills