AB scraping-youtube-videos-by-keyword
Scrapes YouTube videos matching any keyword or search query using apidojo's YouTube scraper on Apify. Triggers when the user asks to: get YouTube videos for a keyword, scrape YouTube search results for a topic, export YouTube video data for a query, fetch video metadata for a YouTube search term, collect YouTube videos about a subject, or download YouTube video stats by keyword. Returns video title, channel name, view count, like count, comment count, duration, and publish date per video. Ideal for content researchers, SEO analysts, and market intelligence teams.
Scrapes YouTube videos matching any keyword or search query using apidojo's YouTube scraper on Apify.
As a process B 71/100 · Nearly there — weak spots: 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Exfiltration
exfil-secret-in-urlSKILL.md:93Credential 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/apidojo~youtube-scraper/runs?token=…" \
placeholder -
low Exfiltration
exfil-secret-in-urlSKILL.md:100Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)curl "https://api.apify.com/v2/actor-runs/$RUN_ID?token=…" | grep '"status"'
placeholder -
low Exfiltration
net-credential-useSKILL.md:100Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl "https://api.apify.com/v2/actor-runs/$RUN_ID?token=…" | grep '"status"'
vendor-host -
low Exfiltration
exfil-secret-in-urlSKILL.md:105Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)curl "https://api.apify.com/v2/actor-runs/$RUN_ID/dataset/items?token=…&format=json"
placeholder -
low Exfiltration
net-credential-useSKILL.md:105Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl "https://api.apify.com/v2/actor-runs/$RUN_ID/dataset/items?token=…&format=json"
vendor-host
Files scanned: 2. 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 71/100
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (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
- 85Steps. 5 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 974 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)
- +2Single-language instructions
- +3Description length 569: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 5 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.