fix(plugins): sync all 171 plugin SKILL.md files with fixed skills/ versions

Propagates Anti-Patterns sections, description rewrites, Required Inputs additions, and Quality Checks format fixes from skills/ to matching plugin SKILL.md copies. https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
2026-06-08 13:06:21 +00:00
parent fb85a1cb55
commit affae033fe
171 changed files with 1428 additions and 56 deletions
@@ -117,6 +117,14 @@ Ask the user for these if not provided:
 - [ ] What the data cannot tell us is explicitly named
 - [ ] Recommended action includes an owner and timeline

+## Anti-Patterns
+
+- [ ] Do not present correlations as causation — always state the distinction explicitly
+- [ ] Do not report a metric movement without stating the time window and comparison baseline
+- [ ] Do not skip the "so what" — raw observations without recommended actions are incomplete analysis
+- [ ] Do not overstate confidence — label hypotheses clearly and note what data would be needed to confirm them
+- [ ] Do not ignore segment breakdowns — aggregate metrics can mask opposing trends in sub-segments
+
 ## Guidelines

 - Always state what the data *cannot* tell you — never oversell confidence
@@ -57,3 +57,11 @@ Analyse across four layers:
 - [ ] Every flagged metric has a root cause hypothesis, not just "it dropped"
 - [ ] Observations are written for a non-technical stakeholder (no raw query language or data jargon)
 - [ ] Overall health rating is justified with specific evidence
+
+## Anti-Patterns
+
+- [ ] Do not report a single aggregate metric without segment breakdowns — averages hide opposing trends
+- [ ] Do not flag a metric as healthy just because it is above the target — check if the target itself is meaningful
+- [ ] Do not list metric movements without root cause hypotheses — observations without explanations are not analysis
+- [ ] Do not mix product health metrics with business KPIs without explaining the relationship between them
+- [ ] Do not omit recommended actions — a health report that only describes problems without prioritised next steps is incomplete
@@ -126,6 +126,14 @@ Ask the user for these if not provided:
 - [ ] Churned user interviews are recommended (not just data analysis)
 - [ ] Monitoring plan includes an alert threshold

+## Anti-Patterns
+
+- [ ] Do not recommend "improve onboarding" without specifying what specific step to change and why
+- [ ] Do not analyse retention without segmenting by cohort — aggregate retention curves hide cohort-specific patterns
+- [ ] Do not treat DAU/MAU below 5% as a retention problem — at that level, it is a product-market fit problem
+- [ ] Do not skip qualitative research — churned user interviews reveal reasons that quantitative data cannot
+- [ ] Do not set a monitoring alert without specifying the threshold that triggers it
+
 ## Guidelines

 - Never recommend "improve onboarding" without specifying *what* to change and *why*