hyperflow-sticky
Hyperflow auto-routing mode. Use to control how aggressively hyperflow auto-routes — "make hyperflow sticky", "stop using hyperflow", "auto-route to hyperflow", "disable hyperflow auto-routing". Sets on (every task-shaped message routes) / auto (intent-verb messages route — default) / off (no auto-routing).
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill hyperflow-sticky --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# hyperflow-sticky — auto-routing mode (Antigravity single-agent) Control hyperflow's auto-routing aggressiveness. Follow the `hyperflow` doctrine. ## Modes - **on** — every task-shaped message routes through a hyperflow workflow. - **auto** (default) — only messages whose first verb matches the routing table (build/fix/audit/scope/design/ship…) route. - **off** — no auto-routing; hyperflow runs o
What does the hyperflow-sticky skill do?
Hyperflow auto-routing mode. Use to control how aggressively hyperflow auto-routes — "make hyperflow sticky", "stop using hyperflow", "auto-route to hyperflow", "disable hyperflow auto-routing". Sets on (every task-shaped message routes) / auto (intent-verb messages route — default) / off (no auto-routing).
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill hyperflow-sticky --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.