skill-registry

Generates governed lifecycle proposals for skill package promotion, deprecation, and retirement.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill skill-registry-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-registry
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/skill-registry
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill skill-registry-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing the lifecycle of governed skill packages—promotion, deprecation, retirement, and revocation—requires verified provenance, dependency impact analysis, and policy enforcement, which is error-prone when done manually. ## Core Features & Use Cases - Provenance and Integrity Verification: Validates skill package provenance metadata, integrity checks, and ownership consistency before any lifecycle action. - Dependency Impact Analysis: Evaluates downstream break risk using evidence from skill-inventory and skill-dependency-manager before proposing changes. - Policy-Enforced Proposals: Produces governed action proposals with rationale, prerequisites, rollback routes, and explicit approval gates—never performing remote mutation itself. - Use Case: When a team wants to deprecate an outdated skill, this Skill produces a complete deprecation proposal including dependency impact, policy trace, and required approvals, or blocks the request if provenance checks fail. ## Quick Start Ask the agent to prepare a deprecation proposal for a specific skill package with full dependency impact and policy trace.

Frequently Asked Questions about skill-registry

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

FAQPage Schema
How do I deprecate a governed skill package safely?

Request a deprecation proposal through this Skill, which verifies provenance, evaluates dependency impact via skill-dependency-manager, and enforces policy-engine decisions. The output is a governed proposal with rationale and rollback route; actual deprecation requires explicit approval.

What is the difference between skill-registry and skill-create?

skill-registry manages package metadata, discovery, provenance, and lifecycle transitions like promotion and retirement. skill-create is used to author the actual skill content. Use skill-registry for governance decisions, not content authoring.

Can skill-registry directly publish or retire a skill package?

No. Publishing, installation, promotion, retirement, revocation, or any remote mutation requires explicit approval. The Skill only produces proposals recorded as approved, denied, or approval-required.

What happens when provenance verification fails for a skill package?

The Skill fails closed and emits a blocked proposal listing unresolved integrity or approval prerequisites. It never recommends promotion or retirement without traceable governance evidence.

What outputs does the skill-registry workflow produce?

It writes two owned reports: reports/skill-registry.json and reports/skill-registry.md. These contain the action proposal, provenance and integrity checks, policy trace, and dependency impact summary.