About this skill
Use when the user asks whether a skill already exists, wants a skill for a topic or prompt, or is looking for documentation-based skills (React, Godot, Blender, Claude Code, Unity, and similar). Searches local VibeFuse skills, then Skill Seekers presets, before creating anything new.
SKILL.md 19 lines · Skill instructions Show code Hide code
# Skill Seekers lookup You are looking up an **existing skill** that matches the user's prompt. Do not invent a new skill until this search is done. ## Procedure 1. Extract the topic from the user prompt (framework, product, docs site, or capability). 2. Call `list_skills` and scan names + descriptions for a local VibeFuse match. If one matches, `execute_skill` that skill and stop. 3. Call `mcp_skill-seekers_list_configs` (no arguments). Match the topic against preset names and descriptions (React, Godot, Blender, Claude Code, Unity Addressables / DOTween / Spine, httpx, Medusa, Astrovalley, and others). 4. Optionally call `mcp_skill-seekers_list_marketplaces` if configs did not cover the topic. 5. Report the best match (or that none exists). Quote the preset name and what it covers. 6. Only if the user then asks to **build** it: use Skill Seekers `generate_config` → `scrape_docs` → `package_skill`. Put packaged output under `C:\vibefuse\skills` when they want it installed locally. 7. If Skill Seekers MCP tools are missing, tell them to open Settings → Tools → Skill Seekers and click Connect. Do not pretend the search ran. ## Rules - Prefer an existing match over creating a duplicate skill. - Do not scrape or package unless the user asked to generate the skill. - Keep the reply short: match, why it fits, and the next optional step.