log-correction

Log and categorize analytical errors with their fixes.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/Amar1404/AI_ANALYST --skill log-correction-amar1404
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-correction
Source: https://github.com/Amar1404/AI_ANALYST/tree/main/skills/log-correction
Command: npx skills add https://github.com/Amar1404/AI_ANALYST --skill log-correction-amar1404

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of recording and analyzing analyst mistakes and their fixes, ensuring that future analyses benefit from past errors.

Core Features & Use Cases

  • Error Logging: Record errors, corrections, and the reasoning behind them.
  • Error Categorization: Classify errors into categories like SQL, metric, schema, logic, and other.
  • Use Case: When an analyst discovers an error in an analysis, the Skill can be used to log the error details and the corrected approach.

Quick Start

Trigger the Skill by saying "log a correction", "that was wrong because...", or by invoking /log-correction.

Frequently Asked Questions about log-correction

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

FAQPage Schema
How do I log analytical errors and categorize mistakes for continuous learning?

To log analytical errors, you record the mistake, its correction, and the reasoning behind it, then classify it into categories like SQL, metric, schema, or logic to enable continuous learning.

What is the best way to track data analysis mistakes and their fixes?

Tracking data analysis mistakes involves automating the structured logging and categorization of errors alongside their corrected approaches, which ensures future analyses benefit from past analytical mistakes.

Can I categorize SQL and metric errors to improve data quality?

Yes, you can categorize SQL, metric, schema, and logic errors during the logging process, directly addressing data quality by structuring analytical mistakes for systematic review and improvement.

Does automated error logging require any specific framework dependencies?

No, automated error logging for analytical corrections requires no external framework dependencies, allowing you to independently structure your error tracking and categorization workflow.

When should I not use automated error categorization for analytical corrections?

Automated error categorization is not suited for unstructured or non-analytical mistakes, as it requires structured logging of specific SQL, metric, schema, or logic errors to function properly.