AGENT SKILL

team-advisor

Bind one advisor, the built-in advisor tool or a warm `pstack:poteto-agent`, and consult it before substantive work, completion, commits, or when stuck. Use when the user asks for an advisor or a second opinion on the approach.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 7
Forks
1

01 前言 Front Matter

name
team-advisor
description
Bind one advisor, the built-in advisor tool or a warm `pstack:poteto-agent`, and consult it before substantive work, completion, commits, or when stuck. Use when the user asks for an advisor or a second opinion on the approach.

02 资源文件 1

03 SKILL.md 正文

Team Advisor

One warm advisor at the strongest tier this session can reach. This session is the sole consumer.

Refs

Doc Holds
docs/references/advisor-tool.md Consult cadence and weight. When to call, the hard rule before first write, and how to treat advice. Read this for every consult.
~/.claude/_shared/advisor/advisor-protocol.md Bind and lifecycle. Session identity, host detect, model floor, warm-up, CLI fallback. Its read map routes each moment to a reference/ detail file.
Installed poteto-mode skill Reply contract. The advisor prompt carries ENDORSE / CORRECTION / PLAN / STOP.
reference/advisor-docs-review.md Anthropic advisor-tool source facts: measured effects, Sonnet steering, cost levers, failure modes. Background. Read it when tuning the bind, not on every consult.

Bind

  1. Name the session identity first (protocol Host profiles), then walk the model floor.
  2. Claude: when advisor is in this session's tool list, the built-in advisor tool is the advisor. Spawn nothing and call advisor() at each consult point. Otherwise spawn or resume pstack:poteto-agent at Opus high with the advisor response contract in the prompt. When the bound model is out of usage, use the configured fallback at the same effort. Codex: use the native advisor path. Third-party: use the headless advisor path. When the host's walk fails, fail closed.
  3. Name the warm instance team-advisor-agent and keep its advisor response contract in every first prompt. When a native Codex subagent spawn is the advisor path and the spawn tool has a flags field, pass flags: ["--advisor"] with Astra and record advisor_flag: passed. A spawn that skips an offered flag is a failed bind. When the spawn tool has no flags field, as in codex exec, spawn gpt-6-astra plainly, record advisor_flag: unavailable, and treat it as bound.
  4. Skip the multi-consumer "who you are" opener. This session is the sole consumer.
  5. When the bind or reply path fails, fail closed and report to the user. On a third-party host, only the bound advisor issues ENDORSE / CORRECTION / PLAN / STOP.

GOTCHA (Cursor / ThirdParty + Astra): when the walk reaches Astra or the user asks for Astra, first tool call is python ~/.claude/_shared/advisor/scripts/codex_astra_advisor.py --bind --enable-astra --cwd <repo-root> with the charter on stdin. Do not use Agent or Task. Do not search for a probe path. Details: third-party-bind.md GOTCHA and astra-rung.md.

Full walk, charter, consult packet, Astra routing, and drift re-bind live in the protocol read map and its reference/ files.

Consult

Follow When to call, Hard rule, and How to treat advice in advisor-tool.md.

Build every first brief with _shared/advisor/reference/consult-format.md. Later briefs carry only the delta and changed evidence.

With the built-in advisor tool, call advisor() with no brief. The tool forwards the whole transcript. Its reply is free text, not one of the four signal words, so weigh it per How to treat advice in advisor-tool.md.

Aim for two consults on a normal task: one after orientation and one after writes and validation. Reserve a third for advisory recovery or reconciliation guidance, and add a consult when a material fork produces new evidence. This is an advisory target owned by the task, not a cap or gate.

Constraints

  • One bind per session; this session owns the built-in tool choice, spawn, in-session Astra spawn, or CLI bind, drift re-bind, and shutdown.
  • Bind at or above the protocol floor for this host.
  • The advisor only answers (messaging); the session runs tools and posts.
  • Keep an optional reference gap in the reference record: path, status, repair action, and repair result. A reference gap leaves bind status separate.
  • On Codex, select native Astra when its bind and reply validation pass. Record selected_tier: Astra and reply_path: native, plus advisor_flag: passed or advisor_flag: unavailable.
  • Mark fallback_kind: broken only when the selected bind or reply path fails. Record the selected tier, fallback reason, and reply path in the same evidence object.
  • Record first, recovery, and completion consults with changed evidence, validation, unresolved risks, and report-back status.
  • Write the evidence object to the session-controlled model-tier-run.json record described in advisor-tool.md.

04 同仓库更多 Skills

jl-cmd-projects
jl-cmd-projects/claude-dev-env

update

Fast-forwards a local repository's main branch to a remote's main after confirming the repo path and source remote through AskUserQuestion. Use when the user says '/update', 'update main', 'fast-forward main', 'sync main from origin', 'pull latest main into <path>', or 'bring main up to date'.

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

source-command-sr-loop

Converging cleanup loop: repeat /simplify until clean, then repeat /code-review --fix until clean

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

skill-builder

Skill lifecycle: classify, scaffold, write via the skill-writer-agent, self-audit, compose sub-skills, polish description triggers, enforce deterministic scripts. Triggers: build a skill, new skill workflow, improve this skill, optimize skill description, skill development lifecycle, skill modularity, skill composition, description trigger catalog, deterministic skill scripts.

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

session-tidy

Audit, clean, and consolidate session logs in the Obsidian vault. Fixes format drift, resolves orphaned next-steps, updates stale statuses, and generates project rollup summaries. Use when session logs feel cluttered or before starting a new project milestone. Triggers on '/session-tidy', 'tidy sessions', 'clean up session logs', 'session audit'.

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

session-log

Logs a session report as an HTML page, tracks vault context, extracts decisions, and outputs a /rename command. Use for /session-log, 'journal this session', 'log this work', 'session report', 'summarize/log/record this session', 'save session', 'capture session', or 'document what we did'.

★ 7
jl-cmd-projects
jl-cmd-projects/claude-dev-env

run-claude-dev-env

Build, install, run, and test the claude-dev-env installer. Use when asked to run claude-dev-env, install the Claude Code config into ~/.claude, drive the installer, smoke-test it against a sandbox, or run its test suite.

★ 7