BF lygo-ollama-army
Local Ollama multi-role army (ClawHub-safe). In-process threaded daemons for hb-light, draft-simple, memory-triage, classify, champion-chat only. Queue JSON under ollama_queue/. localhost Ollama only. No planting, no social outbound, no public HTTPS probes, no desktop installers, no subprocess shell. FULL operator stack (optional) on SkillHub if running full LYGO. Install clawhub:@deepseekoracle/lygo-ollama-army.
Local Ollama multi-role army (ClawHub-safe).
As a process F 30/100 · Will not run — References files that are not bundled: references/SECURITY.md, references/SKILLSPECTOR_AUDIT.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 0. 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") - warning
missing-refreference to a missing file: references/SECURITY.md - warning
missing-refreference to a missing file: references/SKILLSPECTOR_AUDIT.md
Process rating: all ten parameters 30/100
- 0Tools and files. 2 referenced file(s) missing: references/SECURITY.md, references/SKILLSPECTOR_AUDIT.md
- 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. 1 mutating operations with no state check
- 85Steps. 7 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 557 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +2Single-language instructions
- +3Description length 416: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.