What is the recommended first step when troubleshooting skill issues?	Use the skills validator tool to catch structural problems before debugging.
If a skill fails to trigger, what is the most common cause?	The description lacks sufficient overlap with how the user actually phrases their requests (semantic matching).
How should a user fix a skill that fails to trigger?	Add specific trigger phrases that match the natural language requests users would make.
What are the two structural requirements for a skill to load correctly?	The `SKILL.md` file must be inside a named directory (not at the root), and the file name must be exactly `SKILL.md`.
What command should be run to diagnose specific skill loading errors?	`claude --debug`.
If a skill is ignored due to a priority conflict, what is the simplest solution?	Rename the skill to something more distinct.
What must be checked and fixed if a skill fails due to permission issues during runtime?	The script needs execute permission, which is fixed using `chmod +x`.
When developing skills, what path separator should always be used, even on Windows?	Forward slashes (`/`).
If a skill fails because it requires external packages, where must the dependency information be added?	The skill description.
If Claude uses the wrong skill or seems confused between two skills, what must be done with the descriptions?	Make the descriptions more distinct and specific to prevent overlap.