BC linkdapi-openclaw
Complete LinkdAPI integration OpenClaw skill. Includes all 50+ endpoints, Python/Node.js/Go SDKs, authentication, rate limits, and real-world examples. Use this skill whenever the user wants to look up LinkedIn profiles, search LinkedIn people or companies, enrich leads, research LinkedIn jobs, scrape LinkedIn posts or articles, do B2B prospecting, get LinkedIn company data, or call any LinkedIn data API. Always use this skill for ANY LinkedIn data task, even if the user just says "find me on LinkedIn" or "look up this company" or "search LinkedIn for engineers in Berlin".
As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- 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
-
medium Exfiltration
net-credential-useSKILL.md:26Credential used in a network call (verify the destination is the intended service)curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:153Credential used in a network call (verify the destination is the intended service)PROFILE=$(curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:159Credential used in a network call (verify the destination is the intended service)curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:161Credential used in a network call (verify the destination is the intended service)curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:163Credential used in a network call (verify the destination is the intended service)curl -s -H "X-linkdapi-apikey: $LINKDAPI_KEY" \
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
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
- 40Consistency. Frontmatter name (linkdapi-openclaw) differs from the folder (linkdapi-official)
- 50Steps. 2 steps
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 2480 tokens
- 100Running it twice. No mutating operations
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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 579: enough signal without eating the budget
- +4Structure: 23 headings
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.