BD orca-control
Manage, orchestrate, inspect, and automate the Orca IDE and Multi-Agent Runtime Server — projects, worktrees, supervised workers, interactive terminals, decision gates, accounts, and automations.
Manage, orchestrate, inspect, and automate the Orca IDE and Multi-Agent Runtime Server — projects, worktrees, supervised workers, interactive terminals…
As a process D 40/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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
-
high Exfiltration
exfil-read-secret-filesreferences/github_integration_and_preflight.md:23Reads credential / secret filescp /root/.config/gh/hosts.yml /home/orca/.config/gh/hosts.yml
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 195 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "credits" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 40/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
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 26 steps
- 100Execution cost. Instruction body is 2256 tokens
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 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)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -215 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 195: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (13 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.