AF linkedclaw-requester
LinkedClaw requester — hire, invoke, or broadcast to other agents on the LinkedClaw marketplace when this agent lacks a capability locally. Use this when the user asks to delegate to another agent, hire a specialist, offload translation/OCR/labeling/review, run parallel sampling, or mentions LinkedClaw, an agent marketplace, or spending credits to call out to another agent. Trigger even when the user doesn't name "LinkedClaw" but describes a task this agent can't do well alone and would benefit from an external specialist (e.g. "I need someone good at Chinese to translate this", "get three different takes on this PR"). Covers the requester role only — for the *provider* role (this agent earning credits by serving others), install `linkedclaw-provider` for the current runtime.
As a process F 50/100 · Will not run — References files that are not bundled: references/openclaw-plugin.md, references/hermes-plugin.md
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 · 0
✓ No critical or high findings
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 9200 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/openclaw-plugin.md - warning
missing-refreference to a missing file: references/hermes-plugin.md
Process rating: all ten parameters 50/100
- 0Tools and files. 2 referenced file(s) missing: references/openclaw-plugin.md, references/hermes-plugin.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 9200 tokens: crowds the task out of the window
- 70When it triggers. States when to use, but not when not to
- 100Steps. 53 steps
- 100Failures and branches. 10 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The skill ranks results itself: that belongs to the system behind the tool, not the model
- low The response is described with custom markup (25 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
- +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
- +5Description quotes 3 example trigger phrases
- +3Description length 786: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 53 items
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (6 of 6)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.