Menu

Individual skill

DataRefresh

0upvotes

Keeps your data-backed public sites and their source datasets current: freshness check, source repull, rebuild, gated deploy, live verify. USE WHEN update our data sites, refresh the data sites, are our datasets stale, data freshness, repull the data, refresh the dataset, update the data and the site, stale data check, which sites need updating, refresh any registered data property by name. NOT FOR system upgrades (Upgrade), uptime/security monitoring (Bunker/Workflows), US economic indicators (USStats), non-data deploys (use your deploy tooling).

LifeOS/install/skills/DataRefresh/SKILL.md

Read pinned source

Source commit b7efec97d8c3885feee285bee468c35602fb0606

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
19,769
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# DataRefresh

Registry-driven freshness engine for data-backed public sites. Each registered target carries its own fetch scripts, source-of-record dataset updater, build step, sanctioned deploy command, and live verify probe. One command reports staleness across the fleet; one command brings a target current.

## Ideal State

- Every registered target's freshness is known against its own cadence, and a stale one is brought current from its real upstream sources, not from a cached or frozen copy.
- A target that passes its cadence reaches the principal without being asked, through a scheduled read-only status check that reports to Vigil; that check never refreshes or deploys.
- Nothing reaches production unless the principal's ask covered publishing, and a deployed refresh is proven on the live site.
- Narrative figures that the fresh data contradicts are found and fixed by hand; deterministic code never rewrites prose.
- Every refresh run leaves one line per target in the run log (status writes none), and every touched repo ends committed per its own conventions.

## Intent Routing