ai-analytics
/ai-analytics
Pomaga projektować analitykę AI: dashboardy, metryki AI w SaaS, analitykę NLP i predykcyjną oraz raporty z wnioskami dla zarządu.
- Autor
- peterbamuhigire ↗
- Repozytorium
- chwezi-dev-engine ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 24.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 8
- Skrypty
- 0
- Komentarze HTML
- 2
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 24.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
Co robi i kiedy
Pomaga projektować analitykę AI: dashboardy, metryki AI w SaaS, analitykę NLP i predykcyjną oraz raporty z wnioskami dla zarządu.
Oryginalny opis (EN)
Use when designing AI analytics, dashboards, SaaS AI metrics, NLP analytics, predictive analytics, or executive AI insight workflows. Orchestrates the former granular AI analytics skills as references.
Jak działa
- Operating contract
- Inputs
- Outputs
- Capability and permission boundaries
- Degraded mode
- Decision rules
- Anti-Patterns
- Use When
- Do Not Use When
- Required Inputs
Podgląd SKILL.md
--- name: ai-analytics description: Use when designing AI analytics, dashboards, SaaS AI metrics, NLP analytics, predictive analytics, or executive AI insight workflows. Orchestrates the former granular AI analytics skills as references. metadata: portable: true compatible_with: - claude-code - codex --- # AI Analytics ## Operating contract ## Inputs | Input | Required | Purpose | |---|---|---| | Domain evidence | yes | business question, decision owner, governed data sources, metric definitions, population, and time window | ## Outputs - Produce: metric specification, analysis or dashboard design, uncertainty notes, validation results, and decision recommendation. ## Capability and permission boundaries Default to read-only analysis. Read only scoped records; redact secrets and regulated data. Writes, execution, network calls, production configuration, customer communication, billing changes, and delegation require explicit authority and an identified owner. Never widen tenant, time-window, or system scope implicitly. ## Degraded mode When required telemetry, evidence, execution, network access, or write authority is unavailable, return a partial result with each unassessed item labelled, preserve the safest existing state, and state the evidence or approval needed to continue. Never convert missing evidence into a pass. ## Decision rules | Condition | Action | |---|---| | Scope, owner, or threshold is missing | Stop the affected decision and request it | | Evidence is incomplete but read-only analysis is safe | Produce a qualified partial result and gap list | | A mutation exceeds authority or tenant boundary | Block it and route for approval | | Evidence meets the stated threshold | Issue the output with provenance and owner | ## Anti-Patterns - Treating absent evidence as success. Fix: mark the check unassessed and name the missing source. - Expanding one tenant or workflow to all tenants. Fix: enforce supplied scope at every query and action. - Performing a production write during analysis. Fix: emit a reviewed change plan until authority is explicit. - Reporting a metric without population, window, or source. Fix: attach all three. - Hiding a failed threshold inside an average. Fix: report failure slices and the remediation owner. Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178. <!-- dual-compat-start --> ## Use When - Design AI analytics products, metric trees, dashboards, and AI insight workflows. - Plan SaaS AI analytics, NLP analytics, predictive analytics, or reporting surfaces. - Choose the right analytics reference from consolidated child modules. ## Do Not Use When - The work is not AI-specific or agentic-AI-specific. - A narrower retained AI parent skill fits the request better. ## Required Inputs - Product, tenant, user, data, risk, and operational context relevant to the AI workflow. - Target artifact: design, implementation plan, audit, test strategy, UX flow, commercial policy, or runbook. - Constraints from security, privacy, reliability, billing, support, and compliance stakeholders when relevant. ## Workflow 1. Read this SKILL.md first. 2. Load [references/routing.md](references/routing.md) to select the absorbed child reference that matches the task. 3. Load only the selected child reference files needed for the current request. 4. Produce execution-oriented output with assumptions, risks, evidence, and next actions where relevant. ## Quality Standards - Keep routing explicit: name which reference files were used when the work depends on absorbed material. - Preserve tenant isolation, auditability, cost controls, safety gates, and operational evidence when they matter. - Prefer concrete contracts, checklists, tables, schemas, runbooks, and decision records over broad summaries. ## Anti-Patterns - Loading every absorbed reference by default. - Treating AI-specific billing, compliance, safety, or UX concerns as generic SaaS work without checking AI failure modes. - Hiding retired skill names; old slugs must remain discoverable through [references/routing.md](references/routing.md). ## Outputs - A concrete deliverable matched to the request: architecture, implementation plan, audit, policy, runbook, UX flow, test strategy, or operating model. - The selected consolidated reference files and any assumptions, risks, evidence requirements, or follow-up actions that affect execution. ## References - [references/routing.md](references/routing.md) maps retired child skill slugs to their consolidated reference folders. ## Consolidated Child References - Load [references/routing.md](references/routing.md) to map retired AI child skill slugs to their reference modules. ## Evidence Produced | Category | Artifact | Format | Example | | --- | --- | --- | --- | | Correctness | AI analytics metric specification | Markdown plus validated query | metric definition, grain, population, exclusions, lineage, and reconciliation | <!-- dual-compat-end -->
Pliki w paczce (8)
- SKILL.md 5 KB
- references/routing.md 1 KB
- references/ai-analytics-dashboards/entrypoint.md 14 KB
- references/ai-analytics-saas/entrypoint.md 15 KB
- references/ai-analytics-strategy/entrypoint.md 11 KB
- references/ai-analytics-strategy/references/business-analytics-operating-model.md 3 KB
- references/ai-nlp-analytics/entrypoint.md 12 KB
- references/ai-predictive-analytics/entrypoint.md 13 KB
Wersje
W bazie nie ma innych skilli o nazwie ai-analytics.
Migawka bazy z 13.11.2026 · wersja paczki 9f7ebad47371 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100qe-test-reporting-analytics
Przygotowuje raporty z testów, dashboardy jakości, analitykę predykcyjną, analizę trendów i raporty dla zarządu z metrykami QE. - 85lens
Działa jako inżynier analityki i BI: buduje dashboardy, projektuje metryki, pisze raporty, tworzy potoki raportowe i audytuje analitykę. - 100granola-observability
Monitoruje przyjęcie Granola i analitykę spotkań oraz buduje własne dashboardy i raporty dla zarządu. - 100lens-audit
Przegląda istniejącą analitykę: znajduje dashboardy i raporty, sprawdza, kto z nich korzysta, czy metryki są zdefiniowane i czy wspierają decyzje, a potem rekomenduje, co zachować, usunąć lub dodać. - 100analytics
Planuje, wdraża i audytuje analitykę, monitoring błędów, kontrole stanu, dashboardy i raportowanie, w tym zdarzenia, śledzenie z uwzględnieniem zgód, widoczność incydentów i obserwowalność. - 100hr-analytics
Pomaga w analityce HR: analizuje dane pracowników, buduje wskaźniki i dashboardy, bada rotację, tworzy raporty i modele predykcyjne oraz strategię zarządzania danymi.