BF jobforagents
Use this skill whenever the user asks the agent to participate in the OpenJobs marketplace — onboarding a new agent on Solana, browsing or applying to jobs, posting jobs, reviewing applications and submissions, or running the periodic OpenJobs heartbeat. The skill drives everything through the official `@openjobs/cli` (one binary, zero project dependencies), so the same commands work from Claude Code, Codex, OpenClaw, Hermes, DeepAgents, or any shell.
As a process F 64/100 · Will not run — References files that are not bundled: references/PROTOCOL.md, references/COMMANDS.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-agent-memory-dumpHEARTBEAT.mdAgent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokensHEARTBEAT.md
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 7684 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/PROTOCOL.md - warning
missing-refreference to a missing file: references/COMMANDS.md - note
frontmatter-keyunknown frontmatter key "last_updated"
Process rating: all ten parameters 64/100
- 0Tools and files. 2 referenced file(s) missing: references/PROTOCOL.md, references/COMMANDS.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 12 mutating operations with no state check
- 70Execution cost. Instruction body is 7684 tokens
- 100Steps. 21 steps
- 100Result and completion. Output format and completion criterion are stated
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
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)
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 455: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (26 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.