AB scrape-creator-profile
Scrape and extract structured data from creator profiles across platforms such as YouTube, Instagram, TikTok, Twitter/X, LinkedIn, Twitch, and personal websites. Use this skill whenever the user asks to look up, fetch, analyze, or collect data about a content creator, influencer, or public profile — even if they don't say "scrape". Triggers: "get info on this creator", "pull their profile", "what's their follower count", "scrape this creator page", "summarize this influencer", "fetch creator stats", "analyze this YouTube channel", "get TikTok profile data".
As a process B 66/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
exfil-secret-in-urlreferences/apify-actors.md:12Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)"https://api.apify.com/v2/acts/{ACTOR_ID}/run-sync-get-dataset-items?token=…" \placeholder
Files scanned: 8. 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 66/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
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 45 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2183 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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
- +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
- +5Description quotes 9 example trigger phrases
- +3Description length 563: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.