skills-update

Update vendored skills and pack catalogs to their latest upstream versions.

1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/zacgoodwin/AIBootstrap --skill skills-update-zacgoodwin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skills-update
Source: https://github.com/zacgoodwin/AIBootstrap/tree/main/.claude/skills/skills-update
Command: npx skills add https://github.com/zacgoodwin/AIBootstrap --skill skills-update-zacgoodwin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vendored skills under .claude/skills/ and pack catalogs under docs/frameworks/ track upstream repositories that change over time, and without a recorded pin and a comparison process there is no way to know what has drifted or to refresh safely. ## Core Features & Use Cases - Upstream drift detection: Run node tools/skills-update.mjs check to classify every entry in tools/sources.json as current, moved, unpinned, manual, unreachable, or local. - Judged updates: Use diff to inspect upstream changes and pull to apply them, with human judgment on whether to take, defer, or reject each change; pull refuses to overwrite locally adapted copies without --force. - Catalog rewrites: Regenerate pack catalog files per the documented workflow, move rows between pack files and NON-PACK-SKILLS.md, then stamp the manifest and header together. - Use Case: A maintainer suspects a vendored skill is stale, runs check, sees moved, reviews the diff, pulls the update, runs the gate, and records the change in the changelog. ## Quick Start Ask the assistant to check whether the vendored skills and pack catalogs are current against their upstream sources and update any that have moved.

Frequently Asked Questions about skills-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if vendored skills are out of date?

Run `node tools/skills-update.mjs check` to compare each entry's pinned commit in tools/sources.json against its upstream repository head. Entries come back as current, moved, unpinned, manual, unreachable, or local.

How do I update a vendored skill to the latest upstream version?

Run `node tools/skills-update.mjs diff <id>` to review the upstream changes, then `node tools/skills-update.mjs pull <id>` to copy the files and restamp the manifest. Read the result afterward to confirm it still fits the repo.

What does the 'moved' status mean when checking upstream?

Moved means the upstream repository head changed, but the check only sees the repo head, not the specific subpath. Run the diff command to determine whether the vendored files actually changed before treating anything as out of date.

What happens if a vendored skill was edited locally?

The pull command refuses to overwrite a working copy that no longer matches its recorded pin. Passing --force discards the local edits, which is a decision left to the user rather than made automatically.

Why does adding a new vendored skill fail the gate?

Vendoring a skill without a corresponding tools/sources.json entry fails the gate by design, because an unrecorded source would silently appear up to date forever. Add the entry with id, kind, upstream, and pinned commit in the same commit.