Use Case
Blocked Page Fallback isn't just for solo use β teams can share skills and build consistent AI workflows across the organization. Recover when a web page is thin, blocked, JS-heavy, region-limited, or fetch-incompatible by switching to lawful fallback paths instead of stopping early. This guide covers how to deploy Blocked Page Fallback for your team, standardize prompts, and create shared workflows that everyone can use.
Install Blocked Page Fallback in your project directory: .claude/skills/blocked-page-fallback/
Commit the skill folder to your repository so the whole team has access
Document your team's standard prompts in a shared README
Use Blocked Page Fallback in code reviews, standups, and planning sessions
Iterate: collect feedback from the team and refine your prompts
Copy these prompts and use them with your AI agent after installing Blocked Page Fallback
How can my team use Blocked Page Fallback together?
Set up Blocked Page Fallback for our project so everyone can use it
Create a shared workflow using Blocked Page Fallback for our team
Select your agent
Option 1: Install via CLI (recommended)
Recommended (no pre-install needed)
npx clawhub@latest --dir ~/.claude/skills install blocked-page-fallbackOr via clawhub CLI (if already installed)
clawhub --dir ~/.claude/skills install blocked-page-fallbackβ οΈ Requires Node.js 18+. No Node? Use Option 2 below to download the ZIP instead. Install Node.js β
Option 2: Manual install (no Node required)
Download the ZIP, extract it, and place the folder at the path below. Restart your agent to activate.
Install path
~/.claude/skills/blocked-page-fallback/π‘Extract and place the folder at the path above, then restart your agent.