auto-updater

Compare pinned SHAs to registry versions and present diffs for approval.

Updated May 28, 2026
One-click install
npx skills add https://github.com/gtgspot/clegal --skill auto-updater-gtgspot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-updater
Source: https://github.com/gtgspot/clegal/tree/main/legal-builder-hub/skills/auto-updater
Command: npx skills add https://github.com/gtgspot/clegal --skill auto-updater-gtgspot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and coordinate updates for installed community skills by comparing local pins to registry versions, surfacing actionable diffs, and gating changes behind explicit approval.

Core Features & Use Cases

  • Detect updates for installed skills by comparing pinned SHAs to registry SHAs.
  • Present a clear diff of changes across SKILL.md, hooks/hooks.json, .mcp.json, and related manifests.
  • Enforce explicit user approval before applying updates to maintain control and safety.

Quick Start

Review the proposed update and approve to apply changes.

Frequently Asked Questions about auto-updater

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

FAQPage Schema
How do I approve skill updates before applying changes to installed community skills?

To approve skill updates, the system compares pinned local commit SHAs against registry SHAs, presents a diff of changes, and requires explicit user confirmation before applying any updates.

What does a commit diff show when updating community skills?

A commit diff for skill updates shows changes across SKILL.md, hooks/hooks.json, .mcp.json, and related manifests, allowing you to review modifications before giving explicit approval to apply them.

How does version control work for managing installed community skills?

Version control for installed skills works by fetching the latest commit SHAs from the registry, comparing them against your local pinned SHAs, and surfacing actionable diffs for review.

Can I review changes to hooks.json and .mcp.json before updating a skill?

Yes, you can review changes to hooks.json and .mcp.json before updating. The update process generates a clear diff of these related manifests and enforces explicit user approval to proceed.

Do I need to manually check the registry for newer community skill commits?

No, you do not need to manually check the registry for newer commits. The skill management process automatically fetches latest commit SHAs and compares them against pinned versions to detect available updates.

Why does updating installed skills require explicit approval?

Updating installed skills requires explicit approval to maintain control and safety, ensuring you review the generated diff of manifest changes and confirm before any modifications are applied to your deployment.