Security audit
Security checks for vulnerabilities and agentic risk
The skill matches a financial transaction enrichment purpose, but it needs review because it handles banking and email-derived data, mutates local financial databases, documents cron automation, and includes unpinned self-update instructions.
Install only if you are comfortable giving this skill access to local banking databases, Plaid tokens, Google/Places keys, possible Gmail receipt content, and scheduled database-changing workflows. Before use, require explicit read-only versus write/sync modes, remove or externalize self-update instructions, pin reviewed versions, clarify Gmail receipt scope, and define retention/consent rules for LLM queues and receipt line items.
Error handling in styx follows a strict never-modify-raw-data policy: if enrichment fails, log the error, mark the record as unresolved, and continue processing. - **Self-update: untracked files block `git pull`** — `git stash` only stashes tracked files. New (untracked) files in the skill directory will block the merge. Move them aside before pulling, then compare/restore afterward. - **Self-update: stash pop may conflict** — After pulling, `git stash pop` can produce merge conflicts if both the pulled changes and the stashed changes touch the same lines. - **`query.py --health-check` does not exist** — Use inline Python to verify DB integrity instead. - **Raw transaction data is sacred** — Styx never modifies or deletes records in `transactions.db`.
Error handling in styx follows a strict never-modify-raw-data policy: if enrichment fails, log the error, mark the record as unresolved, and continue processing. - **Self-update: untracked files block `git pull`** — `git stash` only stashes tracked files. New (untracked) files in the skill directory will block the merge. Move them aside before pulling, then compare/restore afterward. - **Self-update: stash pop may conflict** — After pulling, `git stash pop` can produce merge conflicts if both the pulled changes and the stashed changes touch the same lines. - **`query.py --health-check` does not exist** — Use inline Python to verify DB integrity instead. - **Raw transaction data is sacred** — Styx never modifies or deletes records in `transactions.db`. - **Name cleaning is essential** — Plaid transaction names are heavily obfuscated (e.g., `DD *DOORDASH ROYALINDI`, `ABM-350 MISSION GARAGE`). Strip prefixes before matching.
## Automation ### Self-update Pull the latest Styx package from GitHub source. Full procedure: `references/self_update.md`. ## Support File Map
## Automation ### Self-update Pull the latest Styx package from GitHub source. Full procedure: `references/self_update.md`. ## Support File Map
| `references/query-api.md` | Before writing consumer queries | | `references/enrichment-pipeline.md` | Before running or debugging LLM enrichment | | `references/styx_universal_enrichment.md` | Before running Google Places enrichment (read FIRST) | | `references/self_update.md` | Before running self-update | | `references/cron-gotchas.md` | Before debugging cron enrichment failures | | `references/verify-bank-alert.md` | Before cross-checking a bank/card email alert against local ledger |
| `references/query-api.md` | Before writing consumer queries | | `references/enrichment-pipeline.md` | Before running or debugging LLM enrichment | | `references/styx_universal_enrichment.md` | Before running Google Places enrichment (read FIRST) | | `references/self_update.md` | Before running self-update | | `references/cron-gotchas.md` | Before debugging cron enrichment failures | | `references/verify-bank-alert.md` | Before cross-checking a bank/card email alert against local ledger |
- **URL**: https://portal.plaid.com — self-serve, no business verification - **Free tier**: Up to 100 linked accounts for personal use - **Supports**: 12,000+ institutions including Capital One and Chase - **Auth**: Plaid Link flow → access token - **Python SDK**: `plaid-python` - **Production base URL**: `https://production.plaid.com`
### Teller Details (_not used_) - Free tier = sandbox only, fake banks - Production requires mTLS (client cert + private key) + user access tokens - Dashboard is Phoenix LiveView SPA — doesn't render in regular browser tool - Teller Connect JS requires HTTPS → needs self-signed cert + Cloudflare tunnel or similar
# Styx Self-Update Procedure ## When to run
If an update causes issues:
```bash
cd {skill_root} && git reset --hard HEAD~1
```
## GotchasBusiness name:"""
return prompt
# ── Main enrichment ──────────────────────────────────────────────────────────print(f"Found {len(redacted)} redacted transactions")
# Get all access tokens
tokens = txn_conn.execute('SELECT access_token FROM plaid_items').fetchall()
# For each token, pull recent transactionsprint(f"Found {len(redacted)} redacted transactions")
# Get all access tokens
tokens = txn_conn.execute('SELECT access_token FROM plaid_items').fetchall()
# For each token, pull recent transactions# ── Plaid helpers ─────────────────────────────────────────────────────────────
def load_env(path):
"""Load environment variables from a .env file."""
env = {}
with open(path) as f:
for line in f:No suspicious patterns detected.