fnl-advisor
Advisor
One agent reads the situation and gives a judgement. You stay the decider; the advisor does not drive the work.
User's request: $ARGUMENTS
When to run
Propose an advisor and wait for the user's yes, because each run spends quota. Propose it when the decision cannot be undone or changes a contract, or when your own analysis leaves you unsure. A user who asks for one needs no proposal. When the user is away, run one without the yes when a decision would otherwise wait for them, as fnl-delegate says for an absent user, and record who settled it.
Picking the advisor
- An agent the user names wins.
- Otherwise prefer contrast: a model family other than the one you run on (
fnl-delegatereferences/models.md). Three families are on offer: Claude (Claude Code), GPT (Codex) and Gemini (Antigravity Argon). Running on Claude, ask Codex or Argon; running on Codex, ask Claude Code or Argon; running on Antigravity, ask Claude Code or Codex. All read-only. The tier follows the question's difficulty: strong for an easy or medium question (a mid-priced model is enough), frontier for a hard or very hard one. - When one family is out of quota or unreachable, try the other family, and each of its models. Use a subagent of your own host with fresh context only when every model of both other families is out of quota or unreachable, and say that the opinion comes from the same family.
Load the fnl-delegate skill and the host config for the invocation commands and read-only flags. Requires the fnl-delegate skill installed beside this one. When it is missing, tell the user to add it (npx skills add finolabs/finolabs-vibecode --skill fnl-delegate, or install the whole plugin) and stop.