team-advisor

Binds a warm advisor agent and consults it before substantive work, commits, or when stuck.

6|1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/jl-cmd/claude-dev-env --skill team-advisor-jl-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-advisor
Source: https://github.com/jl-cmd/claude-dev-env/tree/main/packages/claude-dev-env/.agents/skills/team-advisor
Command: npx skills add https://github.com/jl-cmd/claude-dev-env --skill team-advisor-jl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Long coding sessions drift, and a single executor model can lock onto a weak approach without any checkpoint. This Skill binds one high-tier advisor (the built-in advisor tool or a warm pstack:poteto-agent) and consults it at key moments so plans, corrections, and stop signals arrive before costly mistakes. ## Core Features & Use Cases - Session-scoped advisor binding: Detects the host (Claude, Codex, or third-party), walks the model floor, and binds the strongest available advisor tier once per session, with fail-closed behavior when the bind fails. - Structured consult cadence: Consults after orientation and after writes and validation, following the hard rule of calling the advisor before the first write, edit, or state-changing shell call. - Evidence recording: Writes consult evidence (selected tier, fallback reason, reply path, validation, unresolved risks) to a session-controlled model-tier-run.json record. - Use Case: Before refactoring a module, the session consults the bound advisor with a brief built from the consult-format reference, receives an ENDORSE / CORRECTION / PLAN / STOP signal, and proceeds or adjusts accordingly. ## Quick Start Ask the agent to bind a team advisor for this session and consult it before making the first code change.

Frequently Asked Questions about team-advisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a second opinion from a stronger model during a Claude Code session?▼

Bind one advisor per session using the built-in advisor tool when available, or spawn a warm pstack:poteto-agent at high effort. Consult it after orientation and after writes and validation, following the hard rule of calling before the first write.

When should the advisor be consulted during a coding task?▼

Consult before the first write, edit, or state-changing shell call, then again after writes and validation. A normal task targets two consults, with a third reserved for recovery or reconciliation when a material fork produces new evidence.

Does the advisor workflow work on Codex or third-party hosts?▼

Yes. Codex uses the native advisor path, and third-party hosts use a headless CLI bind via codex_astra_advisor.py. When the host's model walk fails, the skill fails closed and reports to the user.

What happens if the advisor bind or reply path fails?▼

The session fails closed and reports the failure to the user. It records fallback_kind as broken only when the selected bind or reply path fails, along with the selected tier, fallback reason, and reply path in the evidence object.

How is advisor consult evidence recorded and audited?▼

Each consult is recorded with changed evidence, validation results, unresolved risks, and report-back status. The evidence object is written to the session-controlled model-tier-run.json record described in the advisor-tool reference.