skill-developer

Configure and debug Claude Code skills with triggers and hooks.

5|Updated Oct 31, 2025
One-click install
npx skills add https://github.com/deomiarn/claude-setup-template --skill skill-developer-deomiarn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-developer
Source: https://github.com/deomiarn/claude-setup-template/tree/main/.claude/skills/skill-developer
Command: npx skills add https://github.com/deomiarn/claude-setup-template --skill skill-developer-deomiarn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex process of creating, configuring, and troubleshooting Claude Code skills, ensuring they activate correctly and enforce best practices. It helps developers build robust, reliable AI workflows without manual guesswork, saving time on setup and debugging.

Core Features & Use Cases

  • Skill Creation & Configuration: Guides through defining skill structure, YAML frontmatter, and trigger conditions in skill-rules.json.
  • Trigger Management: Explains how to set up keyword, intent, file path, and content-based triggers for precise skill activation.
  • Hook Mechanism Debugging: Details the UserPromptSubmit and PreToolUse hooks, helping diagnose why skills might not be suggesting or blocking as expected.
  • Use Case: Imagine you're building a new feature and want Claude to automatically suggest a "database-verification" skill whenever you mention "Prisma" or "schema," and block direct database edits until the skill is used. This skill helps you configure and debug that exact behavior, ensuring your guardrails work as intended.

Quick Start

Use the skill-developer skill to create a new skill called 'my-new-feature-skill' that triggers when I mention 'new feature' in my prompt.

Frequently Asked Questions about skill-developer

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

FAQPage Schema
How do I automate Claude Code skill activation based on keywords and patterns?

Skill activation automates through trigger patterns defined in skill-rules.json, detecting keywords, intent patterns, file paths, and content to activate guardrail and domain skills automatically during prompts and tool usage without manual intervention.

What's the best way to configure triggers for Claude Code skills?

Configure triggers in skill-rules.json by specifying keyword matches, intent patterns, file path conditions, and content patterns, then set enforcement modes—block, suggest, or warn—to control how and when skills activate during code project prompts and tool verification.

How do I debug why my Claude Code skill isn't triggering or blocking?

Debug skill activation by examining UserPromptSubmit and PreToolUse hook mechanisms in skill-rules.json, verifying trigger conditions match your keywords and patterns, checking session tracking state, and confirming enforcement mode settings align with your intended behavior.

Can I use skill rules to gate tool usage before execution?

Yes, skill rules support pre-tool verification gating through the PreToolUse hook, allowing you to enforce skill checks before tools execute, block direct operations until guardrails are satisfied, and track enforcement across sessions.

What file formats and structure do I need for Claude Code skill configuration?

Claude Code skills require YAML frontmatter for skill metadata and a skill-rules.json file defining trigger conditions, hook types (UserPromptSubmit, PreToolUse), enforcement modes, skip conditions, and session-aware tracking to orchestrate skill activation.

Can I create conditional skill activation with skip conditions and multiple trigger types?

Yes, skill rules support configurable skip conditions, multiple concurrent trigger types (keywords, intent, file paths, content patterns), and session-aware enforcement, enabling fine-grained control over when skills activate and whether they suggest, warn, or block.