Flow Router
SkillMediaFlow network throughput window — live download/upload meter, interface selection, single-height center-stack docking, classic/modern window controllers, and rendering behavior.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Flow Router skill
What this skill tells your AI
The instructions your AI receives, as published by ad-repo/nullplayer in skills/flow/SKILL.md and read by ahel’s review.
Trigger
Use Flow when .agents/ exists, spec bundles live under .agents/bundles/specs/, or the user requests a Flow action. Flow is a skill, not a CLI; never run flow as a shell command.
Workflow
Route the requested operation directly to its owning lifecycle skill:
setup→flow-setupprd|plan|refine|revise|research|task→flow-planningimplement→flow-executionsync|status|refresh→flow-sync-statusreview|finish|archive|revert|docs|cleanup|validate→flow-completion
The router owns no operations and performs no disk mutations.
Guardrails
- Load only the selected lifecycle skill; let it resolve needed context.
- Task files under
.agents/bundles/specs/<flow_id>/tasks/are the sole authority for task state. - Preserve Git history and tag immutability.
Output
Identify the selected lifecycle skill and hand off the request immediately.
Validation
Confirm exactly one lifecycle owner matches the requested operation and that
the active host exposes its /flow:<operation> command or can load the named
owner skill directly.
Example
For a request like "implement the active flow", route to flow-execution without applying claim mutations in the router.
References
Signals
- GitHub stars
- 120
- Forks
- 9
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
flow- Source
- github.com/ad-repo/nullplayer