financial-site-bypass-workflow
Workflow for accessing restricted financial sites when browser automation is blocked
Best use case
financial-site-bypass-workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Workflow for accessing restricted financial sites when browser automation is blocked
Teams using financial-site-bypass-workflow 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/financial-site-bypass-workflow/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How financial-site-bypass-workflow Compares
| Feature / Agent | financial-site-bypass-workflow | 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 restricted financial sites when browser automation is blocked
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
# Financial Site Bypass Workflow When Codex-in-Chrome blocks financial domains (Fidelity, brokerages), direct browser automation fails. Instead: (1) Take a screenshot and paste it to Codex for OCR, (2) Manually export CSV/transaction files from the site UI and load them via file path, or (3) Copy/paste table data directly into chat. Store exported files in a local workspace folder and back them up to git. This preserves data access without unblocking security restrictions.
Related Skills
digitalmodel-orcawave-orcaflex-proof-workflows
Class-level digitalmodel OrcaWave/OrcaFlex readiness, semantic-proof, fixture-proof, and closeout workflows.
worktree-pre-push-bypass-for-tier1-checks
Handle workspace-hub integration-branch pushes from isolated git worktrees when the pre-push hook incorrectly assumes sibling tier-1 repos exist under the worktree path.
portable-pattern-verification-workflow
Multi-package implementation with verification strategy for cross-platform configuration hardening
plan-gated-issue-validation-workflow
Systematic validation pattern for plan-approved GitHub issues with pre-existing deliverables
multi-year-tax-filing-verification-workflow
Verify and reconcile complex multi-form tax filings by cross-referencing source documents, identifying data dependencies, and validating line-by-line against authoritative records.
multi-file-tax-reconciliation-workflow
Systematic parallel review and reconciliation of multi-document tax filings with cross-reference validation
metadata-only-wiki-sweep-workflow
Disciplined inventory process for cataloging documents by filename/path without content claims, using parent-centric grouping to prevent stub proliferation
handle-browser-automation-financial-site-blocks
Workflow for working around Chrome extension blocks on financial sites during data collection tasks
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
freetaxusa-efiling-workflow
Navigate FreeTaxUSA e-filing process through final steps, handling session timeouts and identifying required manual signature steps
financial-data-export-workflow
Structured process for exporting and analyzing multi-year brokerage transaction history when browser automation is blocked