prompt-evaluation-runn…
Use when evaluating prompts, LLM outputs, red-team suites, or model behavior with local eval configs and safe provider/cost controls.
Use when a Codex or generic local agent needs a focused second opinion from Gemini CLI without MCP routing.
$ npx -y skills add yeaight7/agent-powerups --skill ask-gemini --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/ask-geminiContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when a Codex or generic local agent needs a focused second opinion from Gemini CLI without MCP routing.
name: ask-gemini description: Use when a Codex or generic local agent needs a focused second opinion from Gemini CLI without MCP routing.
Use local Gemini CLI as an external advisor for brainstorming, design feedback, or focused reviews. The workflow is local-first and always leaves a Markdown artifact.
**For multi-turn advisory sessions** (persistent context across follow-ups), use `relay-gemini` instead — `apx relay start <name> --provider gemini` keeps context across turns.
Run through APX:
apx ask-gemini "Brainstorm edge cases for this CLI"
Equivalent nested APX and direct CLI calls:
apx ask gemini "Brainstorm edge cases for this CLI"
gemini -p "Brainstorm edge cases for this CLI"
If `gemini` is missing, stop and ask the user to install/configure Gemini CLI. Verify with:
gemini --version
APX writes:
.apx/artifacts/gemini-<slug>-<timestamp>.md
Artifact sections:
apx check ask-gemini apx ask-gemini "Return OK only" --json
Confirm JSON includes `provider`, `artifactPath`, `promptLength`, and raw output in `stdout`. Open the artifact before applying advice.
Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more
Repo: yeaight7/agent-powerups
Use when evaluating prompts, LLM outputs, red-team suites, or model behavior with local eval configs and safe provider/cost controls.
Use when creating or reviewing red-team eval plugins, attack templates, grader rubrics, safety fixtures, or model-risk test metadata.
Use when designing, running, debugging, or hardening deterministic eval suites for agent skills, prompts, tool workflows, or MCP-backed cases.
Use when designing tool definitions for a new agent or subagent, an agent shows high retry rates, ambiguous tool invocations, or silent failures, or an…
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…
Use when starting work in an unfamiliar area of a codebase, spawning a subagent that needs targeted file context, a first search pass missed the relevant file,…