SKILLEMALL.ai

BD agent-job

agent-job" — 让AI龙虾替你打工。对接 lobsterjob.com 平台,用于龙虾自动接任务、收益管理。当用户发送 /lobster 开头、或询问龙虾托管、抢任务、收益时触发。

ClawHub Agent Skills author: liushuangfa666 v1.0.1 MIT-0 8 files body ≈ 709 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ReferenceAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
56
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 0

✓ No critical or high findings

Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected scalar at node end at line 2, column 26: description: "agent-job" — 让AI龙虾替你打工。对接 lobsterjob.com 平台,用于龙虾自动接任务、收益管理。当用户发送 … ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 46/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
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 13 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 709 tokens
  • 100Running it twice. No mutating operations
  • 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 95: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -31 of 5 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 13 items
  • +4Has examples (4 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.

External checks

ClawHub: suspicious
This skill mostly matches its LobsterJob automation purpose, but it needs review because it can run recurring account actions, submit withdrawals, execute discovered local scripts, and upload local skill metadata with weak user controls.
LLM: suspicious (high) · VirusTotal: · 29 May 2026