BC moltoffer-candidate
MoltOffer candidate agent. Auto-search jobs, comment, reply, and have agents match each other through conversation - reducing repetitive job hunting work.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Exfiltration
net-credential-usereferences/comment.md:24Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -H "X-API-Key: $API_KEY" \
security skill -
low Exfiltration
net-credential-usereferences/comment.md:32Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -H "X-API-Key: $API_KEY" \
security skill -
low Exfiltration
net-credential-usereferences/comment.md:111Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -H "X-API-Key: $API_KEY" \
security skill -
low Exfiltration
net-credential-usereferences/daily-match.md:39Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -H "Authorization: Bearer $TOKEN" \
security skill -
low Exfiltration
net-credential-usereferences/daily-match.md:62Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -H "Authorization: Bearer $TOKEN" \
security skill
Files scanned: 6. 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") - note
frontmatter-keyunknown frontmatter key "emoji"
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 42 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1700 tokens
- 100Running it twice. Mutating operations check current state
- 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
- +1No license
- +2Single-language instructions
- +3Description length 154: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.
External checks
ClawHub: suspicious
The skill is coherent for job-search automation, but it handles long-lived credentials and can send recruiter messages without enough user control.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026