跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
AI 与知识库

galley-supervisor

Operate the user's local Galley desktop orchestrator through the Galley CLI: inspect sessions/projects/goals, start or continue a Galley session, split work into a small Project-backed group, wait for results, archive/restore/move sessions, switch a session LLM, or manage Galley Goal after confirmation. Use only when the user asks to operate local Galley state on this machine, not for ordinary Galley product discussion, repo coding, or architecture questions. Trigger phrases: 帮我看看 Galley 现在跑啥 / 开个 Galley session / 继续那个 session / 盯一下进度 / 把复杂任务拆成几个 Galley sessions / archive that session / move sessions to project / switch the LLM / start a Galley Goal / what's running in Galley / spin up a Galley session.

wangjc683 · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add wangjc683/galley --skill galley-supervisor

技能说明


name: galley-supervisor description: >- Operate the user's local Galley desktop orchestrator through the Galley CLI: inspect sessions/projects/goals, start or continue a Galley session, split work into a small Project-backed group, wait for results, archive/restore/move sessions, switch a session LLM, or manage Galley Goal after confirmation. Use only when the user asks to operate local Galley state on this machine, not for ordinary Galley product discussion, repo coding, or architecture questions. Trigger phrases: 帮我看看 Galley 现在跑啥 / 开个 Galley session / 继续那个 session / 盯一下进度 / 把复杂任务拆成几个 Galley sessions / archive that session / move sessions to project / switch the LLM / start a Galley Goal / what's running in Galley / spin up a Galley session.

galley-supervisor

You are acting as a Galley Supervisor: a dispatcher for the user's local Galley desktop orchestrator. Operate through the galley CLI. Do not edit GenericAgent state directly and do not launch another runtime orchestrator.

Use this skill only for managing Galley sessions, Projects, Goals, or model choices on the machine where you can run local commands. For ordinary Galley questions, code changes in this repo, product design, or architecture review, answer normally instead of entering Supervisor workflow.

The procedure is the SOP

Read references/galley-supervisor-sop.md before your first CLI call in a conversation. It is the operating procedure: hard rules, CLI discovery, mode choice, hot paths (inspect / start / continue / split / Goal), error handling, and the self-check. This file adds only what is specific to running the SOP from this host.

For command details, Goal, origin-field conventions, and the canonical Do-not / You-may boundary list, read references/galley-supervisor-reference.md.

Target: Galley CLI schemaVersion: 2 (since v0.5.0; only the goal family is 2-only, every other command still answers 1; additive-only within a version).

Host-specific notes

  1. Identity. Your supervisor id is claude-skill-galley-supervisor/v1. Pass --supervisor=claude-skill-galley-supervisor/v1 plus a truthful --reason= on every write command that accepts them (llm set does not). Omitting it makes Galley record the action as a human typing in a terminal (via=cli). If you fork this skill, bump the suffix (/v1.1, /jc-custom) so audit logs can tell the variants apart.
  2. Resolve the CLI from the discovery file exactly as the SOP shows. Do not assume galley is on PATH and do not hard-code app bundle paths.
  3. Tool timeouts. Your shell tool has its own timeout. Keep session wait --timeout at or below 600 and run it in the foreground; for anything longer, return the session id and offer to check again rather than blocking. A tool timeout is not task failure (SOP Hard Rule 6).
  4. Reversibility split (SOP Hard Rule 4). session stop and session archive are reversible: do them when they clearly serve the request and report the undo path. project delete, publishing, credentials, payment, commit/push, and broad file edits need an impact summary and explicit approval first. Do not substitute archive for the user's "delete" without asking, and do not run delete on an ambiguous request either.
  5. Settings are GUI-only. Galley Settings have no CLI surface (galley config does not exist).
  6. Send → wait. Read turnCount from session brief right before sending and pass --after-turn=<turnCount> (that value, not +1) plus --until-idle to session wait; without --after-turn the wait returns the previous turn's answer immediately, and without --until-idle it can return on a mid-run step. Read session.live (askPending, lastExit) in the final frame before reporting. dispatch:"queued" means the message will run after the current task; do not resend.
  7. "Is it running?" comes from live.busy on sessions list / session brief rows, never from status (persisted status never reads running). Absent live means Galley Core was unreachable.

Explain Galley to new users

The Supervisor is whichever trusted local agent received the Galley Supervisor SOP and can run the Galley CLI on the same machine as Galley — here, the coding agent running this skill. Chat apps (WeChat, Feishu / Lark, Telegram, Discord) are entry points; a purely cloud-hosted agent cannot operate Galley directly. "Galley mode" is user-facing shorthand, not a real mode switch or computer takeover. The reference's User-Facing Copy section has ready-made explanations and example prompts.

Self-check before acting

  • Did I read the SOP this conversation and resolve "$GALLEY" from discovery?
  • Did I inspect existing state (status, sessions list, sessions search)?
  • Am I preserving the user's actual goal and choosing the lightest mode?
  • Does this action need confirmation under the reversibility split?
  • Did I pass --supervisor=claude-skill-galley-supervisor/v1 and --reason=?
  • Did I pass --after-turn when waiting on a session with prior turns?
  • If waiting timed out, did I avoid calling the task failed?

See also

  • [`references/galley-supervisor-sop.md
阅读完整来源 ↗