trevors/dot-claude
Overview
This skill helps you design, write, and validate focused Agent Skills with clear triggers, concise descriptions, and a discoverable structure. It guides you from initial design through validation and discovery testing so your skill is easy for agents to pick up and for users to find.
How this skill works
It walks you through clarifying the problem, defining 3–5 concrete triggers, and choosing a focused scope and location. It provides a compact file layout pattern, a minimal instruction file template, and checklists to validate structure, discovery, and functionality. Finally, it shows how to generate natural prompts to test discovery and iterates on trigger language and syntax errors.
When to use it
- Building a new agent skill and defining its purpose and triggers
- Refining an existing skill to improve discovery and usage
- Testing whether natural prompts map to the correct skill
- Designing skill file layouts and progressive disclosure patterns
- Validating frontmatter, description length, and trigger coverage
Best practices
- Keep one primary capability per skill or tightly related modes
- Write a description: What it does. Use when <trigger> or <trigger> or <trigger>
- Include 3–5 concrete trigger phrases using action verbs and domain terms
- Keep the main instruction file concise and move extended examples to a supporting reference file
- Validate YAML frontmatter, character limits, and that examples are realistic
Example use cases
- Create a commit-message skill: describe what it does and include triggers like ‘write a commit message’
- Build a PDF-extraction skill with triggers: ‘extract text from PDF’, ‘summarize this report’
- Author a SwiftUI review skill with modes: architecture review, debugging, migration guidance
- Test discovery: generate 2–3 natural prompts that should map to your skill and 1–2 that should not
- Iterate: if the skill is not invoked, add clearer trigger words and check YAML syntax
FAQ
Include 3–5 concrete trigger phrases that users would naturally say; use action verbs and domain terms.
How long should the main instruction file be?
Keep the main file concise—roughly 100–200 lines—with expanded patterns and examples in a single supporting reference file if needed.
12 skills
This skill helps you design, validate, and structure discoverable agent skills with clear triggers and concise descriptions.
This skill helps you iteratively optimize CUDA kernels by profiling with nsys and ncu, classifying bottlenecks, and validating improvements.
This skill profiles and benchmarks qwen3-tts-rs inference inside a CUDA Docker container, producing Chrome Trace, timing breakdowns, and bottleneck insights.
This skill transcribes WAV audio with OpenAI Whisper and reports intelligibility, optionally comparing results to expected text for quality assessment.
This skill provides the exact uv run command to download HuggingFace models with huggingface_hub, ensuring correct syntax and local directory handling.
This skill formats Markdown for Notion imports, applying standard markdown, Notion-specific syntax, and clear annotations for manual steps to ensure smooth
This skill lets you read, search, and navigate digital books from the command line, returning quotes and locations quickly.
This skill audits and improves Claude Code configurations, organizing CLAUDE.md, skills, commands, and hooks for reliable discoverability and quality.
This skill helps you set up and run Docker in Claude Code for Web environments, tackling bridge, iptables, and SSL proxy challenges.
This skill helps you write Svelte 5 components correctly by using runes and avoiding outdated Svelte 4 patterns.
This skill helps you manage jj workflows non-interactively, enforce descriptions, and streamline commits and recovery for clean, traceable version control.
This skill helps you quickly locate past solutions and commands from Claude Code conversations using semantic and text search across sessions.