handle-blocked-financial-sites-workaround
Workflow for accessing financial account data when browser automation is blocked on brokerage sites
Best use case
handle-blocked-financial-sites-workaround is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Workflow for accessing financial account data when browser automation is blocked on brokerage sites
Teams using handle-blocked-financial-sites-workaround 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-blocked-financial-sites-workaround/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How handle-blocked-financial-sites-workaround Compares
| Feature / Agent | handle-blocked-financial-sites-workaround | 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 accessing financial account data when browser automation is blocked on brokerage sites
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.
SKILL.md Source
# Handle Blocked Financial Sites Workaround When browser automation tools are blocked on financial/brokerage sites (by design for security), use data export as the primary retrieval method. Request the user to manually export CSV files from the brokerage platform (transactions, positions, gains/losses) and save them locally or in a shared directory. If manual export isn't feasible, ask for a screenshot or direct copy-paste of table data. Never attempt to circumvent security blocks on sensitive financial sites—the restrictions prevent accidental trade execution or credential exposure.
Related Skills
tax-pdf-download-workaround
Handle FreeTaxUSA PDF download popups that block automation by capturing structured data and manual download workflow
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-browser-automation-financial-site-blocks
Workflow for working around Chrome extension blocks on financial sites during data collection tasks
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
blocked-branch-preserve-tag-cleanup
Safely clean stale local branches that cannot be merged by preserving them with local tags before deletion
financial-analysis
Domain expertise for financial markets, investment analysis, corporate finance, risk management, and energy finance.
delegate-task-4-lane-workaround
Work around delegate_task batch concurrency cap when the user wants four parallel review lanes.