BB Threads Scraper
This skill should be used when the user asks to "scrape Threads posts", "get Threads data", "extract Threads content", "search Threads", "monitor Threads hashtags", "analyze Threads engagement", "get posts from a Threads user", or needs to collect data from Meta Threads.
As a process B 69/100 · Nearly there — weak spots: consistency, progress reporting
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:126Credential used in a network call (verify the destination is the intended service)STATUS=$(curl -s "https://api.apify.com/v2/actor-runs/$RUN_ID?token=…" \
-
medium Exfiltration
net-credential-useSKILL.md:134Credential used in a network call (verify the destination is the intended service)curl -s "https://api.apify.com/v2/datasets/$DATASET_ID/items?token=…" | jq '.'
-
low Exfiltration
exfil-secret-in-urlSKILL.md:117Credential 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/futurizerush~meta-threads-scraper/runs?token=…" \
placeholder -
low Exfiltration
exfil-secret-in-urlSKILL.md:126Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)STATUS=$(curl -s "https://api.apify.com/v2/actor-runs/$RUN_ID?token=…" \
placeholder -
low Exfiltration
exfil-secret-in-urlSKILL.md:134Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)curl -s "https://api.apify.com/v2/datasets/$DATASET_ID/items?token=…" | jq '.'
placeholder
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 69/100
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (Threads Scraper) differs from the folder (apify-threads-scraper)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 15 steps
- 100Execution cost. Instruction body is 1622 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)
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 271: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 15 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.