Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From hopper
Use when the user asks Hopper to refresh vendor capabilities, probe installed CLIs, update cached models, or diagnose model cache staleness.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hopper:hopper-probeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Probe is the explicit discovery surface. It may spawn vendor CLIs and writes the machine-local cache at `~/.hopper/cache/vendor-capabilities.json`.
Probe is the explicit discovery surface. It may spawn vendor CLIs and writes the machine-local cache at ~/.hopper/cache/vendor-capabilities.json.
hopper-dispatch from PATH or the plugin root near this SKILL.md. No .hopper/ project directory is required — --probe writes the machine-local cache (~/.hopper/cache/) and runs from anywhere.codex, kimi, opencode, copilot, agy, grok, or mimo.hopper-dispatch --probe or hopper-dispatch --probe <vendor>.hopper-dispatch --models [vendor] when the user wants the detailed cached model list..hopper/queue.md or .hopper/AGENTS.md.npx claudepluginhub surebeli/hopper-plugin --plugin hopperCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.