Context
Running the Agent Skills spec audit against ui-ux-pro-max v2.5.0 yields a warning:
⚠️ ui-ux-pro-max
Warning: Description lacks clear trigger phrases ('when', 'mention', 'use')
Root cause
The audit script greps the SKILL.md description for the literal words when, mention, or use to verify trigger-phrase clarity. The current description is excellent in many other ways (67 styles, 96 palettes, 57 font pairings, etc.) and lists many action verbs (plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor) but never spells out a literal "when to use" or "use to" phrase.
Suggested fix
Prepend a short "Use when…" clause to the existing description, for example:
description: "Use when designing or reviewing UI/UX. UI/UX design intelligence with 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, …"
This passes the audit, costs ~30 chars of the 1024-char budget, and makes the trigger semantics more explicit for agents that match descriptions by keyword.
Impact if unfixed
None functional — the skill works perfectly today. This is a spec-compliance warning that surfaces in user audit reports.
Reproduce
npx uipro-cli init --ai claude
# audit script from https://agentskills.io/specification.md
bash audit-skills.sh ~/.claude/skills
# → ⚠️ ui-ux-pro-max — Description lacks clear trigger phrases ('when', 'mention', 'use')
Reported via Claude Code on Windows after a fresh install. Happy to send a PR if useful.
Context
Running the Agent Skills spec audit against
ui-ux-pro-maxv2.5.0 yields a warning:Root cause
The audit script greps the SKILL.md description for the literal words
when,mention, oruseto verify trigger-phrase clarity. The current description is excellent in many other ways (67 styles, 96 palettes, 57 font pairings, etc.) and lists many action verbs (plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor) but never spells out a literal "when to use" or "use to" phrase.Suggested fix
Prepend a short "Use when…" clause to the existing description, for example:
This passes the audit, costs ~30 chars of the 1024-char budget, and makes the trigger semantics more explicit for agents that match descriptions by keyword.
Impact if unfixed
None functional — the skill works perfectly today. This is a spec-compliance warning that surfaces in user audit reports.
Reproduce
Reported via Claude Code on Windows after a fresh install. Happy to send a PR if useful.