What problem does it solve?
This Skill eliminates the guesswork and common pitfalls of writing SLICC agent skills, solving the problem of skills that fail to load, have broken trigger descriptions, or don't follow platform conventions that prevent them from working as intended.
Core Features & Use Cases
- Frontmatter & Discovery Rules: Covers required SKILL.md fields (name, description, allowed-tools), valid skill root paths (native /workspace/skills/ vs compatibility .agents/ and .claude/ roots), and discovery precedence to ensure skills are found by the agent.
- Trigger Description Best Practices: Teaches how to write description fields that reliably match user intent, avoiding vague keyword lists that cause skills to load at irrelevant times.
- Companion File Guidance: Explains when and how to ship .jsh JavaScript shell scripts for deterministic tasks and .bsh browser hooks for site-specific automations, including runtime surface rules and capability bridges.
- Use Case Example: If you want to build a skill that automates pulling invoice data from a vendor portal, this Skill teaches you how to structure the SKILL.md frontmatter so the agent loads it only when the user asks for invoice-related tasks, and how to add a .jsh helper for safe, deterministic API calls.
Quick Start
Use the skill-authoring skill to create a new SLICC skill that automates sending daily status updates to your team's Slack channel, following all frontmatter and description best practices to ensure it loads reliably when you ask for Slack-related tasks.
