Skill2.9k estrellas del repoactualizado 6d ago

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).

Ver fuente Repositorio: tons-of-skills-marketplace

Instalar en Claude Code

Copiar

git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/hyperflow-sticky && cp -r /tmp/hyperflow-sticky/plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-sticky ~/.claude/skills/hyperflow-sticky

Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

Definición

SKILL.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.

Del mismo repositorio

agency-osSkill

apexSkill

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

apex-planSkill

Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

apex-reconSkill

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

apex-reviewSkill

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

apex-statusSkill

CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

apex-takeoverSkill

System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".

atlasSkill

Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports.