kpi-analyst

Derive auditable business KPIs from verifiable lab data into a structured registry.

9|Updated May 24, 2026
One-click install
npx skills add https://github.com/picmakpro/vibeflow-os --skill kpi-analyst-picmakpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kpi-analyst
Source: https://github.com/picmakpro/vibeflow-os/tree/main/plugin/kpi-analyst
Command: npx skills add https://github.com/picmakpro/vibeflow-os --skill kpi-analyst-picmakpro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents teams from managing a business with misleading activity counters or invented figures by deriving real KPIs from verifiable lab data and preserving the source behind every value.

Core Features & Use Cases

  • KPI Schema Design: Infer three to six relevant business indicators from a lab brief, then freeze their keys after explicit human validation.
  • Deterministic Extraction: Create and run repeatable extractors for revenue, leads, MRR, conversion, views, engagement, and other domain-specific metrics without recalculating values through LLM reasoning.
  • Auditable Publishing: Assemble a structured KPIS registry with source references, confidence levels, trends, and machine-readable data for standalone use or optional dashboard ingestion.
  • Governed Data Acquisition: Keep external data collection human-gated, read-only, scoped, and clearly separated from internal source extraction.

Quick Start

Ask the KPI analyst to configure the lab indicators from its brief, validate the proposed schema, create deterministic extractors, and publish the first KPI registry.

Frequently Asked Questions about kpi-analyst

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

FAQPage Schema
How do I derive business KPIs from scattered data without relying on invented metrics?

To derive business KPIs from scattered data without invented metrics, use deterministic extractor scripts that pull verifiable values from lab sources. This ensures every published indicator cites its origin, preventing reliance on meta-level activity counters.

What is the best way to track revenue and MRR without recalculating values through LLM reasoning?

The best way to track revenue and MRR deterministically is by creating repeatable extractor scripts that query source data directly. This bypasses LLM reasoning, ensuring KPI analysis yields verifiable, stable figures for your registry.

How do you build an auditable KPI registry with source references and confidence levels?

Building an auditable KPI registry involves assembling structured data from deterministic extraction, attaching source references and confidence levels to each value. This creates a machine-readable output for dashboard reporting and tracking.

Do I need a human-validated schema before configuring lead analytics and revenue tracking?

Yes, you need a human-validated stable schema before configuring lead analytics and revenue tracking. Freezing indicator keys after explicit validation ensures deterministic extraction remains repeatable and prevents schema drift.

Can I use jq for deterministic extraction and governed data acquisition in KPI analysis?

Yes, you can use jq for deterministic extraction during KPI analysis. It supports governed data acquisition by keeping external data collection human-gated, read-only, and scoped, separating internal extraction from external sources.

Why does KPI analysis fail when using misleading activity counters instead of verifiable lab data?

KPI analysis fails with misleading activity counters because they lack data provenance and reflect meta-level activity rather than true business metrics. Deriving values from verifiable lab data ensures trustworthy, auditable reporting.