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).
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add jeremylongshore/tons-of-skills-marketplace --skill hyperflow-sticky --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Hyperflow Sticky?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeremylongshore-hyperflow-sticky)More formats (shields.io, HTML) on the badges page.
---
name: hyperflow-sticky
description: 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).
---
# 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 only when a `/hyperflow*` command is explicitly invoked.
## Steps
1. Read the requested mode (on / auto / off).
2. Write it to `.hyperflow/.sticky-mode` (one word).
3. The core `hyperflow` skill reads this on each task to decide whether to auto-route.
4. Print the new mode.
## Rules
- This only changes routing behavior — it never runs work. Default is `auto` when the file is absent.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
