SuperAPI AI Directory

gm-skill-manager

General & other

View repository

Updated 10-16 12:47

About this skill

GM Skill Manager

Manage Skills as an executable coordinator. The Native Installers and native records of Codex, Claude Code, and npx skills are always authoritative; the Manager only generates the current Unified Inventory, formulates the Execution Plan, invokes native mechanisms, and verifies results.

Non-negotiable rules

  1. Inventory first, then Action; after Action, inventory again.
  2. Capability Identity is determined solely by normalized Remote Source + canonical SKILL.md path; Revision, name, Runtime, and Package Format do not participate in identity.
  3. Runtime adapters only produce Observed Evidence; only Identity Resolution can adjudicate identical Capabilities.
  4. Do not directly modify plugin registry, cache,skills-lock, private databases, or Runtime links.
  5. Do not copy local directories to simulate installation; normal installation only accepts GitHub/Git Remote Source.
  6. doctor is read-only; repair is a separate mutation Action.
  7. Output Facts, Findings, Recommendations, and Execution Plan separately.
  8. Stage 1 manages Codex Plugin, Claude Code Plugin,npx skills; ZCode only reports unmanaged.

Generate Unified Inventory

Run from this skill directory:

python3 scripts/inventory.py --json

Optional views:

python3 scripts/inventory.py --view capability
python3 scripts/inventory.py --view package
python3 scripts/inventory.py --view runtime
python3 scripts/inventory.py --redact --json
python3 scripts/inventory.py --project /explicit/project/root --json

Capability View is used by default. For machine-readable output, schema_version is the contract version; unknown values for required fields are explicitly written as unknown. Project scope is read only when the Operator explicitly provides the root directory via --project ; it must not be inferred from the current working directory.

Inventory must be able to express:

  • Installation Package、Package Format、Installation、Capability、Exposure;
  • Resolved / Unresolved Identity;
  • Installation State and Exposure State;
  • Revision Relation;
  • Registry / Discovery Verification;
  • Duplicate Exposure、Revision drift、broken Installation;
  • ZCode unmanaged。

Action routing

Before executing any mutation, read references/action-contract.md. When runtime paths and commands are needed, read references/runtime-map.md。

Read-only Actions

  • list: generate three views.
  • doctor: report installer, identity, state, scope, manifest, and exposure issues.
  • Remote catalog / Package Impact: read known Remote Sources; do not search unknown repositories to guess sources.

Mutation Action

  • install
  • uninstall
  • enable
  • disable
  • repair

Mutation must:

  1. Specify the Capability or Installation Package.
  2. Specify the target Runtime; do not default to Codex + Claude.
  3. When multiple scopes are available, have the Operator make an explicit choice.
  4. Preview Package Impact and affected Capabilities.
  5. Choose the most native Package Format for the target Runtime; only when none exists, use npx skills。
  6. Use the Native Installer or the Runtime's native Plugin UI.
  7. Immediately perform Registry Verification and Discovery Verification after each step.
  8. Stop on failure, re-inventory, and report Partial Success; do not automatically roll back.

When an explicit request already includes the Action, target, Runtime, and scope, it may be treated as Action Authorization. If preflight finds additional Capabilities, executable extensions, data deletion, project/local scope, or batch impact, confirmation must be obtained again.

Native Installer selection

Codex 有 codex-plugin format
  → codex plugin / Codex Plugin UI

Claude Code 有 claude-code-plugin format
  → claude plugin

目标 Runtime 无原生 Plugin format,但 npx skills 支持
  → npx skills

均不支持
  → blocked: unsupported-format

When a Capability is exposed by both a Plugin and npx skills in the same Runtime, do not infer load priority: mark ambiguous, recommend keeping the native Plugin, but do not automatically delete.

Complete verification

Action completion must simultaneously satisfy:

  • Native Installer returns success;
  • native registry / lock reflects the target state;
  • Runtime can reliably discover the Capability;
  • no new Duplicate Exposure or broken Installation is added;
  • the actual impact does not exceed the authorized Execution Plan.

When Discovery Verification cannot be completed, the Exposure State remains unknown, and it must not be claimed as active. The presence of SKILL.md in the installation directory only proves file/manifest evidence and does not constitute Discovery Verification.

Output Contract

## Facts
- 当前 Native Installer evidence 和 Unified Inventory 状态

## Findings
- identity、revision、installation、exposure、scope 问题

## Recommendations
- 非执行建议

## Execution Plan
- 仅在 Operator 选择 Action 后生成

## Verification
- Registry / Discovery evidence

## Risks
- unknown、unmanaged、partial success、未验证内容