Create Plugin

Name: Create Plugin
Availability: InStock
Author: Zack

Automate end-to-end Copilot CLI plugin creation from discovery to validation.

2|Updated Mar 19, 2026

Search Tags:#workflow #development #validation #scaffold #plugin #copilot-cli

Ready to run

npx skills add https://github.com/Poorgramer-Zack/copilot-cli-things --skill create-plugin-poorgramer-zack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Create Plugin
Source: https://github.com/Poorgramer-Zack/copilot-cli-things/tree/main/plugins/plugin-dev/skills/create-plugin
Command: npx skills add https://github.com/Poorgramer-Zack/copilot-cli-things --skill create-plugin-poorgramer-zack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The workflow eliminates the guesswork and boilerplate involved in creating a new Copilot CLI plugin by providing a structured, phase-driven process that covers discovery, planning, implementation, validation, and documentation.

Core Features & Use Cases

Phase-driven scaffolding that guides the plugin lifecycle from concept to release.
Structured component planning for skills, agents, hooks, MCPs, and settings.
Built-in validation checkpoints and references to evaluation utilities.

Quick Start

Run the plugin creation workflow to scaffold a new Copilot CLI plugin from concept to validated artifact.

Frequently Asked Questions about Create Plugin

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

FAQPage Schema

How do I scaffold a Copilot CLI plugin from scratch?▼

To scaffold a Copilot CLI plugin, you need a structured workflow that guides you through planning, implementation, and validation. A phase-driven process eliminates boilerplate by automating discovery, scaffolding components like skills and hooks, and generating validated artifacts.

What is the best way to structure Copilot CLI plugin development?▼

The best way to structure Copilot CLI plugin development is using a phase-driven lifecycle from concept to release. This involves structured component planning for skills, agents, hooks, MCPs, and settings, ensuring all elements are properly organized before implementation and validation.

Do I need a SKILL.md file to create a Copilot CLI plugin?▼

Yes, you need a SKILL.md file to create a Copilot CLI plugin. The file must include frontmatter with a name and description to initiate the workflow. You can also use optional resource directories to organize scripts, references, and assets for the plugin.

How does plugin validation work in a Copilot CLI workflow?▼

Plugin validation in a Copilot CLI workflow works through built-in validation checkpoints and references to evaluation utilities. This ensures the scaffolded components function correctly and meet requirements before the plugin is considered a validated artifact ready for release.

Can I use multi-phase workflows for Copilot CLI plugin creation?▼

Yes, you can use multi-phase workflows for Copilot CLI plugin creation. The process supports multi-phase workflows that automate the end-to-end creation cycle, covering discovery, planning, implementation, validation, and documentation to guide developers from initial concept to final release.

What components should I plan when developing a Copilot CLI plugin?▼

When developing a Copilot CLI plugin, you should plan components including skills, agents, hooks, MCPs, and settings. Structured component planning during the scaffolding phase ensures each part of the plugin lifecycle is properly configured before implementation and validation.