plumbeer-skill-creator

Create agent skills following Plumbeer's philosophy and authoring best practices.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/marioplumbeer/skills --skill plumbeer-skill-creator-marioplumbeer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plumbeer-skill-creator
Source: https://github.com/marioplumbeer/skills/tree/main/.agents/skills/plumbeer-skill-creator
Command: npx skills add https://github.com/marioplumbeer/skills --skill plumbeer-skill-creator-marioplumbeer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing agent skills without a clear methodology leads to vague instructions, incoherent scope, and fragile automation. This Skill provides a structured four-step process for authoring skills grounded in real expertise, prescriptive guidance, and validation gates. ## Core Features & Use Cases - Four-Step Authoring Process: Scaffolding via skill-creator, external specification alignment, Plumbeer's six principles, and final content crafting. - Six Opinionated Principles: Ground in expertise, be prescriptive at fragile points, favor defaults over menus, design coherent units, add validation loops, and target moderate detail. - Framework Conflict Resolution: A defined priority order (Plumbeer > AgentSkills spec > skill-creator defaults) for resolving contradictory guidance. - Use Case: You want to build a new code-review skill. This Skill walks you through naming it with the plumbeer- prefix, writing an imperative description, mapping 3-5 use cases, and adding approval gates before autonomous operations like merges. ## Quick Start Use the plumbeer-skill-creator skill to help me author a new agent skill for reviewing pull requests.

Frequently Asked Questions about plumbeer-skill-creator

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

FAQPage Schema
How do I create a new agent skill for Claude?▼

Start with the skill-creator scaffolding to generate the directory and SKILL.md, then apply the AgentSkills specification and Plumbeer's principles. Finish by naming it with the plumbeer- prefix, writing an imperative description, and mapping real use cases.

What makes a good SKILL.md description?▼

A good description uses imperative phrasing, stays specific, and remains under 1024 characters. Frame it as an instruction to the agent, such as 'Use this when...', so discovery and activation work reliably.

When should a skill include validation gates?▼

Add validation gates whenever the skill performs autonomous operations like file writes, commits, or PR merges. Present the plan, ask 'Proceed?', and only execute after explicit user approval to prevent destructive mistakes.

What is the difference between a coherent skill and a one-off task?▼

A coherent skill solves a class of problems, like 'code review' for any PR, while a one-off task targets a single instance, like 'review my PR from yesterday'. If you cannot describe the skill in one sentence, the scope is likely incoherent.

How are conflicts between skill authoring frameworks resolved?▼

Resolve conflicts in priority order: Plumbeer's philosophy first, then the AgentSkills specification, then skill-creator defaults. The customization layer wins because it is grounded in repeated practical experience.