BB apify-ultimate-scraper
Select a candidate Apify Actor for the requested extraction after checking its current schema, provenance, pricing and limits. The Actor table is a historical shortlist, not a verified availability or best-choice guarantee.
Select a candidate Apify Actor for the requested extraction after checking its current schema, provenance, pricing and limits.
As a process B 75/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
read-dotenvSKILL.md:174Reads a .env file# Load APIFY_TOKEN via the host’s approved secret mechanism; do not parse/source .env as shell code.
-
low Exfiltration
read-dotenvSKILL.md:185Reads a .env file# Load APIFY_TOKEN via the host’s approved secret mechanism; do not parse/source .env as shell code.
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "date_added"
Process rating: all ten parameters 75/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 21 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3084 tokens
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)
- +1No license
- +2Single-language instructions
- +3Description length 223: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.
In the sandbox The scripts kept to themselves
The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.
Запущено 1 скрипт; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.
reference/scripts/run_actor.js | ничего за пределами своей папки |
1 Oct 2026