skill-descriptions-must-include-explicit-user-facing-trigger-phrases
9 Helix skill descriptions were too generic (e.g., ‘handles X’ or ‘manages Y’) and failed to auto-trigger because Claude couldn’t match user phrasing to skill intent. Effective descriptions must include verbatim user phrases that should activate the skill (e.g., ‘when user says: deploy, release, ship, production push’). Abstract capability descriptions score ~92% auto-trigger readiness; explicit phrase lists push it to near-100%.