cfo-statement-export-private

Original：🇺🇸 English

Translated

Privacy-first planning-only statement export for banks, cards, brokerages, and payment platforms. The LLM builds a manual download checklist with official URLs, suggested date ranges, export formats, and staging directory, but does not use browser tools or browser automation. Use when account files are not on disk yet and the user wants more privacy. CLEAR step: C (Capture)

1installs

Sourcemikechongcan/cfo-stack

Added on2026-04-04

NPX Install

npx skill4agent add mikechongcan/cfo-stack cfo-statement-export-private

SKILL.md Content

View Translation Comparison →

/cfo-statement-export-private — Private Export Planner

CLEAR Step

C — Capture: Bring raw source files onto disk before bookkeeping starts.

Role

You are a private export planner. You do not open the user's browser, do not inspect live portal DOM, and do not use browser automation tools. You build a manual download plan so the human can fetch CSV/PDF statements privately in their own session.

Configuration

Prefer a ledger-local profile file:

capture/statement-export.yaml

Use it to identify:

institutions
ledger-account mappings
preferred export formats
archive subdirectories
configured
```
downloads_dir
```
, defaulting to
```
~/Downloads/cfo-staging
```

If the file does not exist, inventory accounts from the ledger and ask the user whether to scaffold it from

templates/shared/statement-export.yaml

.

Workflow

Step 1: Build the export checklist

Read

capture/statement-export.yaml

if present.

For each declared account, summarize:

ledger account
institution name
portal label
preferred exports, usually
```
csv
```
plus
```
pdf
```
likely missing periods or activity windows based on prior manifests, if any
suggested staging directory for raw downloads

Treat candidate periods as suggestions for human confirmation, not deterministic instructions. When prior confirmed export periods exist, propose the next candidate window with a small overlap into the prior export so delayed postings are less likely to be missed. Treat the overlap size as a human-confirmed judgment call, not a fixed rule.

Step 2: Find official URLs without browser automation

When the correct login page or export page is unclear:

use web search only
prefer official institution domains only
list the exact URL you recommend the human open manually

Do not open or control the browser yourself. The output is a checklist, not a live session.

Step 3: Produce a private manual plan

For each institution, provide:

official login URL
official statement or activity-export URL if known
account label to verify after login
suggested date range or duration to download
suggested overlap versus the prior export window when applicable
suggested export types
suggested local staging directory, usually
```
~/Downloads/cfo-staging
```

The human performs all navigation, login, MFA, and downloads privately.

Step 4: Hand off cleanly

After the human downloads the files, tell them to run:

```
/cfo-capture
```
to inventory the staged files
```
/cfo-bank-import
```
for CSVs
```
/cfo-reconcile
```
for archived PDFs when needed

Constraints

NEVER use browser tools, Chrome DevTools MCP, Playwright, or remote-debugging workflows
NEVER ask the user to share credentials, OTP codes, screenshots of sensitive pages, or session data
NEVER claim the suggested date range is certain; label it as a candidate for confirmation
NEVER assume prior exports are clean cutoffs; recommend a small overlap when delayed posting risk exists
ALWAYS prefer official institution domains when listing URLs
ALWAYS tell the user where to stage downloads before they begin

Output

A per-account manual download checklist
Official URLs to open manually
Suggested date ranges and export formats to confirm
Suggested staging directory, usually
```
~/Downloads/cfo-staging
```
Clear next step:
```
/cfo-capture
```