skill-developer

Extract semantic metadata from Skill Units into machine-readable JSON.

19|2|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/ai-debugger-inc/aidb --skill skill-developer-ai-debugger-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-developer
Source: https://github.com/ai-debugger-inc/aidb/tree/main/.claude/skills/skill-developer
Command: npx skills add https://github.com/ai-debugger-inc/aidb --skill skill-developer-ai-debugger-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creating effective AI Skills requires adherence to specific architectural patterns, content guidelines, and trigger configurations. This Skill provides a comprehensive guide to developing, managing, and optimizing Claude Code skills, ensuring they are discoverable, efficient, and aligned with best practices. It helps developers build high-quality, self-activating AI assistants.

Core Features & Use Cases

  • Skill Creation Workflow: Step-by-step guide from file creation to trigger testing and refinement.
  • 500-Line Rule Enforcement: Learn to structure skills for optimal token efficiency and progressive disclosure.
  • AI-Powered Trigger Configuration: Master how to define skill descriptions and keywords for automatic, intelligent activation.
  • Use Case: When you need to encapsulate a new domain of knowledge or a complex workflow into an AI-driven automation, use this skill to design and implement a new Claude Skill that seamlessly integrates into the AI's context.

Quick Start

Guide me through creating a new Claude Skill, including its file structure and how to define its 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 a new Claude Skill from scratch?

Creating a Claude Skill involves defining its file structure, writing semantic metadata, configuring triggers for automatic activation, and testing against the 500-line rule for token efficiency. Start by establishing the skill's core task, keywords, and dependencies, then structure content for progressive disclosure.

What are triggers and how do I configure them for my Skill?

Triggers are the mechanisms that automatically activate your Skill based on user queries. Configure triggers by defining precise skill descriptions and keywords that match search intent. The two-tier injection model routes meta-skills and domain-skills through distinct trigger pathways for optimal relevance.

How do I structure a Skill to stay within the 500-line rule?

The 500-line rule enforces token efficiency by requiring progressive disclosure: expose core functionality upfront, then progressively reveal advanced details. Structure content into sections, use references for external detail, and test retrieval efficiency to ensure your Skill activates precisely without exceeding token budgets.

What's the difference between meta-skills and domain-skills?

Meta-skills provide foundational automation patterns and governance—like this Skill itself—while domain-skills encapsulate specialized knowledge in specific technical areas. The two-tier model ensures meta-skills inject contextual rules first, then domain-skills activate based on user intent and skill metadata.

How do I make my Skill discoverable through search?

Maximize discoverability by crafting clear, searchable keywords that describe your Skill's core task, not its structure. Write a concise tagline, use semantic metadata with vector-embedding-friendly fields like request and description, and configure trigger activation to match genuine user search vocabulary.

What role does session tracking play in Skill design?

Session tracking enables hook mechanisms that maintain context across multiple Skill activations, allowing progressive disclosure and stateful workflows. Document session scope in your Skill metadata to ensure the two-tier injection model correctly sequences meta-skill rules and domain-skill behavior.