How do I install the Updating Daily skill?

Run npx skillmds@latest add socketdev/updating-daily in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Updating Daily safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Updating Daily?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Updating Daily free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Updating Daily?

socketdev (@socketdev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Updating Daily by socketdev — Agent Skill

Name: Updating Daily
Author: socketdev

File contents

updating-daily

The daily, cheap maintenance pass: promote dependency soak-exclusions that have cleared their 7-day minimumReleaseAge window. A soak-exclude is a temporary bypass; once the package is old enough to install normally, the bypass is dead weight and should come out. Invoked daily by daily-update.yml (which routes through the same socket-registry reusable as the weekly run, opening a PR), or directly via /update-daily.

When to use

The daily scheduled run (the workflow passes updating-skill: updating-daily).
Any time you want to clear soaked exclusions from pnpm-workspace.yaml.

What it does NOT do

npm version bumps. That's the weekly /updating umbrella's job (taze, lockstep, submodules). Daily is soak-promotion only — small, predictable, safe to run unattended.
Add exclusions. Adding a soak-bypass is the Allow minimumReleaseAge bypass flow, not this skill.
Touch repo-local non-exclude settings. Only minimumReleaseAgeExclude entries are promoted; the rest of pnpm-workspace.yaml is untouched.

Phases

#	Phase	Outcome
1	Promote	`node scripts/fleet/check/soak-excludes-have-dates.mts --fix` removes every entry whose `removable:` date has passed — the bullet plus its `# published/removable` annotation.
2	Reconcile	If step 1 changed `pnpm-workspace.yaml`, run `pnpm install` so the lockfile matches the slimmed catalog/exclude set.
3	Report	If nothing was promoted, exit cleanly with no diff — the workflow opens no PR. Otherwise the changed files (`pnpm-workspace.yaml` + `pnpm-lock.yaml`) become the PR.

Run

node scripts/fleet/check/soak-excludes-have-dates.mts --fix
# then, only if pnpm-workspace.yaml changed:
pnpm install

--fix prints each promoted entry on stdout and is a no-op (clean exit, no write) when nothing has soaked. A no-change run leaves the tree clean, so the wrapping workflow opens no PR.

Commit shape

The change is mechanical and needs no tracking: chore(deps): promote soaked exclusions. List the promoted pkg@ver entries in the body. Cascade commits and this daily promotion are exempt from the prose skill.

---name: updating-dailydescription: Promote soak-cleared dependency exclusions, drop expired dates, and reconcile the lockfile.---# updating-dailyThe daily, cheap maintenance pass: promote dependency soak-exclusions that have cleared their 7-day `minimumReleaseAge` window. A soak-exclude is a temporary bypass; once the package is old enough to install normally, the bypass is dead weight and should come out. Invoked daily by `daily-update.yml` (which routes through the same socket-registry reusable as the weekly run, opening a PR), or directly via `/update-daily`.## When to use- The daily scheduled run (the workflow passes `updating-skill: updating-daily`).- Any time you want to clear soaked exclusions from `pnpm-workspace.yaml`.## What it does NOT do- **npm version bumps.** That's the weekly `/updating` umbrella's job (taze, lockstep, submodules). Daily is soak-promotion only — small, predictable, safe to run unattended.- **Add exclusions.** Adding a soak-bypass is the `Allow minimumReleaseAge bypass` flow, not this skill.- **Touch repo-local non-exclude settings.** Only `minimumReleaseAgeExclude` entries are promoted; the rest of `pnpm-workspace.yaml` is untouched.## Phases| # | Phase | Outcome || --- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- || 1 | Promote | `node scripts/fleet/check/soak-excludes-have-dates.mts --fix` removes every entry whose `removable:` date has passed — the bullet plus its `# published/removable` annotation. || 2 | Reconcile | If step 1 changed `pnpm-workspace.yaml`, run `pnpm install` so the lockfile matches the slimmed catalog/exclude set. || 3 | Report | If nothing was promoted, exit cleanly with no diff — the workflow opens no PR. Otherwise the changed files (`pnpm-workspace.yaml` + `pnpm-lock.yaml`) become the PR. |## Run```bashnode scripts/fleet/check/soak-excludes-have-dates.mts --fix# then, only if pnpm-workspace.yaml changed:pnpm install````--fix` prints each promoted entry on stdout and is a no-op (clean exit, nowrite) when nothing has soaked. A no-change run leaves the tree clean, so thewrapping workflow opens no PR.## Commit shapeThe change is mechanical and needs no tracking: `chore(deps): promote soakedexclusions`. List the promoted `pkg@ver` entries in the body. Cascade commitsand this daily promotion are exempt from the `prose` skill.

Frequently asked questions

Updating Daily