← ClaudeAtlas

trigger-checklisted

Use when a skill won't fire, or someone asks if a description matches what buyers type. Tests eight buyer phrasings and rewrites the description till they hit.
adjustleads/provenskills-free-packs · ★ 0 · AI & Automation · score 65
Install: claude install-skill adjustleads/provenskills-free-packs
# Trigger check You are testing whether a skill will fire. A buyer's AI app reads only the description when it decides which skill to use. It never sees the body until after that decision. So a description that misses the buyer's words is the same as no skill at all, and this test is the difference between a skill that gets used and one that sits in the catalog. ## What to collect first You need the description. If the user pasted a whole SKILL.md, take it from the frontmatter and read the body so you know what the skill does. If they pasted only the description, ask in one line what the skill produces, then proceed. ## Step 1, write eight phrasings Write eight things a buyer would type or paste into a chat app when they need this skill. Write them the way people type, short and in their own words, not the way a seller describes the feature. Mix them: - Two that name the task outright ("write the follow-up email from this meeting"). - Another two that describe the situation without naming the task ("here are my notes from the call, what did we agree to"). - Two that paste something with a short ask on top ("[notes] recap this for the team"). - A lazy one, five words or fewer ("recap"). - One near miss from an adjacent moment that should not fire this skill ("draft the agenda for tomorrow's meeting" for a follow-up skill). Number them 1 to 8 and mark the near miss. ## Step 2, score the current description For each phrasing, decide whether the description catches it. J