self-improving-analytics

Log analytics learnings, data issues, and feature requests to markdown files.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/jose-compu/self-improving-skills --skill self-improving-analytics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-improving-analytics
Source: https://github.com/jose-compu/self-improving-skills/tree/main/self-improving-analytics
Command: npx skills add https://github.com/jose-compu/self-improving-skills --skill self-improving-analytics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Capture and organize analytics learnings, data issues, and governance requests as markdown entries to enable continuous improvement and cross-team promotion.

Core Features & Use Cases

  • Log data quality problems, metric drift, pipeline failures, misleading visualizations, and definition mismatches.
  • Promote broadly applicable learnings to data dictionaries, data quality SLAs, pipeline runbooks, and dashboard standards.
  • Integrate with OpenClaw hooks and cross-skill workflows to seed learning and automation.

Quick Start

Log a new analytics learning by adding a markdown entry under the analytics learnings workspace and tagging it with the appropriate category.

Frequently Asked Questions about self-improving-analytics

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

FAQPage Schema
How do I log analytics learnings and data quality issues for continuous improvement?

Capture data quality issues, metric drift, and pipeline failures by logging them as structured markdown entries. This process tracks analytics learnings across ingestion, transformation, modeling, and reporting stages to enable continuous improvement and actionable resolution.

What is the best way to track metric drift and data freshness breaches in analytics pipelines?

Track metric drift and data freshness breaches by documenting them as markdown entries within a dedicated analytics learnings workspace. This method categorizes pipeline failures and definition mismatches to maintain historical visibility and prevent recurring data quality issues.

Can I promote documented analytics learnings into data dictionaries and pipeline runbooks?

Yes, broadly applicable analytics learnings can be promoted into data dictionaries, metric definitions, pipeline runbooks, and dashboard standards. Governance hooks facilitate this promotion to ensure reusable patterns are standardized across teams.

How do misleading visualizations and definition mismatches get documented for data governance?

Document misleading visualizations and definition mismatches as categorized markdown entries within an analytics learnings workspace. This structured logging captures reporting anomalies and feeds them into a learning-extraction workflow for governance review and cross-skill linking.

Do I need any specific dependencies to capture data issues using markdown files?

No dependencies are required to capture data issues using markdown files. The Skill operates independently, relying on a markdown-based workspace and internal governance hooks to manage analytics learnings, feature requests, and data quality entries.