kpi-metrics

id: SKL-kpi-KPIMETRICS name: Kpi Metrics description: KPIs are measurable values that demonstrate how effectively an organization is achieving key business objectives. Effective KPIs are aligned with business goals, actionable, trackable over time, and d version: 1.0.0 status: active owner: '@cerebra-team' last_updated: '2026-02-22' category: Backend tags:

• api
• backend
• server
• database stack:
• Python
• Node.js
• REST API
• GraphQL difficulty: Intermediate

Kpi Metrics

Skill Profile

(Select at least one profile to enable specific modules)

• DevOps
• Backend
• Frontend
• AI-RAG
• Security Critical

Overview

KPIs are measurable values that demonstrate how effectively an organization is achieving key business objectives. Effective KPIs are aligned with business goals, actionable, trackable over time, and drive decision-making. This skill covers defining KPIs using the SMART framework, tracking them through data collection systems, and visualizing them in dashboards for business insights.

Why This Matters

• Focus: Align team on priorities and strategic goals
• Accountability: Clear ownership of metrics and outcomes
• Decision-making: Enable data-driven choices instead of gut feelings
• Performance: Track progress over time and identify trends
• Improvement: Identify areas to optimize and measure impact of changes

Core Concepts & Rules

1. Core Principles

• Follow established patterns and conventions
• Maintain consistency across codebase
• Document decisions and trade-offs

2. Implementation Guidelines

• Start with the simplest viable solution
• Iterate based on feedback and requirements
• Test thoroughly before deployment

Inputs / Outputs / Contracts

• Inputs:
  • Business objectives and goals
  • Data sources (database, analytics tools, APIs)
  • Metric definitions and formulas
  • Target values and benchmarks
• Entry Conditions:
  • Clear business objectives defined
  • Data collection infrastructure in place
  • Stakeholders identified and aligned
• Outputs:
  • KPI definitions document
  • Tracking queries and data pipelines
  • Dashboard configurations
  • KPI reports and insights
• Artifacts Required (Deliverables):
  • KPI Definition Document (with formulas, owners, targets)
  • SQL queries or data collection scripts
  • Dashboard configuration files
  • Regular KPI reports
• Acceptance Evidence:
  • KPI definitions reviewed and approved
  • Data accuracy validated
  • Dashboard accessible to stakeholders
  • Regular reporting schedule established
• Success Criteria:
  • All KPIs follow SMART framework
  • Data collection automated and reliable
  • Dashboards provide actionable insights
  • Stakeholders use KPIs for decision-making

Skill Composition

• Depends on: dashboard-design, business-intelligence, sql-for-analytics
• Compatible with: ab-testing-analysis, cohort-analysis, funnel-analysis
• Conflicts with: None
• Related Skills: data-visualization, conversion-optimization

Quick Start

Assumptions / Constraints / Non-goals

• Assumptions:
  • Development environment is properly configured
  • Required dependencies are available
  • Team has basic understanding of domain
• Constraints:
  • Must follow existing codebase conventions
  • Time and resource limitations
  • Compatibility requirements
• Non-goals:
  • This skill does not cover edge cases outside scope
  • Not a replacement for formal training

Compatibility & Prerequisites

• Supported Versions:
  • Python 3.8+
  • Node.js 16+
  • Modern browsers (Chrome, Firefox, Safari, Edge)
• Required AI Tools:
  • Code editor (VS Code recommended)
  • Testing framework appropriate for language
  • Version control (Git)
• Dependencies:
  • Language-specific package manager
  • Build tools
  • Testing libraries
• Environment Setup:
  • .env.example keys: API_KEY, DATABASE_URL (no values)

Test Scenario Matrix (QA Strategy)

Technical Guardrails & Security Threat Model

1. Security & Privacy (Threat Model)

• Top Threats: Injection attacks, authentication bypass, data exposure

• Data Handling: Sanitize all user inputs to prevent Injection attacks. Never log raw PII
• Secrets Management: No hardcoded API keys. Use Env Vars/Secrets Manager
• Authorization: Validate user permissions before state changes

2. Performance & Resources

• Execution Efficiency: Consider time complexity for algorithms
• Memory Management: Use streams/pagination for large data
• Resource Cleanup: Close DB connections/file handlers in finally blocks

3. Architecture & Scalability

• Design Pattern: Follow SOLID principles, use Dependency Injection
• Modularity: Decouple logic from UI/Frameworks

4. Observability & Reliability

• Logging Standards: Structured JSON, include trace IDs request_id
• Metrics: Track error_rate, latency, queue_depth
• Error Handling: Standardized error codes, no bare except
• Observability Artifacts:
  • Log Fields: timestamp, level, message, request_id
  • Metrics: request_count, error_count, response_time
  • Dashboards/Alerts: High Error Rate > 5%

Agent Directives & Error Recovery

(ข้อกำหนดสำหรับ AI Agent ในการคิดและแก้ปัญหาเมื่อเกิดข้อผิดพลาด)

• Thinking Process: Analyze root cause before fixing. Do not brute-force.
• Fallback Strategy: Stop after 3 failed test attempts. Output root cause and ask for human intervention/clarification.
• Self-Review: Check against Guardrails & Anti-patterns before finalizing.
• Output Constraints: Output ONLY the modified code block. Do not explain unless asked.

Definition of Done (DoD) Checklist

• Tests passed + coverage met
• Lint/Typecheck passed
• Logging/Metrics/Trace implemented
• Security checks passed
• Documentation/Changelog updated
• Accessibility/Performance requirements met (if frontend)

Anti-patterns

Reference Links & Examples

• Internal documentation and examples
• Official documentation and best practices
• Community resources and discussions

Versioning & Changelog

• Version: 1.0.0
• Changelog:
  • 2026-02-22: Initial version with complete template structure