Gemini 助手
- 作者仓库星标 0
- 作者更新于 实时读取
- 作者仓库 skills-registry
- 领域
- 通用
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @tomevault-io · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 底层运行要求
- Node.js
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
---
name: gemini-cli-runtime
description: Internal helper contract for calling the polycli companion runtime for Gemini from Claude Code U…
category: 通用
runtime: Node.js
---
# gemini-cli-runtime 输出预览
## PART A: 任务判断
- 适用问题：通用任务拆解、检查和交付。
- 输入要求：目标材料、限制条件、期望输出和验收方式。
- 证据边界：围绕“Primary helper / Commands available to the agent / Latency expectations”读取原文规则，不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断：确认你的需求是否属于通用任务拆解、检查和交付，并标出输入、限制和预期结果。
- **02** 执行计划：优先按“Primary helper / Commands available to the agent / Latency expectations”拆成步骤，说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果：给出可复制的命令、文件改动、检查清单或内容草稿，并说明如何继续迭代。
- **04** 风险边界：结合 读取文件、写入/修改文件、执行终端命令、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件、执行终端命令；主要在本地完成；通常不需要额外 API Key。
- 先小样例验证，再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。原文出现了 `/polycli` 这类斜杠命令；如果你的 Agent 支持命令触发，优先用命令开场，再补充目标和边界。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是：读取文件、写入/修改文件、执行终端命令。
先用一个小任务确认它会围绕“Primary helper / Commands available to the agent / Latency expectations”工作；涉及文件或命令时，先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作；如果输出泛泛而谈，就补充输入、边界和验收标准后重跑。
---
name: gemini-cli-runtime
description: Internal helper contract for calling the polycli companion runtime for Gemini from Claude Code U…
category: 通用
source: tomevault-io/skills-registry
---
# gemini-cli-runtime
## 什么时候使用
- 把通用方向的常用动作沉淀成 Agent 可调用的技能 适合处理通用任务拆解、检查、交付和复盘，核心价值是把输入、判断、执行、验证和交付边界固定下来，避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤；通常不需要额外…
- 面向通用任务拆解、检查和交付，优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Primary helper / Commands available to the agent / Latency expectations」组织步骤，不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令；主要在本地完成；通常不需要额外 API Key。
- 先跑小样例，确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown，不编造命令、平台或依赖。作者原文负责流程事实；仓库文件负责来源和命令；流狐只补充适用场景、限制和质量判断。
skill "gemini-cli-runtime" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Primary helper / Commands available to the agent / Latency expectations
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> Node.js | 读取文件、写入/修改文件、执行终端命令 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
}Gemini CLI Runtime Contract
This skill defines how polycli:polycli-provider-agent (the subagent) interacts with the
polycli companion script for Gemini. Only invoked from within polycli:polycli-provider-agent.
Primary helper
node "${CLAUDE_PLUGIN_ROOT}/scripts/polycli-companion.bundle.mjs" rescue --provider gemini "<prompt>" --jsonCommands available to the agent
The provider-agent forwards whatever subcommand the caller supplied. Use rescue for multi-step agent work and ask for one-shot questions; the rest are slash-command-driven user flows.
| Command | Used by agent? | Purpose |
|---|---|---|
rescue |
Yes | Multi-step agent task (600s base, 1200s for deep-reasoning models — see Latency expectations) |
ask |
Yes | One-shot question (120s base, 240s for deep-reasoning models — see Latency expectations) |
setup |
No | User checks installation |
health |
No | User runs end-to-end probe |
review |
No | User triggers code review |
adversarial-review |
No | User triggers adversarial review |
status |
No | User checks job status |
result |
No | User fetches completed output |
cancel |
No | User cancels background job |
timing |
No | User inspects timing history |
Resumable thread state is exposed via the --resume-last flag, not a separate subcommand.
Latency expectations
Only deep-reasoning Gemini variants (Pro / Thinking series) routinely spend 30s–several minutes silently reasoning before emitting visible text. Flash and other non-reasoning variants typically stream within seconds. This is upstream behavior, not a polycli stall.
To absorb the reasoning latency without inflating other models' budgets, the companion applies a model-scoped multiplier:
PROVIDER_TIMEOUT_MULTIPLIERS = {
gemini: { "gemini-3.1-pro-preview": 2 },
opencode: { "kimi-for-coding/k2p6": 2 }, // also a code-reasoning model
}(The opencode entry was added 2026-05-02 after a HumanEval/130 Tribonacci probe hit the 120s ask ceiling; the same pattern can be extended to any other reasoning model id.)
Resolution rules (per resolveTimeoutMs in polycli-companion.mjs):
--model gemini-3.1-pro-preview→ ×2 budget (the explicit reasoning case)- No
--model, cached upstream-default model isgemini-3.1-pro-preview→ ×2 budget (the common case today) --model <some-flash-or-other>→ ×1 (caller explicitly chose a non-reasoning model)- Unknown / cache empty / non-gemini provider → ×1
Effective ceilings when the multiplier applies:
| kind | base | gemini reasoning |
|---|---|---|
ask |
120s | 240s |
rescue |
600s | 1200s |
review |
300s | 600s |
adversarial-review |
300s | 600s |
health keeps the universal 60s budget regardless of model — gemini's health prompt is sentinel-only and does not exercise reasoning.
If you cannot estimate how long a gemini prompt will take (e.g. open-ended diagnosis on a large diff), prefer --background and poll with /polycli:status / /polycli:result instead of relying on the foreground timeout. The background worker reuses the same execution.timeout (so gemini still gets the model-resolved budget), but the calling shell is freed immediately and the user can decide how long to wait.
When upstream releases a new reasoning-capable Gemini model id, add it to PROVIDER_TIMEOUT_MULTIPLIERS.gemini. Do not blanket-multiply the whole provider — that would over-budget Flash users.
Routing controls
These are CLI flags, not prompt text:
--background— run async, return job ID immediately--write— allow Gemini to modify files (maps to--approval-mode auto_edit)--resume-last— continue previous Gemini thread--fresh— start new thread (ignore previous)--model <model>— override the default model--effort <low|medium|high>— reasoning effort level--prompt-file <path>— read prompt from file instead of positional args--json— always use this for machine-readable output
Safety rules
- Preserve prompt text as-is. Only reshape via
gemini-promptingskill. - Never inspect the repo from the agent. Claude does that.
- Return stdout exactly. No independent analysis.
- Return nothing if invocation fails (let Claude handle the error).
Source: bbingz/polycli — distributed by TomeVault.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核