agentsclimarketplace
Sign in

Canonical advisor routing

Skill yeaight7/agent-powerups/plugins/agentic-systems/skills/canonical-advisor-routing

Use when routing a prompt to a local provider CLI for a second opinion, review, or plan -- you are about to call a provider directly, need the response saved for later, or want a single consistent way to invoke codex/gemini/claude.From its SKILL.md

Install
npx -y skills add yeaight7/agent-powerups --skill canonical-advisor-routing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.3 KB, 694 tokens by cl100k_base, as published. Nobody here has run it

Purpose

Route a prompt through a local provider CLI and persist the result as an artifact. The execution path is process-first: always go through the canonical apx ask-* wrappers rather than hand-assembled raw provider commands, so routing and artifact capture stay consistent.

When to Use

  • You want a focused second opinion, review, or plan from a local provider
  • You are about to invoke a provider CLI directly and want a consistent entry point
  • The response needs to be saved to disk for later reference, not just printed
  • A previous wrapper run misbehaved and you are debugging the routing

Inputs

  • A clear prompt describing the task for the advisor
  • The chosen provider (codex, gemini, or claude) installed and authenticated locally

Workflow

  1. Pick the provider and frame the prompt. Choose ask-codex, ask-gemini, or ask-claude based on the task, and write a single self-contained prompt string.

  2. Invoke the canonical wrapper. Run the prompt through the apx ask-* command. Do not manually assemble raw provider CLI commands unless you are debugging the wrapper itself.

    apx ask-codex "review this patch from a security perspective"
apx ask-gemini "suggest UX improvements for this flow"
apx ask-claude "draft an implementation plan for issue #123"

  3. Confirm prerequisites if the call fails. Verify the selected local CLI is installed and authenticated before retrying; a missing or unauthenticated CLI is the usual cause.

  4. Persist the response as an artifact. Write the result to the standard artifact location so it can be reviewed later. The path is .agent-powerups/artifacts/ask/ with a filename of the form provider-slug-timestamp (Markdown extension).

  5. For multi-turn or session work, defer to the relay skills. When the task needs cross-turn context rather than a one-shot answer, route through the relay siblings (relay-codex, relay-gemini, relay-claude) instead of repeated ask-* calls.

Output

  • The provider's response written under .agent-powerups/artifacts/ask/ with a provider-slug-timestamp Markdown filename
  • A consistent, reproducible routing path that other agents can follow

Verification

  • The provider was invoked through an apx ask-* wrapper, not a hand-built raw command
  • The selected local CLI was installed and authenticated before the call
  • The response was written to the standard .agent-powerups/artifacts/ask/ location
  • The artifact filename follows the provider-slug-timestamp pattern

Failure Modes

  • Bypassing the wrapper — assembling raw provider CLI commands by hand outside of debugging, which loses consistent routing and artifact capture.
  • Unauthenticated CLI — invoking a provider whose local CLI is not installed or signed in, so the call fails before producing any artifact.
  • Lost response — reading the answer from stdout only and never writing it to the artifact location, leaving nothing to review later.
  • Wrong tool for the job — using one-shot ask-* for work that needs cross-turn context instead of the relay siblings.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most review quality skills give in 694 tokens

Counted across 1,048 of the 1,783 authors here whose files we hold, read 2026-08-07

  • Ask questions one at a timein 81 of 1048, across 64 files
  • Provide a recommended answer for each questionin 73 of 1048, across 50 files
  • Explore the codebase instead of asking answerable questionsin 66 of 1048, across 42 files
  • Resolve dependencies between decisions one-by-onein 42 of 1048, across 17 files
  • Interview the user relentlessly about the planin 38 of 1048, across 13 files
  • Order findings by severityin 31 of 1048
  • Resolve each branch of the decision treein 27 of 1048, across 5 files
  • Run a grilling sessionin 26 of 1048, across 5 files
  • Update CONTEXT.md immediately when a term is resolvedin 26 of 1048, across 11 files
  • Propose precise canonical terms for vague languagein 25 of 1048, across 7 files
  • Create documentation files lazilyin 24 of 1048, across 5 files
  • Assign severity to every findingin 24 of 1048

Said here and by no other author read

  • write a single self-contained prompt string
  • invoke the canonical wrapper
  • persist the response as an artifact
  • use relay skills for multi-turn work

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,645. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.