agentsclimarketplace
Sign in

Canonical advisor routing

Skill yeaight7/agent-powerups/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.

2 things 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.
  • runs commandsInstructs the agent to run 3 commands, including `apx ask-codex "review this patch from a security perspective"` and 2 more.

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,273 of the 2,403 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 63 of 1273, across 62 files
  • Provide a recommended answer for each questionin 47 of 1273, across 45 files
  • Rank findings by severityin 44 of 1273
  • Use parameterized queries for database accessin 38 of 1273, across 20 files
  • Validate all user input with schemasin 33 of 1273, across 15 files
  • Store secrets in environment variablesin 32 of 1273, across 14 files
  • Explore the codebase to answer questionsin 31 of 1273, across 29 files
  • Store tokens in httpOnly cookiesin 30 of 1273, across 12 files
  • Implement rate limiting on API endpointsin 30 of 1273, across 12 files
  • Sanitize user-provided HTMLin 29 of 1273, across 11 files
  • Return generic error messages to usersin 28 of 1273, across 10 files
  • Cite file and line for every findingin 28 of 1273, across 25 files

Said here and by no other author read

  • Use apx ask wrappers for all provider calls
  • Write provider responses to the artifact directory
  • Verify local CLI installation and authentication
  • Use relay skills for multi-turn tasks

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 325,949. 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.