Agent skill · Workflow & Productivity

sticky

Use when the user wants to set auto-routing mode: on (every task-shaped message routes), auto (intent-verb messages route — default), or off (no auto-routing). Intent-detection runs by default; use this skill to expand to full sticky or disable entirely. Trigger with /hyperflow:sticky, "make hyperflow sticky", "stop using hyperflow", "is hyperflow sticky", "auto-route to hyperflow", "disable hyperflow auto-routing".

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill sticky --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 10 KB
Bundled scripts: none
Version: 4.9.0
Allowed tools: ReadWriteEditBash(rm:*)Bash(ls:*)
Requires: Designed for Claude Code
Path: plugins/ai-agency/hyperflow/skills/sticky/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Sticky Set per-project auto-routing mode. Three states: | State | Default? | Behavior | |---|---|---| | `auto` | yes (when `.sticky` absent) | **Intent-detection routing** — messages containing chain-starter verbs (`audit`, `debug`, `fix`, `brainstorm`, `scope`, `deploy`, `review`, …) auto-route. Pure conversation passes through. | | `on` | — | **Full sticky** — every task-shaped message routes, even without explicit intent verbs | | `off` | — | **All auto-routing disabled** — only explicit `/hyperflow:*` slash commands trigger chains | Intent-detection is the floor — the user gets it without any opt-in (the orchestrator scans every user message for chain-starter verbs and routes when matched). Sticky `on` raises the ceiling; sticky `off` lowers the floor. Full doctrine: [DOCTRINE.md](../hyperflow/DOCTRINE.md) Layer 1 auto-routing clause (intent verb taxonomy + routing contract + bypass patterns). ## Subcommands | Subcommand | Description | |---|---| | `on` | Set state: on — full sticky routing on every task-shaped message | | `auto` | Set state: auto — intent-verb routing only (the default) | | `off` | Set state: off — disable ALL auto-routing including intent detection | | `sta

What's inside
Steps it walks through
  1. Subcommands
  2. State persistence
  3. Subcommand Details
  4. on
  5. auto
  6. off
  7. status
  8. Behavioural contract
  9. Activation triggers
  10. Anti-patterns (when sticky is ON)
  11. Flow
  12. Overview
  13. Prerequisites
  14. Instructions
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the sticky skill do?

Use when the user wants to set auto-routing mode: on (every task-shaped message routes), auto (intent-verb messages route — default), or off (no auto-routing). Intent-detection runs by default; use this skill to expand to full sticky or disable entirely. Trigger with /hyperflow:sticky, "make hyperflow sticky", "stop using hyperflow", "is hyperflow sticky", "auto-route to hyperflow", "disable hyperflow auto-routing".

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill 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,630 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.

Keep going