handle-browser-automation-financial-site-blocks
Workflow for working around Chrome extension blocks on financial sites during data collection tasks
Best use case
handle-browser-automation-financial-site-blocks is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Workflow for working around Chrome extension blocks on financial sites during data collection tasks
Teams using handle-browser-automation-financial-site-blocks should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/handle-browser-automation-financial-site-blocks/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How handle-browser-automation-financial-site-blocks Compares
| Feature / Agent | handle-browser-automation-financial-site-blocks | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Workflow for working around Chrome extension blocks on financial sites during data collection tasks
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Handle Browser Automation Blocks on Financial Sites When browser automation tools are blocked on financial domains (Fidelity, brokerages, etc.) due to safety restrictions, use fallback data collection methods: screenshot capture for OCR/image reading, manual CSV export from the site's UI, copy-paste of table data into chat, or ask user to download files locally. Never attempt to bypass security blocks—instead, pivot to human-in-loop data transfer (screenshot, export, paste) and process the data after receipt.
Related Skills
taxact-browser-automation-patterns
Patterns for automating TaxAct Business online (Ionic SPA) via Chrome browser MCP tools — field interaction, navigation, shadow DOM handling
handle-session-overlay-blocking
Technique for dismissing overlay dialogs that freeze rendering and block form interaction in web automation
handle-popup-blocked-pdf-downloads
Recover from automation-blocking PDF popups by capturing page data and escalating to manual download
handle-pdf-download-popups-in-automation
Recover when PDF download buttons open inaccessible popups; fall back to capturing structured data instead
handle-freetaxusa-session-timeouts
Recover from FreeTaxUSA session timeout dialogs blocking form submission and navigation
handle-blocked-financial-sites-workaround
Workflow for accessing financial account data when browser automation is blocked on brokerage sites
handle-blocked-financial-sites-data-export
Workflow for extracting data from blocked financial sites when browser automation is restricted
financial-site-bypass-workflow
Workflow for accessing restricted financial sites when browser automation is blocked
financial-data-export-workflow
Structured process for exporting and analyzing multi-year brokerage transaction history when browser automation is blocked
workspace-hub-sync-concurrent-writer-blocks
Handle repository_sync cleanup when workspace-hub root is being mutated by concurrent Codex/Codex/Gemini sessions.
static-site-build-artifact-plan-review
Plan-review pattern for static-site fixes where the deployed artifact is generated from source files (e.g. sitemap/robots/static assets). Prevents review churn by separating durable regression checks from one-time migration verification and by validating built output, not just source files.
static-site-brand-identity-migration-tdd
Execute approved static-site brand identity/logo migrations with TDD across canonical content sources, generated deploy output, legacy checked-in HTML, existing stale tests, and build/docs contracts.