Help us improve
Share bugs, ideas, or general feedback.
From data
QA an analysis before sharing -- methodology, accuracy, and bias checks
npx claudepluginhub tmorrowdev/tmorrow_ai --plugin dataHow this command is triggered — by the user, by Claude, or both
Slash command
/data:validate <analysis to review>The summary Claude sees in its command listing — used to decide when to auto-load this command
# /validate - Validate Analysis Before Sharing > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md). Review an analysis for accuracy, methodology, and potential biases before sharing with stakeholders. Generates a confidence assessment and improvement suggestions. ## Usage The analysis can be: - A document or report in the conversation - A file (markdown, notebook, spreadsheet) - SQL queries and their results - Charts and their underlying data - A description of methodology and findings ## Workflow ### 1. Review Metho...
/conjoint-diagnosticsRuns a conjoint diagnostics review on the provided task or study, evaluating design integrity, estimation choices, measurement error, external validity, and interpretation against a checklist.
/analyticsAnalyzes data to extract insights, generate visualizations, or perform analytics based on a question and optional approach like SQL or visualization.
/validateValidates plans, roadmaps, or proposals as ruthless CTO mentor, producing 8-section report with verdict, strengths, flaws, blindspots, and next steps.
/analyze-datasetGenerates a data quality report from a dataset description, flagging outliers, biases, missing values, and class imbalance, and suggests preprocessing transforms.
/stress-testStress tests a research thesis or conclusion by surfacing proponents' and critics' factors, core assumptions, and potential invalidators.
/analyzeRuns 7-phase data analysis workflow for revenue and RevOps: setup Marimo notebook, ingest/explore data, model, interpret with bias checks/decision logs, output dashboards/Excel/PPTX.
Share bugs, ideas, or general feedback.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Review an analysis for accuracy, methodology, and potential biases before sharing with stakeholders. Generates a confidence assessment and improvement suggestions.
/validate <analysis to review>
The analysis can be:
Examine:
Systematically review for:
Data completeness:
Statistical issues:
Aggregation errors:
Time-related issues:
Selection and scope:
Where possible, spot-check:
If the analysis includes charts:
Review whether:
Provide specific, actionable suggestions:
Rate the analysis on a 3-level scale:
Ready to share -- Analysis is methodologically sound, calculations verified, caveats noted. Minor suggestions for improvement but nothing blocking.
Share with noted caveats -- Analysis is largely correct but has specific limitations or assumptions that must be communicated to stakeholders. List the required caveats.
Needs revision -- Found specific errors, methodological issues, or missing analyses that should be addressed before sharing. List the required changes with priority order.
## Validation Report
### Overall Assessment: [Ready to share | Share with caveats | Needs revision]
### Methodology Review
[Findings about approach, data selection, definitions]
### Issues Found
1. [Severity: High/Medium/Low] [Issue description and impact]
2. ...
### Calculation Spot-Checks
- [Metric]: [Verified / Discrepancy found]
- ...
### Visualization Review
[Any issues with charts or visual presentation]
### Suggested Improvements
1. [Improvement and why it matters]
2. ...
### Required Caveats for Stakeholders
- [Caveat that must be communicated]
- ...
/validate Review this quarterly revenue analysis before I send it to the exec team: [analysis]
/validate Check my churn analysis -- I'm comparing Q4 churn rates to Q3 but Q4 has a shorter measurement window
/validate Here's a SQL query and its results for our conversion funnel. Does the logic look right? [query + results]