agentleFS
rade-nugrohorade-nugroho/Agentic-Enteprises-Skill/bi-analyst/SKILL.md

bi-analyst

Skill9 starsChanged 6 months agoMITView on GitHub

Design dashboards, write analytical SQL, define KPIs, and manage stakeholder analytics requirements. Cover chart selection, data storytelling, cohort/funnel analysis, metric definitions, and BI tool patterns (Tableau, Looker, Power BI). Triggers on "build dashboard", "design dashboard", "write analytical SQL", "cohort analysis", "funnel analysis", "define KPI", "define metric", "reporting requirements", "data storytelling", "stakeholder analytics", "retention analysis", or "BI report". For business model canvas, TAM/SAM/SOM, and competitor monetization research, use business-model-researcher—not bi-analyst. For building warehouse marts, dbt models, tests, and lineage—not dashboards—use analytics-data-engineer.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the corresponding workflow below

    line 35
  2. Distinctive:

    Use size and color for emphasis, not decoration

    line 88

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Business Intelligence Analyst

Overview

Design dashboards, write analytical SQL, define KPIs, and manage stakeholder analytics requirements. This skill covers the full BI analyst workflow from dashboard design and chart selection through analytical SQL patterns, metric definition templates, and stakeholder engagement processes.

Features

  • Chart selection guidance for different analytical questions
  • SQL pattern library for cohort, funnel, retention, and cumulative analysis
  • Metric definition templates with formula, numerator, denominator, and data source
  • Stakeholder interview and engagement workflow
  • BI tool patterns for Tableau, Looker, and Power BI

Usage

  1. Identify the user's BI need (dashboard, SQL analysis, metrics, or stakeholder work)
  2. Follow the corresponding workflow below
  3. Produce structured outputs: dashboard wireframes, SQL queries, metric definitions, or stakeholder interview notes

Examples

  • User: "Build a retention dashboard" Agent: Runs Dashboard Design workflow, selects line chart for retention curves, applies F-pattern hierarchy, adds benchmark context
  • User: "Write SQL for cohort analysis" Agent: Runs Analytical SQL workflow, uses self-join on first-event date pattern, returns cohort retention table
  • User: "Define our churn metric" Agent: Runs Reporting & Metrics workflow, fills metric definition template with formula, numerator, denominator, data source

When to Use

  • Building or revising dashboards and self-serve BI reports
  • Writing analytical SQL for metrics, cohorts, funnels, or retention
  • Defining, documenting, or reconciling KPIs and business metrics
  • Presenting data insights or eliciting analytics requirements from stakeholders

When NOT to Use

  • Enterprise data platform, mesh, or governance architecture → use data-architect
  • Warehouse ETL design, incremental loads, or platform-specific tuning → use data-warehouse-engineer
  • dbt marts, incremental models, data tests, and docs/lineage → use analytics-data-engineer
  • Predictive modeling, experiment design, or ML productionization → use data-scientist
  • Business process mapping or BRD/FRD requirements without analytics delivery → use business-analyst
  • Business model research, market sizing, unit economics modeling → use business-model-researcher

Core Workflows

1. Dashboard Design

Design checklist:

  1. Define the audience and action
    • Who uses this dashboard? How often?
    • What decision does it support?
    • What action should they take after viewing?
  2. Choose the right charts
    QuestionChart Type
    How much/many?KPI cards, bar charts
    How does it change over time?Line charts, area charts
    How is it distributed?Histograms, box plots
    How do parts relate to the whole?Pie charts (limited), treemaps, stacked bars
    How do variables relate?Scatter plots, heatmaps
    Where is it happening?Maps, geo charts
  3. Apply visual hierarchy
    • Most important metrics at top left (F-pattern reading)
    • Use size and color for emphasis, not decoration
    • Limit to 3-5 colors per dashboard
    • Consistent formatting across all dashboards
  4. Add context
    • Benchmarks, targets, or prior period comparisons
    • Annotations for significant events
    • Last refresh timestamp

2. Analytical SQL

Common analysis patterns:

AnalysisSQL Pattern
Month-over-month growthLAG() window function
Running totalSUM() OVER (ORDER BY date)
Top N per groupROW_NUMBER() OVER (PARTITION BY group ORDER BY metric DESC)
Cohort retentionSelf-join on first-event date
Funnel conversionCOUNT(DISTINCT CASE WHEN step = N THEN user_id END)
Cumulative distinctCOUNT(DISTINCT user_id) OVER (ORDER BY date)

3. Reporting & Metrics

Metric definition template:

## [Metric Name]

**Definition:** [Clear, unambiguous description]
**Formula:** [Mathematical formula or SQL pseudocode]
**Numerator:** [What is counted]
**Denominator:** [The population, if a rate/ratio]
**Data source:** [Table(s) used]
**Dimensions:** [How it can be sliced: date, region, product]
**Owner:** [Who maintains this definition]
**Last updated:** [Date]

4. Stakeholder Management

Engagement workflow:

  1. Discovery: Interview stakeholders to understand business questions
  2. Prototype: Build a quick draft with sample data
  3. Review: Walk through with stakeholders; capture feedback
  4. Refine: Iterate based on feedback (limit to 2-3 rounds)
  5. Deliver: Deploy with documentation and training
  6. Maintain: Schedule quarterly reviews for relevance

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.