skill-create

Create governed skill packages with validated metadata, ownership boundaries, and dependency wiring.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams building AI agent workspaces often create duplicate, inconsistent, or poorly scoped skills that conflict with existing contracts. This Skill enforces a governed authoring workflow so every new skill has valid metadata, clear ownership, acyclic dependencies, and matching documentation. ## Core Features & Use Cases - Duplicate Detection: Runs an inventory check against existing skill names, outputs, and triggers before authoring anything new. - Contract Authoring: Defines purpose, inputs, deterministic procedure, validation, failure behavior, and approval gates for each new skill. - Dependency Wiring: Analyzes both incoming and outgoing integration with existing skills, keeping dependencies acyclic and single-owner. - Use Case: When a user asks to add a reporting capability to their Copilot workspace, this Skill checks the inventory, obtains approval, authors the contract, generates the help prompt, and refreshes the skill catalog and project documentation. ## Quick Start Ask the agent to create a new skill for a bounded capability, describing its inputs, outputs, and ownership intent.

Frequently Asked Questions about skill-create

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

FAQPage Schema
How do I create a new skill for GitHub Copilot Agent mode?

Describe the capability, inputs, outputs, and ownership intent, and the skill-creation workflow checks the existing inventory for duplicates before authoring. After explicit approval, it writes the SKILL.md contract, generates a help prompt, and refreshes the catalog documentation.

How do I avoid creating duplicate skills in a repository?

Run a skill inventory comparison against existing names, descriptions, outputs, ownership, and triggers before authoring. If a matching capability exists, reuse or extend it instead of creating a new skill silently.

What metadata does a valid SKILL.md file require?

A valid SKILL.md requires YAML frontmatter with a name matching its directory ID in lowercase kebab-case, plus a description used for discovery. The body should define purpose, inputs, procedure, validation, failure behavior, and approval gates.

When should I update an existing skill instead of creating a new one?

Route to an update workflow when the request targets an existing skill ID or extends a capability already covered by an inventory match. Creation is reserved for capabilities with no reusable match, confirmed after the inventory check.

Why must skill dependencies be acyclic?

Acyclic dependencies prevent circular routing where skills depend on each other indefinitely, which breaks deterministic execution. Every declared dependency must resolve to an existing skill and remain dependency-closed.