BD ramalama-cli
Run and interact with AI agents.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationInfrastructureAI and agentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenreferences/models.md:22High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| `Qwen…uct` | 30B (A3B active MoE) | Best-quality local coding assistance | Top recommendation when hardware permits. | `rlcr://qwen…uct` ; `hf://unsloth/Qwen3
table -
low Secrets in code
secret-high-entropy-tokenreferences/models.md:24High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| `Deep…uct` | 16B (2.4B active MoE) | Complex repo reasoning on high-end local systems | Use the Lite variant for local workflows; the full 236B variant is not a practical loca
table
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 85Steps. 30 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 953 tokens
- low The response is described with custom markup (9 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)
- +3Description length 32: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +4Structure: 14 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.
External checks
ClawHub: clean
This skill appears to be a straightforward guide for using the Ramalama CLI, with one practical caution around local API serving exposure.
LLM: benign (medium) · VirusTotal: benign · 28 May 2026