Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
This skill should be used when managing financial data, syncing bank transactions via Plaid/GoCardless, fetching bills from Gmail, or exporting to Beancount/Ledger formats. Provides local-first data sovereignty for OpenClaw users.
This skill should be used when managing financial data, syncing bank transactions via Plaid/GoCardless, fetching bills from Gmail, or exporting to Beancount/Ledger formats. Provides local-first data sovereignty for OpenClaw users.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Complete financial data management for OpenClaw with local-first architecture. Sync bank transactions, fetch bills from email, and export to accounting formats.
BillClaw is safe, open-source software designed with security-first principles.
Transparent packages: All npm packages are open-source and published with provenance Auditable code: Full source available at GitHub npm provenance: Cryptographic proof linking packages to source code Local-first: Your financial data never leaves your machine User-controlled credentials: You provide all API credentials through your own accounts System keychain: Tokens encrypted in your platform's secure keychain Explicit invocation: Requires explicit user action (disable-model-invocation: true) See SECURITY.md for detailed security architecture and verification steps.
ConcernExplanationsets-process-nameComes from transitive npm dependencies, not BillClaw codedetect-debug-environmentCommon Node.js ecosystem pattern, not maliciousAPI credentialsRequired for functionality; you control them from your accountsExternal packagesAll packages are open-source with npm provenance
Important: Credentials are NOT required at install time. Configure them when you're ready to use specific features: Environment VariablePurposeRequired ForPLAID_CLIENT_IDPlaid API client IDPlaid bank syncPLAID_SECRETPlaid API secretPlaid bank syncGMAIL_CLIENT_IDGmail OAuth client IDGmail bill fetchingGMAIL_CLIENT_SECRETGmail OAuth client secretGmail bill fetching Obtain credentials from: Plaid: https://dashboard.plaid.com/ Gmail: https://console.cloud.google.com/apis/credentials Configure via: Environment variables (recommended) Configuration file (~/.firela/billclaw/config.json) OpenClaw config under skills.entries.billclaw.env
npm install @firela/billclaw-openclaw The plugin registers these tools and commands with OpenClaw: Tools: plaid_sync, gmail_fetch, conversational_sync, conversational_status Commands: /billclaw-setup, /billclaw-sync, /billclaw-status, /billclaw-config
When you're ready to use a feature, configure the required credentials: # For Plaid bank sync export PLAID_CLIENT_ID="your_client_id" export PLAID_SECRET="your_secret" # For Gmail bill fetching export GMAIL_CLIENT_ID="your_client_id" export GMAIL_CLIENT_SECRET="your_secret"
/billclaw-setup The interactive wizard will guide you through: Connecting bank accounts (Plaid/GoCardless) Configuring Gmail for bill fetching Setting local storage location
You: Sync my bank transactions for last month OpenClaw: [Uses plaid_sync tool from BillClaw plugin] Synced 127 transactions from checking account Or use the command directly: /billclaw-sync --from 2024-01-01 --to 2024-12-31
/billclaw-export --format beancount --output 2024.beancount
This skill provides instructions for using BillClaw with OpenClaw. The actual integration is provided by the @firela/billclaw-openclaw npm package.
plaid_sync - Sync bank transactions from Plaid gmail_fetch - Fetch bills from Gmail conversational_sync - Natural language sync interface conversational_status - Check sync status
/billclaw-setup - Configure accounts /billclaw-sync - Sync transactions /billclaw-status - View status /billclaw-config - Manage configuration
For users who prefer a command-line interface, the standalone CLI is available as a separate npm package. See https://github.com/fire-la/billclaw for installation instructions.
For self-hosted OAuth flows, the Connect server is available as a separate npm package. See https://github.com/fire-la/billclaw for configuration details.
SourceDescriptionRegionsPlaidBank transaction syncUS, CanadaGoCardlessEuropean bank integrationEuropeGmailBill fetching via emailGlobal
Location: ~/.firela/billclaw/ (your home directory) Format: JSON files with monthly partitioning Security: Local-only storage
Configuration is stored in ~/.firela/billclaw/config.json: { "plaid": { "clientId": "your_client_id", "secret": "your_secret", "environment": "sandbox" }, "gmail": { "clientId": "your_gmail_client_id", "clientSecret": "your_gmail_client_secret" } }
2024/01/15 * "Starbucks" Expenses:Coffee Liabilities:CreditCard:Visa $5.50
2024/01/15 Starbucks Expenses:Coffee $5.50 Liabilities:Credit Card:Visa
Documentation: https://github.com/fire-la/billclaw Issues: https://github.com/fire-la/billclaw/issues Security: Report security vulnerabilities privately at security@fire-la.dev npm packages: https://www.npmjs.com/org/firela
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.