skill-developer

Create Claude Code skills with SKILL.md frontmatter and hook tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skill-developer brings order to Claude Code skill creation so teams stop missing trigger keywords, exceed the 500-line rule, or forget progressive disclosure reference files when defining new guardrails or domain guidance.

Core Features & Use Cases

  • Skill authoring checklist: Walks through writing SKILL.md frontmatter, syncing names with skill-rules.json, documenting intent patterns, and keeping content concise while pointing to detailed references for deeper knowledge.
  • Hook orchestration & diagnostics: Unpacks UserPromptSubmit and PreToolUse flows, exit-code behavior, session tracking, skip markers, and performance tips alongside troubleshooting guidance so enforcement stays reliable.
  • Use Case: When adding a database guardrail skill the guide ensures you describe keywords, include PATTERNS_LIBRARY and HOOK_MECHANISMS references, test the prompt and PreToolUse scripts, and verify the guardrail message matches SKILL_RULES_REFERENCE.

Quick Start

Use this guide to craft new SKILL.md files, align them with skill-rules.json, and run the prescribed hook tests before committing.

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 SKILL.md file for Claude Code that follows best practices?

To create SKILL.md files for Claude Code, include concise frontmatter, document trigger patterns, sync names with skill-rules.json, and use progressive disclosure reference files for detailed knowledge. Keep content under 500 lines while pointing to external references for deeper context.

What are Claude Code hook behaviors and how do PreToolUse flows work?

Claude Code hook behaviors orchestrate UserPromptSubmit and PreToolUse flows using exit codes, session tracking, and skip markers. PreToolUse scripts intercept tool execution to enforce guardrails, returning specific exit codes that control whether the tool call proceeds or gets blocked.

How do I configure trigger patterns and guardrails in a Claude Code skill?

Configure trigger patterns by documenting intent keywords in SKILL.md and syncing them with skill-rules.json. Define guardrails using PATTERNS_LIBRARY and HOOK_MECHANISMS reference files, then test PreToolUse scripts to verify enforcement messages match SKILL_RULES_REFERENCE specifications.

Why does my Claude Code skill guardrail not trigger on expected prompts?

Guardrails fail to trigger when SKILL.md keywords are missing or misaligned with skill-rules.json entries. Verify your trigger patterns match user prompts, check hook exit-code behavior in PreToolUse scripts, and confirm skip markers aren't inadvertently bypassing the enforcement logic.

Can I use progressive disclosure in skill development to keep documentation concise?

Progressive disclosure in skill development keeps SKILL.md concise by placing detailed knowledge in separate reference files like PATTERNS_LIBRARY and HOOK_MECHANISMS. This approach satisfies the 500-line limit while preserving deep domain guidance for complex guardrail and hook configurations.

What's the best way to test Claude Code hook configurations before committing?

Test Claude Code hook configurations by running prescribed hook tests that validate UserPromptSubmit and PreToolUse flows, verify exit-code behavior, and confirm guardrail messages match SKILL_RULES_REFERENCE. Check session tracking and skip markers to ensure reliable enforcement before committing.