ci-mockup-figure
Create paper and proposal figures guided by confirmed visual preferences and efficient use of page space. HTML mockups for…
@yzhao062Install SkillDevelopment
Skill
/my-router
Context-aware router that detects work type and dispatches to the right skill. Ships with a minimal default routing table; extend it in a fork, or register project-local skills in a consuming repo via routing-table.local.md or an AGENTS.local.md Routing section.
Claude Code
$ npx -y skills add yzhao062/anywhere-agents --skill my-router --agent claude-code
Codex
$ npx skills add yzhao062/anywhere-agents --skill my-router -a codex -y
Cursor
$ npx skills add yzhao062/anywhere-agents --skill my-router -a cursor -y
Gemini CLI
$ npx skills add yzhao062/anywhere-agents --skill my-router -a gemini-cli -y
GitHub Copilot
$ npx skills add yzhao062/anywhere-agents --skill my-router -a github-copilot -y
OpenCode
$ npx skills add yzhao062/anywhere-agents --skill my-router -a opencode -y
Windsurf
$ npx skills add yzhao062/anywhere-agents --skill my-router -a windsurf -y
SKILL.md
my-router.SKILL.mdname: my-router
description: Context-aware router that detects work type and dispatches to the right skill. Ships with a minimal default routing table; extend it in a fork, or register project-local skills in a consuming repo via routing-table.local.md or an AGENTS.local.md Routing section.
My Router
Overview
A routing layer that sits between the outer workflow (e.g., `superpowers` brainstorm/plan/execute/verify) and domain skills. The router reads the working directory, file types, and user prompt to decide which skill to invoke, so the user does not need to remember skill names.
In this repo's shipped form, the routing table has concrete entries for the seven shipped skills (`implement-review`, `ci-mockup-figure`, `readme-polish`, `editable-figure`, `agent-models`, `my-router` itself, and `prun` for explicit parallel fan-out intent). It is also designed as a **pattern you extend**. A fork of this repo edits `references/routing-table.md` directly. A consuming project, where that file is overwritten on every bootstrap, instead registers its own skills in a bootstrap-proof local file (`routing-table.local.md` at the repo root, or a `## Routing` section in `AGENTS.local.md`); the router reads those rows and dispatches to them. See [Extending the Router](#extending-the-router).
When to Use Superpowers vs. Direct Dispatch
The router decides this. Not all tasks need superpowers' full ceremony.
| Task shape | Route | Why | |---|---|---| | Clear, scoped task with an obvious skill match (e.g., "review staged changes") | **Direct dispatch** — router picks the domain skill and runs it immediately | Brainstorming and planning add no value when the task is already well-defined | | Open-ended, multi-step, or ambiguous task (e.g., "build a new feature", "restructure the paper") | **Superpowers first** — brainstorm → plan → execute (router dispatches during execute) → verify | These benefit from thinking before doing | | Quick edit or fix (e.g., "fix the typo on line 42", "rename this variable") | **Neither** — just do it directly | No routing or workflow needed |
The rule: **if the domain skill is obvious and the scope is clear, skip superpowers and dispatch directly. If the task needs exploration or planning, let superpowers run the outer loop and the router dispatches during execution.**
Integration with Superpowers
When superpowers is active, it handles workflow phases: brainstorm → plan → execute → verify. The router activates during the **execute** phase and dispatches to the right domain skill.
When superpowers is not active (direct dispatch or quick task), the router works standalone.
How Routing Works
At dispatch time, the router checks three signals in order (keywords, file types, project structure). In a consuming project, before applying the shipped table below, it first merges any **consumer-local routing extensions**: a `routing-table.local.md` at the repo root, or a `## Routing` section in `AGENTS.local.md`. These two files survive bootstrap (the shipped table does not), so they are where a consuming repo registers its own skills; on a keyword or file-type conflict, the local row wins. See [Extending the Router](#extending-the-router).
1. Prompt keywords (highest priority)
The user's prompt often contains the clearest signal. The shipped routing table includes keyword entries for `implement-review`, `ci-mockup-figure`, `readme-polish`, `editable-figure`, and `agent-models`. Add entries for your own skills in your fork's `references/routing-table.md`, or, in a consuming project, in a bootstrap-proof local file (see [Extending the Router](#extending-the-router)).
When a figure request explicitly asks for PowerPoint or native editability, take the `editable-figure` route ahead of the generic figure, README-polish, or slide routes. A request to simplify an existing editable figure stays on that route. An explicit HTML mockup, TikZ, screenshot, or prompt-only request keeps its requested format. Before taking that route, check that the session can perform the desktop PowerPoint validation `editable-figure` requires. If it cannot, explain the limitation and offer `ci-mockup-figure` only when its output fits the request. Do not silently substitute HTML for an explicitly requested PPTX.
A question about which model or effort an agent role runs on, a request to change one, or a doubt that a setting took effect goes to `agent-models`. Run its `show` and `doctor` commands before answering, and never state a model name or effort level from memory.
See [`references/routing-table.md`](references/routing-table.md) for the current table and the extension template.
For a paper or proposal explanatory figure, especially an overview or "Figure 1", read `editable-figure/references/gallery/index.md` through the normal skill lookup. Do this whichever figure skill the route selects, including a project-local variant such as `nsf-figure-builder`. When working for Yue Zhao, enforce its required preference-first design protocol as the top design priority. Inspect selected images and feedback, map confirmed qualities to the new design, and carry that mapping into prompts and implementation. Compare the result against those references. Preserve the requested output format; reading the gallery does not require PowerPoint or change a prompt-only task into a figure build.
2. File types in working directory
If prompt keywords are ambiguous, inspect the files being worked on. The shipped router recognizes staged git changes → `implement-review`, HTML mockup files for dashboards/timelines → `ci-mockup-figure`, a top-level `README.md` flagged for polish → `readme-polish`, and `.pptx` figure sources beside a paper, proposal, or README → `editable-figure`. Add your own file-type rules when you add new skills.
3. Project structure hints
Some projects declare their type in `AGENTS.local.md` or via directory naming conventions (e.g., a `proposals/` or `papers/` directory,
Read more
name: my-router description: Context-aware router that detects work type and dispatches to the right skill. Ships with a minimal default routing table; extend it in a fork, or register project-local skills in a consuming repo via routing-table.local.md or an AGENTS.local.md Routing section.
My Router
Overview
A routing layer that sits between the outer workflow (e.g., `superpowers` brainstorm/plan/execute/verify) and domain skills. The router reads the working directory, file types, and user prompt to decide which skill to invoke, so the user does not need to remember skill names.
In this repo's shipped form, the routing table has concrete entries for the seven shipped skills (`implement-review`, `ci-mockup-figure`, `readme-polish`, `editable-figure`, `agent-models`, `my-router` itself, and `prun` for explicit parallel fan-out intent). It is also designed as a **pattern you extend**. A fork of this repo edits `references/routing-table.md` directly. A consuming project, where that file is overwritten on every bootstrap, instead registers its own skills in a bootstrap-proof local file (`routing-table.local.md` at the repo root, or a `## Routing` section in `AGENTS.local.md`); the router reads those rows and dispatches to them. See [Extending the Router](#extending-the-router).
When to Use Superpowers vs. Direct Dispatch
The router decides this. Not all tasks need superpowers' full ceremony.
| Task shape | Route | Why | |---|---|---| | Clear, scoped task with an obvious skill match (e.g., "review staged changes") | **Direct dispatch** — router picks the domain skill and runs it immediately | Brainstorming and planning add no value when the task is already well-defined | | Open-ended, multi-step, or ambiguous task (e.g., "build a new feature", "restructure the paper") | **Superpowers first** — brainstorm → plan → execute (router dispatches during execute) → verify | These benefit from thinking before doing | | Quick edit or fix (e.g., "fix the typo on line 42", "rename this variable") | **Neither** — just do it directly | No routing or workflow needed |
The rule: **if the domain skill is obvious and the scope is clear, skip superpowers and dispatch directly. If the task needs exploration or planning, let superpowers run the outer loop and the router dispatches during execution.**
Integration with Superpowers
When superpowers is active, it handles workflow phases: brainstorm → plan → execute → verify. The router activates during the **execute** phase and dispatches to the right domain skill.
When superpowers is not active (direct dispatch or quick task), the router works standalone.
How Routing Works
At dispatch time, the router checks three signals in order (keywords, file types, project structure). In a consuming project, before applying the shipped table below, it first merges any **consumer-local routing extensions**: a `routing-table.local.md` at the repo root, or a `## Routing` section in `AGENTS.local.md`. These two files survive bootstrap (the shipped table does not), so they are where a consuming repo registers its own skills; on a keyword or file-type conflict, the local row wins. See [Extending the Router](#extending-the-router).
1. Prompt keywords (highest priority)
The user's prompt often contains the clearest signal. The shipped routing table includes keyword entries for `implement-review`, `ci-mockup-figure`, `readme-polish`, `editable-figure`, and `agent-models`. Add entries for your own skills in your fork's `references/routing-table.md`, or, in a consuming project, in a bootstrap-proof local file (see [Extending the Router](#extending-the-router)).
When a figure request explicitly asks for PowerPoint or native editability, take the `editable-figure` route ahead of the generic figure, README-polish, or slide routes. A request to simplify an existing editable figure stays on that route. An explicit HTML mockup, TikZ, screenshot, or prompt-only request keeps its requested format. Before taking that route, check that the session can perform the desktop PowerPoint validation `editable-figure` requires. If it cannot, explain the limitation and offer `ci-mockup-figure` only when its output fits the request. Do not silently substitute HTML for an explicitly requested PPTX.
A question about which model or effort an agent role runs on, a request to change one, or a doubt that a setting took effect goes to `agent-models`. Run its `show` and `doctor` commands before answering, and never state a model name or effort level from memory.
See [`references/routing-table.md`](references/routing-table.md) for the current table and the extension template.
For a paper or proposal explanatory figure, especially an overview or "Figure 1", read `editable-figure/references/gallery/index.md` through the normal skill lookup. Do this whichever figure skill the route selects, including a project-local variant such as `nsf-figure-builder`. When working for Yue Zhao, enforce its required preference-first design protocol as the top design priority. Inspect selected images and feedback, map confirmed qualities to the new design, and carry that mapping into prompts and implementation. Compare the result against those references. Preserve the requested output format; reading the gallery does not require PowerPoint or change a prompt-only task into a figure build.
2. File types in working directory
If prompt keywords are ambiguous, inspect the files being worked on. The shipped router recognizes staged git changes → `implement-review`, HTML mockup files for dashboards/timelines → `ci-mockup-figure`, a top-level `README.md` flagged for polish → `readme-polish`, and `.pptx` figure sources beside a paper, proposal, or README → `editable-figure`. Add your own file-type rules when you add new skills.
3. Project structure hints
Some projects declare their type in `AGENTS.local.md` or via directory naming conventions (e.g., a `proposals/` or `papers/` directory,
Ships withanywhere-agents
One config for every agent — Claude Code, Codex, and whatever comes next. Start with effective defaults. Add packs, small bundles of rules, skills, or permissions, as you need them. One AGENTS.md drives every agent in every repo on every machine.
2616 skills1 agent
Stars on GitHub
Momentum
- stars in total
- 261
Other skills on anywhere-agents.
@yzhao062Install Skilleditable-figure
Design editable PowerPoint overview figures, especially Figure 1 for papers and proposals, using source material and the author's…
@yzhao062Install Skillimplement-review
Review loop for staged changes. Detects content type, prepares a review request for Codex (Terminal-relay manual default, opt-in…
@yzhao062Install Skillprun
Parallel delegation fan-out on Agy. The coordinating session decomposes and integrates while task units run in parallel as Agy…
@yzhao062Install Skillreadme-polish
Audit a GitHub README and rewrite it using modern 2025-2026 patterns — centered header, badges, hero image, GitHub alert…
@yzhao062Install SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about my-router.
- Which coding agents can use my-router?
- my-router installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.