newmanxbt/sealevel-guard · Archived

governance-upgrade-risk

Detects whether governance or upgrade control is concentrated, weakly separated, or capable of undermining user or integrator trust. Internal specialist module for governance risk review.

First seen Mar 27, 2026

Installation

$ npx skills add newmanxbt/sealevel-guard --skill governance-upgrade-risk

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from newmanxbt/sealevel-guard.

npx skills add newmanxbt/sealevel-guard

Browse all from newmanxbt/sealevel-guard

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,200 B
  • docs SUMMARY.md 218 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Governance Upgrade Risk

Governance and upgradeability trust review skill.

Purpose

Detect whether governance or upgrade control is concentrated, weakly separated, or capable of undermining user or integrator trust.

Focus

This skill is responsible for:

  • single-key upgrade authority concentration,
  • emergency admin abuse surface,
  • governance bypass paths,
  • unsafe config authority patterns,
  • and migration or initialization flows that weaken trust.

What To Look For

  • upgrade power held by an unsafe authority structure
  • governance assumptions not matched by enforced control
  • emergency powers that can bypass trust assumptions silently
  • initialization or migration paths that can rewrite critical state

Output Shape

Each finding should state:

  • what trust assumption governance appears to promise,
  • how actual control differs,
  • and whether another agent should refuse to integrate or allocate through it.