More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Web Scrape Block Triage

    1

    Diagnose why your own scraper is blocked and fix it within the rules.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Web Scrape Block Triage

    Web Scrape Block Triage

    Example session with this skill installed

    Apply the skill to this case: A price-check job that ran hourly began returning empty pages on one category, while other categories still worked.

    • Read your context and instructions
    • Compiled the web scrape block

    Situation: A price-check job that ran hourly began returning empty pages on one category, while other categories still worked. Evidence: Logs showed 200 responses with an empty results block, not 403 or 429, and only for that category. A single slow manual request returned the same empty block, so rate was ruled out. The category page had been redesigned and the results container renamed. Decision: Fix the request parsing for the new layout, and add a check that fails loudly if the results block is empty instead of reporting zero prices. Outcome: The category recovered fully, and the empty-result guard later caught a second redesign within one run instead of silently publishing wrong prices.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A block is a symptom with several possible causes: a changed page, a rate problem, a missing header, an expired session, a robots or terms change, or a genuine denial of access. Guessing leads to aggressive retries that make the block worse. This skill reads the block evidence first, classifies it, and prescribes only fixes that respect the provider: slower pacing, fixing your request, using an official feed or API, or stopping. This skill gives you a counted diagnosis, a decision table, a fill-in template, a checklist, and a scoring rubric, plus a runnable script (block_triage.py) that Classifies log lines into rate, access, layout, or unknown blocks and writes a triage report with a stop-or-fix recommendation, with access-denied taking precedence over rate. It is built for the bottleneck moment: when the usual quick fix has already failed, or when a silent failure is worse than a loud one. Follow the protocol in order, record numbers rather than impressions, and use the quality gate before you call the work done.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.

    Results depend on the quality of your evidence set: an incomplete log, missing status codes, or a block whose terms you have not checked will limit the diagnosis, and the skill says so rather than filling gaps with guesses. The script is a helper for counting and reporting; it does not replace judgement about safety, permission, or whether a fix is correct. Thresholds are starting points to adapt to your context, not universal constants.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 23 days ago

    Permissions

    Terminal / Shell
    Write Files
    Network Access
    Listed23 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    No. Slowing down fixes rate problems only. Layout and access problems need a parser fix, an official source, or a stop decision.

    Use only paths you are permitted to collect, at a respectful pace, with a clear identity, and stop if access is denied.

    Pause on the first block, preserve evidence, and never retry in a loop. One slow test request classifies the problem; a sweep deepens it.

    New in Testing & Debugging