meta

Generate semantic prompts and toxicity metadata for Claude Code skills.

9|3|Updated Jun 29, 2012

Search Tags:#debugging #claude #activation #frontmatter #skill-writing

Ready to run

npx skills add https://github.com/whilp/dotfiles --skill meta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: meta
Source: https://github.com/whilp/dotfiles/tree/main/.claude/skills/meta
Command: npx skills add https://github.com/whilp/dotfiles --skill meta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to writing, debugging, and refining Claude Code skills to ensure reliable activation and clear descriptions.

Core Features & Use Cases

Frontmatter validation: ensures required fields like name and description exist and are correctly formatted.
Debugging checklist: guides diagnosing activation failures and improving skill clarity.

Quick Start

Copy the frontmatter pattern from this guide when creating a new skill and run the validation script to verify structure.

Frequently Asked Questions about meta

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

FAQPage Schema

How do I write a Claude Code skill with proper frontmatter and metadata?▼

Frontmatter defines your skill's activation and scope. Required fields include name, description, and activation triggers. Use the three-sentence request format, follow the [Action] [Input] to produce [Output] pattern for descriptions, and include toxicity assessment fields (is_toxic, toxic_reason) to generate valid skill JSON.

What makes a skill description clear and precise for Claude Code?▼

Skill descriptions must follow a fixed semantic structure: state the action, define inputs, specify outputs. This high-density format ensures reliable activation and predictable behavior. Combine it with frontmatter validation to catch formatting errors before deployment.

How do I debug why my Claude Code skill isn't activating?▼

Activation failures stem from missing or malformed frontmatter, unclear request scope, or safety metadata gaps. Use the debugging checklist to validate field presence, verify the description follows the [Action] [Input] to [Output] contract, and confirm toxicity fields are properly set.

What's the difference between skill request and description in the metadata?▼

Request is a concise three-sentence trigger statement; description is a structured explanation using the [Action] [Input] to produce [Output] format that defines what the skill does and what outputs it generates.

Can I use this guide to improve an existing skill's clarity?▼

Yes. Apply the frontmatter validation pattern and description framework to refine existing skills. The debugging checklist helps identify gaps in activation scope or safety metadata that reduce reliability.

Why is toxicity assessment required in skill metadata?▼

Toxicity fields (is_toxic and toxic_reason) are part of the valid JSON contract for skill definitions. They ensure safety checks are explicit and metadata remains structurally complete for Claude Code processing.