skill-developer

Automate Claude Code skill creation with YAML frontmatter and hook-based activation.

4|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/weirdgme/claude-code-infrastructure-showcase --skill skill-developer-weirdgme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-developer
Source: https://github.com/weirdgme/claude-code-infrastructure-showcase/tree/main/.claude/skills/skill-developer
Command: npx skills add https://github.com/weirdgme/claude-code-infrastructure-showcase --skill skill-developer-weirdgme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design and manage Claude Code skills with YAML frontmatter, trigger patterns, enforcement levels, hook mechanisms, and progressive disclosure to ensure reliable auto-activation.

Core Features & Use Cases

  • Two-hook architecture: UserPromptSubmit (suggestions) and PreToolUse (guardrails)
  • Guidelines for skill-rules.json structure and enforcement levels
  • Session-aware guardrails to avoid nagging in a single session
  • Troubleshooting, versioning, and hook mechanics documentation

Quick Start

Create a new skill folder, add SKILL.md with name/description frontmatter, and place optional resources. Update skill-rules.json and run tests to verify triggers.

Frequently Asked Questions about skill-developer

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

FAQPage Schema
How do I create Claude Code skills with YAML frontmatter and trigger patterns?

Claude Code skills use YAML frontmatter in SKILL.md to define metadata, trigger patterns via UserPromptSubmit and PreToolUse hooks, and skill-rules.json for enforcement configuration. This automated approach ensures reliable activation and guardrail application across skill files.

What are the two-hook architecture and when should I use each hook?

UserPromptSubmit hooks trigger suggestions early in user queries, while PreToolUse hooks enforce guardrails before tool execution. Use UserPromptSubmit for contextual guidance and PreToolUse for safety-critical domain constraints and session-aware rule enforcement.

How do I structure skill-rules.json and configure enforcement levels?

skill-rules.json defines rules with enforcement levels controlling how strictly triggers apply. Structure includes trigger conditions, action types, and session tracking to avoid redundant notifications. Progressive disclosure guidelines prevent overwhelming users while maintaining guardrail integrity.

Can I test skill triggers before deployment?

Yes. Create a skill folder with SKILL.md frontmatter, add optional resources, populate skill-rules.json, and run tests to verify trigger patterns activate correctly across your skill files before live use.

What's the 500-line rule and why does skill design matter?

The 500-line rule establishes a complexity ceiling for skill maintainability. Skill design encompasses frontmatter guidelines, hook mechanics, progressive disclosure, and guardrail types to ensure scalable, reliable auto-activation without exceeding functional limits.

How do session-aware guardrails prevent nagging users?

Session tracking in skill-rules.json tracks which guardrails fired within a single session. This prevents repeated enforcement of the same rule, improving user experience while maintaining safety constraints across Claude Code interactions.