BC opencode-remote
通过 HTTP API 远程操作 OpenCode 服务器。用于管理远程 OpenCode 实例的会话、监控状态和执行任务。 核心功能: 1. 管理多个"主session"(每个有独立的四词短名、endpoint、任务) 2. 向 session 发送消息(默认不指定agent,延续之前使用) 3. 自动监控:发送消息后自动开始每5分钟进度汇报 4. 创建 session 时询问用户选择 agent 用户需要提供: - OpenCode 服务器基础 URL(如 http://host:port) - 主session的四词短名(如 "csbx", "kumo", "hetc")
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:33High-entropy token-like string (may be an id, hash or a credential)| csbx | acf3…096 | ses_…Dr7 | OpenCode Web 集成 |
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:34High-entropy token-like string (may be an id, hash or a credential)| kumo | acf3…004 | ses_…3q8 | k8s macOS 部署 |
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:35High-entropy token-like string (may be an id, hash or a credential)| hetc | acf3…457 | ses_…iRT | HETC 项目开发 |
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1357 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -32 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 294: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (20 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.