hyperflow-sticky
The hyperflow-sticky skill controls how aggressively Claude Code auto-routes tasks through hyperflow workflows by setting routing modes. Use this skill when you want to adjust whether every task automatically routes through hyperflow (on mode), only intent-verb tasks route (auto mode, the default), or hyperflow runs only when explicitly commanded (off mode). The skill writes the selected mode to a configuration file that the hyperflow skill reads to determine routing behavior.
git clone --depth 1 https://github.com/jeremylongshore/claude-code-plugins-plus-skills /tmp/hyperflow-sticky && cp -r /tmp/hyperflow-sticky/plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-sticky ~/.claude/skills/hyperflow-stickySKILL.md
# 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.
Audit and fix Claude Code SKILL.md files to meet enterprise compliance standards. Analyzes frontmatter, required sections, and style. Use when you need to validate or repair skills in a plugin directory.
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|
|
|
|
|