AC helios-kanban-remote
Remote control Helios Kanban (helios-kanban) via REST API — list/create/update tasks, start/stop coding agents, follow-up, check status, handle approvals. Use when the user wants to control kanban from phone/chat, mentions Helios Kanban / helios-kanban / vibe-kanban remotely, or asks to create tasks, start agents, or check progress on a running instance. If the skill is not installed yet, read and follow INSTALL.md to self-install from GitHub first.
Remote control Helios Kanban (helios-kanban) via REST API — list/create/update tasks, start/stop coding agents, follow-up, check status, handle approvals.
As a process C 64/100 · Has gaps — weak spots: failures and branches, consistency, running it twice
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 64/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 15 mutating operations with no state check
- 40Consistency. Frontmatter name (helios-kanban-remote) differs from the folder (helios-kanban-skills)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 22 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1470 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (10 tags): a typed call is more reliable
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)
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 453: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 22 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.