ecosystem-update-check

Identify new Sovereign Ecosystem GitHub updates and prompt user approval decisions.

2|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/infinitegameplayer/sovereign-ecosystem --skill ecosystem-update-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecosystem-update-check
Source: https://github.com/infinitegameplayer/sovereign-ecosystem/tree/main/Council%20Chamber/Skills/Ecosystem%20Update%20Check
Command: npx skills add https://github.com/infinitegameplayer/sovereign-ecosystem --skill ecosystem-update-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you identify and apply Sovereign Ecosystem updates with explicit human approval, preventing unintended changes.

Core Features & Use Cases

  • Surface new updates from the Sovereign Ecosystem GitHub repo and compare them against your local sync state.
  • Present updates in an orderly priority (Core, Refinement, Module, Instruction) and require user decisions before applying.
  • Maintain a local sync-state.json to track last check date and applied/ skipped/ deferred updates.

Quick Start

Run the check to fetch the latest update index and begin reviewing which updates to apply.

Frequently Asked Questions about ecosystem-update-check

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

FAQPage Schema
How do I check for new Sovereign Ecosystem updates from GitHub?

To check for Sovereign Ecosystem updates, run the skill to fetch the latest update index from the GitHub repo and compare it against your local sync-state.json to surface unapplied items.

How does update governance work for Sovereign Ecosystem modules?

Sovereign Ecosystem governance requires explicit human approval by prompting you to approve, skip, or defer each update before it is applied, preventing unintended changes.

What is the correct order to apply Sovereign Ecosystem updates?

Sovereign Ecosystem updates are grouped and presented in the priority order of Core, Refinement, Module, and Instruction, with non-optional items flagged with a caution.

How are skipped or deferred Sovereign updates tracked?

Skipped, deferred, and applied Sovereign updates are tracked using a local sync-state.json file that maintains your last check date and previous update decisions.

Can I automate applying GitHub updates without manual consent?

No, this update monitoring process requires explicit user consent for every update, prompting you to approve, skip, or defer decisions to prevent unintended automated changes.