AC OpenCode-CLI-Controller
A powerful skill to control Open Code CLI via a local web server API. Allows executing commands, managing sessions, and automating code generation remotely in the local network.
A powerful skill to control Open Code CLI via a local web server API.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
IntegrationInfrastructureAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Dangerous commands
cmd-background-processscripts/start_server.sh:34Starts a background / autostarted processnohup script -q -c "$OPENCODE_BIN web --port $PORT" /dev/null > "$LOG_FILE" 2>&1 &
Files scanned: 20. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "emoji"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 16 mutating operations with no state check
- 40Consistency. Frontmatter name (OpenCode-CLI-Controller) differs from the folder (opencode-api-control-skill)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 50 steps, 3 vague phrases
- 100Execution cost. Instruction body is 3940 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 21 top-level sections: this looks like several domains in one skill
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
- -217 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 177: enough signal without eating the budget
- +4Structure: 41 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (32 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 12 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.