skill-developer

Design, assemble, and govern VET skills with standardized frontmatter and templates.

Updated Dec 13, 2025
One-click install
npx skills add https://github.com/imehr/vet --skill skill-developer-imehr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-developer
Source: https://github.com/imehr/vet/tree/main/.claude/skills/skill-developer
Command: npx skills add https://github.com/imehr/vet --skill skill-developer-imehr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Meta-architectural guidance to design, assemble, and govern VET skills at scale, ensuring consistent structure and governance across skill units.

Core Features & Use Cases

  • Provides a standardized frontmatter template for skill units including name and description
  • Guides scaffolding of new skills (markdown SKILL.md), resources/, skill-rules.json, and documentation
  • Supports governance workflows for auditing and evolving skills across the VET framework

Quick Start

Use this meta-skill to plan and scaffold a new VET skill by creating a SKILL.md with proper frontmatter and populating resources/ with topic docs. Then define trigger rules in skill-rules.json and reference resources to support activation and governance.

Frequently Asked Questions about skill-developer

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

FAQPage Schema
How do I scaffold a new skill with standardized frontmatter and trigger rules?

To scaffold a new skill, you create a SKILL.md with standardized frontmatter, populate a resources/ directory with topic documents, and define activation triggers in a skill-rules.json file. This template enforces consistent structure and governance across skill units.

What is the best way to govern and audit existing skill units across a framework?

The best way to govern and audit existing skill units is to apply a meta-architectural workflow that enforces standardized frontmatter and validates structure across the .claude/skills hierarchy. This ensures consistent unit design and repeatable governance at scale.

How do I assemble VET skills at scale without losing structural consistency?

You assemble VET skills at scale by using a meta-architectural template that standardizes frontmatter, scaffolds markdown files, and defines trigger rules. This enforces a repeatable workflow for creating, validating, and governing skill units across teams.

Do I need a specific directory structure to organize skill templates and resources?

Yes, you need a specific directory structure that includes a SKILL.md file for frontmatter, a resources/ directory for supporting topic documentation, and a skill-rules.json file to define trigger rules and reference resources for activation.

When should I not use a meta-skill approach for skill development?

You should not use a meta-skill approach if your project requires a one-off, highly customized skill that does not need to align with a broader governance framework, standardized frontmatter, or repeatable scaffolding workflows across the .claude/skills hierarchy.