skill-update

Updates an existing governed skill through candidate resolution, approval gating, and dependency validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Modifying an existing governed skill is risky: the wrong skill can be targeted, changes can break dependency wiring, and documentation can drift out of sync. This Skill enforces a controlled update workflow that resolves the exact target skill, requires explicit approval before any mutation, and keeps inventory, help prompts, and project documentation consistent. ## Core Features & Use Cases - Candidate Resolution: Matches user-supplied names against canonical skill IDs, aliases, descriptions, and triggers, presenting ranked options when the target is ambiguous instead of guessing. - Approval-Gated Mutation: Presents a complete change proposal listing every file to modify and requires an explicit -Proceed or --proceed token before writing anything. - Dependency and Documentation Refresh: Re-runs dependency analysis, regenerates per-skill help prompts, and updates the skill inventory, Project Understanding, and project guide after the change. - Use Case: A user asks to "update the Azure cleanup skill to also handle resource groups." The Skill resolves the request to azure-cleanup, proposes the exact contract and test changes, waits for --proceed, then applies the update and revalidates the dependency graph. ## Quick Start Ask the agent to update an existing skill, for example: update the azure-cleanup skill to also remove empty resource groups, then review the proposal and reply with --proceed to apply it.

Frequently Asked Questions about skill-update

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

FAQPage Schema
How do I update an existing governed skill safely?

Describe the change you want and name the skill. The workflow resolves the exact skill ID, presents a full proposal of files and behavior changes, and only mutates after you reply with -Proceed or --proceed.

What happens if the skill name I give is ambiguous?

The workflow ranks plausible matches against canonical IDs, aliases, descriptions, and triggers, then presents the candidate IDs for you to select. It never mutates the closest match without your explicit selection.

Can I create a new skill through the update workflow?

No. When no plausible existing skill matches your request, the workflow reports that and routes new capability requests to skill-create. The update workflow only modifies exactly one existing skill.

What approval is required before changes are applied?

You must enter -Proceed or --proceed after reviewing the complete proposal. Silence, a prior general request, or a different token does not authorize mutation, and scope changes require a new approval token.

What gets refreshed after a skill is updated?

The dependency graph is revalidated for acyclic closure, the per-skill help prompt is regenerated, and the skill inventory, Project Understanding, project guide, and human-facing catalog documentation are refreshed from verified repository evidence.