skill-developer

Create and manage Claude Code skills with structured templates and validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating and maintaining Claude Code skills with auto-activation can be error-prone without clear guidelines and structured templates.

Core Features & Use Cases

  • Clear frontmatter templates and naming conventions to ensure consistency across skills.
  • Centralized guidance on trigger types (keywords, intent patterns, file paths, content patterns) and enforcement levels for reliable auto-activation.
  • Progressive disclosure via reference files (PATTERNS_LIBRARY.md, TROUBLESHOOTING.md, HOOK_MECHANISMS.md, SKILL_RULES_REFERENCE.md, TRIGGER_TYPES.md) to keep SKILL.md concise while offering depth when needed.

Quick Start

Describe the five-step workflow for creating a new skill: write a SKILL.md with frontmatter, add an entry to skill-rules.json, create or reference supportive materials, and test prompts and tool usage.

Frequently Asked Questions about skill-developer

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

FAQPage Schema
How do I create a Claude Code skill with safe auto-activation?

Creating a Claude Code skill with safe auto-activation involves writing a SKILL.md with frontmatter, adding an entry to skill-rules.json, referencing supportive materials, and testing prompts to enforce reliable trigger patterns.

What are Claude Code skill trigger patterns and how do they work?

Claude Code skill trigger patterns are defined rules in skill-rules.json that match keywords, intent patterns, file paths, or content patterns to automatically activate specific skills when user input meets the specified enforcement levels.

Why does my Claude Code skill auto-activate when it shouldn't?

Unintended Claude Code skill auto-activation typically happens when trigger patterns are too broad or frontmatter is misconfigured. You must validate your trigger types and enforcement levels in skill-rules.json to constrain activation to the correct contexts.

Do I need frontmatter in my SKILL.md file for Claude Code?

Yes, frontmatter is required in your SKILL.md file for Claude Code. It enforces naming conventions, ensures consistency across skills, and provides the necessary metadata for the system to parse and integrate the skill correctly.

What's the best way to structure Claude Code skill documentation?

The best way to structure Claude Code skill documentation is progressive disclosure: keep SKILL.md concise while moving detailed guidance into reference files like PATTERNS_LIBRARY.md, TROUBLESHOOTING.md, and SKILL_RULES_REFERENCE.md.