Install a skill from Vercel or GitHub
Read the trigger rules before installing — overly broad triggers make every prompt fire unrelated skills.
by @whitney · recommended tool Claude · 0 unlocks
0
ALTERNATES
Vercel Skills
EXAMPLES · WHAT THIS PROMPT PRODUCES
Sample output
I reviewed the skill definition you pasted (`competitor-teardown`). Here's the install check before I add it:
**Front-matter — valid**
- `name: competitor-teardown` ✓
- `description:` present and clear ("produces a structured teardown of a named competitor") ✓
- License and author fields present ✓
**Triggers — one concern**
The skill fires on the keywords `competitor`, `analyze`, and `teardown`. The word `analyze` alone is too broad — it'll fire on unrelated requests like "analyze this spreadsheet." **Recommend** narrowing the trigger to require `competitor` or `teardown` specifically, and dropping the standalone `analyze`.
**Tools it needs**
The definition requests `WebSearch` and `WebFetch` (to pull live competitor pages). Both are reasonable for this skill's purpose. It does **not** request file-write or shell access — good, nothing unsafe here.
**Missing / worth adding**
- No output-length cap, so teardowns may run long. Consider adding a "max 1 page" instruction.
- No avoid-list (e.g., "don't fabricate pricing") — recommended for a research skill that could hallucinate competitor data.
**Verdict:** safe to install, but I'd tighten the trigger first. Want me to make that one edit (remove the lone `analyze` trigger) before installing, or install as-is?PRICE HISTORY0 cr · current
PROMPT TEMPLATE · v1.0.0
Install the following as a new skill in my workspace. Paste the full skill definition below. Verify the front-matter, check the triggers, and confirm which tools it needs. Tell me if anything's missing or unsafe. <PASTE SKILL DEFINITION HERE>
WORKFLOW
- 01Browse the Vercel Skills library or GitHub skill repos.
- 02Copy the skill definition (markdown or config).
- 03Paste into Claude and say 'install this as a skill'.
RESULTS · WHAT PEOPLE GOT
0Sign in to show colleagues what this case produced.
No results posted yet. Used this case? Show colleagues what it produced.
DISCUSSION
0 commentsSign in to join the conversation.
No comments yet — be the first.
MORE LIKE THIS