skill-governance

Enforce governance for adding, updating, and deleting skill units.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/OliverOuyang/shuhe-work-skills --skill skill-governance-oliverouyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-governance
Source: https://github.com/OliverOuyang/shuhe-work-skills/tree/main/skills/skill-governance
Command: npx skills add https://github.com/OliverOuyang/shuhe-work-skills --skill skill-governance-oliverouyang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces mandatory governance for creating, updating, and deleting skills in the repository to prevent undocumented, insecure, or inconsistent changes and to ensure registration, versioning, security checks, and documentation are synchronized.

Core Features & Use Cases

  • Multi-stage mandatory workflow: defines requirement confirmation, structure & validation, security vetting, registration, documentation sync, and submission stages.
  • Security and dependency integration: prescribes use of skill-vetter for security scans and skill-lifecycle-manager for dependency and version checks.
  • Registration and documentation enforcement: ensures SKILL.md presence, package.json registration, README and CHANGELOG updates, and semver-compliant version bumps.
  • Use case: a contributor adding a new skill is guided to complete naming checks, add SKILL.md, run security vetting, register in package.json, update README and CHANGELOG, and follow commit conventions.

Quick Start

Follow the governance checklist to validate a new or changed skill before committing.

Frequently Asked Questions about skill-governance

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

FAQPage Schema
How do I enforce security and compliance when adding new skills to a repository?

To enforce security and compliance for new skills, you must follow a multi-stage governance workflow that includes structure validation, security vetting, package.json registration, and synchronized documentation updates.

What is the required lifecycle process for updating or deleting skills in a directory?

The skill lifecycle process requires SKILL.md presence, dependency checks, security scans, semver-compliant version bumps, and synchronized README and CHANGELOG updates before any commit is accepted.

How do I register a new skill and ensure its documentation is synchronized?

Register a new skill by adding it to package.json, ensuring SKILL.md is present, and synchronizing both README and CHANGELOG updates to maintain consistent documentation across the repository.

Does skill governance require security vetting and dependency checks before submission?

Yes, skill governance requires security vetting via skill-vetter and dependency checks via skill-lifecycle-manager to ensure no insecure or undocumented changes are submitted to the repository.

What are the limitations of managing skill updates without a defined governance workflow?

Without a defined governance workflow, skill updates risk undocumented changes, unverified security vulnerabilities, inconsistent versioning, and desynchronized documentation across the repository.

Can I use skill governance to enforce semver-compliant version bumps and commit conventions?

Yes, skill governance enforces semver-compliant version bumps and requires contributors to follow specific commit conventions to maintain repository consistency and lifecycle tracking.