blocked-site-diagnostics

Classify blocked-access pages and collect visible and console evidence.

Updated May 21, 2026
One-click install
npx skills add https://github.com/samlaggz/hermes-agent-sam --skill blocked-site-diagnostics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blocked-site-diagnostics
Source: https://github.com/samlaggz/hermes-agent-sam/tree/main/backup/skills/dogfood/blocked-site-diagnostics
Command: npx skills add https://github.com/samlaggz/hermes-agent-sam --skill blocked-site-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnose blocked-access pages without attempting bypass, collecting visible evidence and runtime clues to determine the block type and guide remediation.

Core Features & Use Cases

  • Evidence capture: snapshot visible content and log console clues to classify blocks as CAPTCHA, 403, 429, or auth-related.
  • Structured remediation: provide actionable next steps such as official API usage, allowlisting, or a visible manual verification path.
  • Safe, non-bypass workflow: emphasize diagnostics and evidence gathering over evasion, suitable for debugging automation in compliant environments.

Quick Start

Observe a blocked page and run this diagnostic to classify the block and collect evidence for remediation.

Frequently Asked Questions about blocked-site-diagnostics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a 403 or 429 blocked site error in my browser?

To diagnose a 403 or 429 blocked site error, you classify the block type by capturing visible page content and console log clues to guide remediation without bypassing access controls.

What is the best way to classify CAPTCHA challenges and auth blocks during automation?

Classifying CAPTCHA challenges and auth blocks involves snapshotting visible content and gathering runtime clues from console logs to identify the block type and determine compliant remediation steps.

How do I collect evidence from a blocked access page without attempting a bypass?

Collecting evidence from a blocked access page safely requires snapshotting visible content and logging console clues to classify blocks like 403, 429, or auth failures for structured remediation.

Can I diagnose blocked pages in non-GUI browser automation environments?

Yes, you can diagnose blocked pages across GUI or non-GUI browser paths by capturing visible content and runtime console logs to classify blocks and guide subsequent remediation actions.

What remediation steps should I take after identifying a 429 block type?

After identifying a 429 block type, structured remediation involves following actionable next steps such as using official APIs, allowlisting IPs, or completing manual verification paths.

Do I need external dependencies to run browser diagnostics for blocked sessions?

No, running browser diagnostics for blocked sessions requires no external runtime beyond the local browser context, relying entirely on in-skill guidelines and visible evidence collection.