From fullvision
Check identity reconciliation, checkout coverage and event coverage before trusting any FullVision number. Runs standalone and as a precondition inside every other skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fullvision:fv-data-healthThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Bad coverage means every downstream number is a lie. This skill's job is to say so, loudly,
Bad coverage means every downstream number is a lie. This skill's job is to say so, loudly, before a recommendation gets made on top of it — not to recommend anything itself.
Read shared/reading-fullvision-data.md before calling anything.
fullvision:query_view on view:health-identity-recon — what share of paying customers
are linked to a tracked visitor. This caps attribution coverage: unlinked payers have no
source, so every channel's revenue is understated.fullvision:query_view on view:health-checkout-coverage — what share of checkouts carry
a visitor cookie. Low coverage biases paid attribution specifically, because paid traffic
converts faster and is more cookie-dependent.fullvision:query_view on view:health-event-coverage — are product events arriving. A
gap here means funnel and engagement views are incomplete for that window.fullvision:query_view on view:ads-measurement-start — the first Stripe webhook charge.
Spend before it is unmeasurable. Report the date; every ads skill needs it.| Check | ✅ ok | ⚠️ degraded | 🚩 broken |
|---|---|---|---|
| Identity recon (payers linked) | ≥ 85% | 60–85% | < 60% |
| Checkout coverage (cookie present) | ≥ 80% | 55–80% | < 55% |
| Event coverage (days with events / days in window) | ≥ 95% | 80–95% | < 80% |
These are fixed. Do not adjust them at runtime to make a run pass.
Every other skill calls this first and inlines the one-line result in its report header. A skill that reaches 🚩 aborts its own analysis and returns this skill's output instead.
shared/report-format.md. Verdict is the worst of the three grades.
npx claudepluginhub fullvision-team/fullvision-plugin --plugin fullvisionGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.