Stop rebuilding data that did not move.

“Do we really need to rebuild this brief every week, or did nothing underneath it actually change?”

The cheap gate that decides, before an expensive workflow runs, whether to skip, partially refresh, recycle, or fully regenerate.

CONVERT MORE PIPELINEINTERMEDIATECRMPRODUCT-ANALYTICS TOOL✓ APPROVED 4/4
EXAMPLE PROMPTS
>Has anything changed since this account brief was last run, or can we reuse it?
>Should we regenerate this pipeline report? Here is last week's version and the new export
>Which sections of this report need a rebuild and which can I recycle as is?
ABOUT THIS SKILL

What this skill does

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.

Inputs

  • Works today with: the existing artifact (paste it or point at the file) and a note of when it was last generated. The skill runs the freshness logic on what you give it.
  • More powerful connected to your data sources: it reads last-modified timestamps and field-level deltas automatically, so the verdict is evidence-backed, not eyeballed.
  • Sharper with a meeting or activity tool: catches new events since the last run that should force a refresh.
  • Sharper with a product-analytics tool: catches a usage-trend shift that should re-open a section.

How it works

  1. 1
    The 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.
  2. 2
    Static 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.

  3. 3
    Freshness 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.

  4. 4
    The 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.

Output format

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

Tips

  • 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.
RELATED SKILLS
CONNECTSINTERMEDIATE · Revenue & Ops Command

Make revenue reporting a weekly habit that drives action.

Pairs a where-we-stand-and-why write-up with a list of hot leads and deals to work now, so the report ends in moves, not a screenshot.

CONNECTS TO CRM, PRODUCT-ANALYTICS TOOLAPPROVED · INSTALL →
CONNECTSADVANCED · Revenue & Ops Command

Get one forecast-aware brief that names today's priorities.

Composes deal risk, pipeline, coaching, and conversation reads into a single morning brief, in rep or leader mode.

CONNECTS TO CRM, PRODUCT-ANALYTICS TOOLAPPROVED · INSTALL →
ALL CONVERT MORE PIPELINE SKILLS →