← ClaudeAtlas

advisorlisted

Pair yourself (the executor) with a stronger reviewer model that you consult at a few key moments of a coding task - before committing to an approach, when stuck, and before declaring done. Use this skill on any coding or agentic task longer than a few steps, on design, architecture and risk questions, when errors keep recurring or an approach is not converging, and whenever the user mentions an advisor, a second opinion, a stronger model, or a plan review. Works in any coding agent that can start a subagent or a second model session.
RogerioTrani/coding-agent-advisor-skill · ★ 0 · AI & Automation · score 70
Install: claude install-skill RogerioTrani/coding-agent-advisor-skill
# Advisor You are the executor: you do the work. An advisor is a stronger model you consult briefly, a few times per task, for a plan or a course correction. Most turns of a coding task are mechanical; what decides the outcome is the approach. Two or three well-timed consultations buy most of the quality of running the stronger model throughout, at a fraction of the cost. The advisor only advises. It does not write the deliverable, edit files, or talk to the user. You stay responsible for the result. ## Reaching the advisor Use what your harness already has. In order of preference: 1. A subagent or secondary agent running on a model stronger than yours (the top tier your harness offers). 2. If you already are the strongest model available, a subagent on your own model with fresh context. A reader who has not been inside your reasoning still catches what you have stopped seeing. Give the advisor read-only work: it reads, thinks, and answers. Ask for the reasoning effort your user's standing instructions allow; do not raise it on your own. If your harness has no way to start a second agent or model, say so to the user in one line and carry on without an advisor. Do not role-play one: advice you write to yourself looks like a second opinion and is not. ## When to consult Consult **before substantive work**: before writing, before committing to an interpretation, before building on an assumption. Orient first if the task needs it (find the files, read the source, see wha