aiwf:skill-developer

Create and maintain Claude Code skills with auto-activation rules.

1|Updated Jun 21, 2025
One-click install
npx skills add https://github.com/moonklabs/aiwf --skill aiwf-skill-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiwf:skill-developer
Source: https://github.com/moonklabs/aiwf/tree/main/skills/skill-developer
Command: npx skills add https://github.com/moonklabs/aiwf --skill aiwf-skill-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive guide for creating and managing Claude Code skills, covering structure, YAML frontmatter, trigger types, hooks, session tracking, progressive disclosure, and the 500-line rule.

Core Features & Use Cases

  • Master skill design: structure SKILL.md, frontmatter, and trigger configuration
  • Pattern guidance: keywords, intentPatterns, fileTriggers, contentPatterns
  • Governance & testing: session tracking, blockMessage, and progressive disclosure

Quick Start

Create a new skill in .claude/skills/{skill-name}/SKILL.md with mandatory frontmatter including name and description, then add to skill-rules.json and test.

Frequently Asked Questions about aiwf: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 trigger patterns?

Create a skill by adding a SKILL.md file in .claude/skills/{skill-name}/ with mandatory frontmatter including name and description, then define trigger patterns using keywords, intentPatterns, and fileTriggers to control when the skill auto-activates.

What are frontmatter and trigger patterns in skill design?

Frontmatter is YAML metadata at the top of SKILL.md that configures skill behavior. Trigger patterns—keywords, intentPatterns, fileTriggers, and contentPatterns—define the conditions under which Claude Code automatically activates the skill.

How do I control when a skill activates with skipConditions and blockMessage?

Use skipConditions to prevent skill activation under specific circumstances and blockMessage templating to display custom messages when a skill is blocked, enabling fine-grained governance over skill behavior and user communication.

How do I test and govern skills across sessions?

Implement session tracking to monitor skill usage patterns and progressive disclosure to gradually expose skill functionality, then validate trigger rules and blockMessage logic through testing frameworks to ensure consistent governance.

What constraints should I follow when building skills?

Adhere to the 500-line rule for skill complexity, respect hook mechanisms for integration points, configure type and enforcement settings in skill-rules.json, and manage priority to resolve conflicts when multiple skills could trigger simultaneously.

Can I set priority and type enforcement for multiple skills?

Yes, skills support type, enforcement, and priority configuration in skill-rules.json, allowing you to resolve conflicts when multiple skills match trigger conditions and control whether skill activation is mandatory or optional.