skill-authoring

To ensure reliable SKILL.md frontmatter activation, you must provide a matching name and description in the frontmatter, aligning the name with the parent directory to guarantee agent discoverability.

Your agent skill never activates because the SKILL.md file likely contains vague descriptions or non-spec fields like applyTo, which block execution and prevent the triggers from firing when relevant.

The required body structure for a markdown skill specification includes clearly defined scope, hard rules, examples, and anti-patterns, ensuring the imperative instructions maximize reliable activation when triggered.

To fix a SKILL.md file using non-spec fields like applyTo, remove the invalid fields and ensure the frontmatter and body meet the agentskills.io spec by defining matching name, description, scope, and hard rules.

Best practices for testing agent skill activation prompts involve validating the imperative body structure and avoiding common pitfalls, ensuring the frontmatter name and description match the directory to fire triggers reliably.

Yes, you can author agent skills outside the standard skills directory by writing a SKILL.md file in locations like .squad/skills/, ensuring the frontmatter and body conform to the agentskills.io specification for proper activation.