Stop rebuilding data that did not move.
The cheap gate that decides, before an expensive workflow runs, whether to skip, partially refresh, recycle, or fully regenerate.
Inside: The four verdicts, the section taxonomy, and a dollarized savings estimate.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it reads last-modified timestamps and field-level deltas automatically, so the verdict is evidence-backed, not eyeballed.
catches new events since the last run that should force a refresh.
catches a usage-trend shift that should re-open a section.
This was built to gate a suite of GTM artifacts. Set these to your stack:
| Set this | What it is | Default / Example |
|---|---|---|
| ARTIFACT TYPES | what you regenerate | account briefweekly reportdeal reviewpipeline analysis |
| DATA SOURCES | where "did it change" comes from | CRM last-modifiedmeeting countusage trend |
| STATIC SECTIONS | reuse, stable 30+ days | company researchbuying committeetech stack |
| DYNAMIC SECTIONS | rebuild every run | activitycurrent dealstime-bound cards |
| CONDITIONAL SECTIONS | rebuild only when a trigger fires | champion changefit-score deltausage-tier shift |
| SKIP_DAYS | age under which unchanged means skip | 7 |
| FULL_DAYS | age over which force a full rebuild | 30 |
Everything the skill does, in full.
Before you spend tokens rebuilding a brief, report, or analysis, this checks whether anything underneath it actually changed. It returns one of four verdicts (skip, partial, recycle, or full), a section-by-section plan of what to reuse and what to rebuild, and an estimate of what you save by not regenerating the whole thing. It is meant to be cheap, so it can gate expensive work and pay for itself many times over.
- 1The four verdicts
Every artifact gets exactly one:
- SKIP: age at or under SKIP_DAYS and no underlying data changed. Return the existing artifact, rebuild nothing, cost zero.
- PARTIAL: recent, but some sections have stale underlying data. Rebuild only those sections and splice them into the existing artifact. Typical savings 60 to 80 percent.
- RECYCLE-CORE: older, but the identity and static sections are unchanged while the dynamic ones are all stale. Reuse the static cards, rebuild the activity-driven ones. Typical savings 30 to 50 percent.
- FULL: older than FULL_DAYS, or an identity-level change (acquisition, segment shift, recategorization), or no existing artifact. Run the whole workflow. Cost 100 percent baseline.
- 2Static vs dynamic sections
Every artifact type splits three ways. STATIC sections are identity-grade and stable for 30+ days (company research, buying committee, tech stack, history). DYNAMIC sections rebuild every run (days-dark, current deal health, time-bound wins, coverage math). CONDITIONAL sections rebuild only when a named trigger fires (a champion job-change, a fit-score delta past threshold, a usage-tier shift). Knowing which section is which is the whole skill; map yours once and the plan writes itself.
- 3Freshness signals
The verdict reads: artifact age; last-modified on the source record; field-level diffs mapped to the sections each field drives; new activity since the last run; a usage-trend tier shift; a fit-score delta past a threshold. Each signal points at specific sections, not the whole artifact, which is what makes a partial plan possible.
- 4The savings estimate
Every partial or recycle plan states the estimated token reduction and cost saved versus a full rebuild, so the call is auditable and anyone can see when the gate is being too aggressive.
- Evidence-first verdicts. Never "the brief is stale." Always "stale because the source changed on {date} and the artifact is from {date}."
- No false-fresh calls. If the evidence is ambiguous (you cannot read the artifact or the source), default to FULL. Better to spend than ship stale.
- Conservative on identity changes. Any identity-level signal (acquisition, segment shift, recategorization) forces FULL regardless of age.
- First run of any new artifact is always FULL. There is nothing to reuse yet.
REFRESH PLAN - account brief for acme.com Verdict: PARTIAL (artifact 4 days old) Reuse: company research, buying committee, tech stack, history Rebuild: days-dark, deal health, top wins Evidence: source last-modified 2 days ago; 2 new meetings; usage trend flat Savings: ~73% fewer tokens vs a full rebuild
SKIP_DAYS (7), FULL_DAYS (30), and the fit-score delta threshold are defaults from one team's cadence, not laws. A weekly artifact and a quarterly one want different windows. If your work changes slowly, widen the windows; if it moves daily, tighten them. The four-verdict logic does not change. The thresholds are yours.
Where an operator takes this next.
The manual check proves the gate is worth running. Here is the version that runs itself.
The gate pays for itself the first week it stops a rebuild nobody needed.
Wire it in front of your weekly revenue report or account-brief generator so nothing regenerates until this verdict says so.
Connect Salesforce so an acquisition or segment-shift field change forces FULL the moment it's logged, not at the next scheduled run.
Log every verdict and its token estimate to a sheet so you can show finance what the gate is actually worth.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.