AF scrapfly-alerting
Threshold-based alerting on Scrapfly account metrics. Wire up rules like "alert me when scrape success rate drops below 95% for 10 minutes" and receive notifications via email, webhook, or in-app. Use when the user asks to "set up an alert", "monitor my scrape success rate", "tell me when my scrapes start failing", "alert on ASP block rate", "watch a specific domain", or any task involving the Scrapfly alerting product. Covers the three call paths: REST API, MCP `alert_*` tools, and the `scrapfly alert` CLI subcommand. Enterprise plan feature; GATED behind the ALERTING feature flag on customer accounts.
Threshold-based alerting on Scrapfly account metrics.
As a process F 49/100 · Will not run — References files that are not bundled: ../scrapfly-cli/, ../scrapfly-agent-rules/, ../scrapfly-scraper/
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../scrapfly-cli/ - warning
missing-refreference to a missing file: ../scrapfly-agent-rules/ - warning
missing-refreference to a missing file: ../scrapfly-scraper/
Process rating: all ten parameters 49/100
- 0Tools and files. 3 referenced file(s) missing: ../scrapfly-cli/, ../scrapfly-agent-rules/, ../scrapfly-scraper/
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 13 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 45 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3138 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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 6 example trigger phrases
- +3Description length 610: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.