AC linkedin-email-phone-apify
Use this skill when the user needs LinkedIn contact enrichment by URLs with both phone and email lookup via Apify actors (phones: X95BXRaFOqZ7rzjxM, emails: q3wko0Sbx6ZAAB2xf), including optional branches and merged output.
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenREADME.md:4High-entropy token-like string (may be an id, hash or a credential)[](https://console.apify.com/actors/X95B…jxM)
-
low Secrets in code
secret-high-entropy-tokenREADME.md:5High-entropy token-like string (may be an id, hash or a credential)[](https://console.apify.com/actors/q3wk…2xf)
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Use this skill when the user needs LinkedIn contact enrichment by … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "required_env_vars" - note
frontmatter-keyunknown frontmatter key "required-env-vars" - note
frontmatter-keyunknown frontmatter key "primary_credential" - note
frontmatter-keyunknown frontmatter key "primary-credential"
Process rating: all ten parameters 59/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
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 516 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
- +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 223: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.
External checks
ClawHub: clean
This skill does what it advertises: it sends user-provided LinkedIn URLs to disclosed Apify actors to retrieve email and phone contact data, with privacy and compliance caveats.
LLM: benign (high) · VirusTotal: benign · 28 May 2026