skills.rest
Yassimba
YassimbaCOMMUNITY
Explore all skills by this author →
GitHub

check-for-updates

Detects stale loom TUI tools and remote skills and reports merge classes against local edits.

9|Updated Jul 17, 2026
Search Tags:#mise#diff#github api#update check#staleness detection#merge classification#skill lock
One-click install
npx skills add https://github.com/Yassimba/loom --skill check-for-updates-yassimba
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-for-updates
Source: https://github.com/Yassimba/loom/tree/main/.agents/skills/check-for-updates
Command: npx skills add https://github.com/Yassimba/loom --skill check-for-updates-yassimba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Installed loom TUI tools and remote skills drift out of date silently, and updating blindly risks overwriting local edits. This Skill produces a read-only briefing that shows exactly what is stale and how safely each update can be applied. ## Core Features & Use Cases - Inventory and staleness detection: Builds a list of selected TUI tools from mise config and remote skills from skill lock files, then compares pins and folder hashes against upstream releases, git trees, or well-known URLs. - Merge classification: Diffs live folders against upstream and lock hashes to label each item clean, drift, or overlap, naming colliding files and hunks. - Use Case: Before running loom update, ask for a briefing to see that one skill has local modifications overlapping upstream changes, so you can resolve the conflict manually instead of losing your edits. ## Quick Start Use the check-for-updates skill to brief me on stale loom tools and remote skills before I apply any updates.

Frequently Asked Questions about check-for-updates

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

FAQPage Schema
How do I check if my loom skills and tools are out of date?▼

Run the check-for-updates skill to build an inventory of selected TUI tools and remote skills, then compare each pin or lock hash against the latest upstream release or tree. It labels every item current or stale and ends with a pick list of stale names.

How does the skill detect stale remote skills?▼

It reads skillFolderHash from the lock files and compares it against the upstream folder SHA from the GitHub trees API, git ls-tree for git and gitlab sources, or a digest of the well-known URL payload. A mismatch marks the skill stale.

Will checking for updates overwrite my local skill edits?▼

No. The run is read-only and only produces a briefing. It classifies each stale item as clean, drift, or overlap by diffing live versus upstream, so you see exactly which local edits would be affected before applying anything.

What do the clean, drift, and overlap merge classes mean?▼

Clean means only upstream moved and applying is a straight take. Drift means your live folder differs from the lock while upstream did not move, so applying overwrites local edits. Overlap means both sides changed the same region, and the colliding files and hunks are named.

What sources does the update check support?▼

It supports GitHub pins via the releases API, npm pins via npm view, and remote skills with sourceType github, git, gitlab, or well-known. TUI selections come from the loom mise config and remote skills from skill lock files.

Related Skills

Explore More Software Engineering Skills→
waynebabywaynebaby
2

loom-skill-enhancement

Enhance skills for deterministic execution within Techne Loom.

Community
Advanced
quanngynxquanngynx

copilotkit-self-update

Reinstall CopilotKit skill definitions to correct outdated API references.

Community
Basic
oskarroughoskarrough

arbe-bro

Rewrites the assistant's previous reply in plain language without jargon.

Community
Basic
statesetstateset

commerce-inventory

Manage inventory counts, adjustments, and reservations across locations.

Official
Intermediate