Cash Flow Planner
v1.1.0Build 13-week cash flow forecasts, identify liquidity gaps, and design capital allocation plans for ecommerce businesses navigating inventory cycles and seas...
⭐ 0· 110·0 current·0 all-time
byLeroyCreates@leooooooow
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and all included reference guides/templates are focused on building 13‑week cash forecasts, scenario planning, and capital-allocation playbooks for ecommerce — no unrelated binaries, credentials, or system access are requested.
Instruction Scope
SKILL.md explicitly instructs the agent to pull 12+ weeks of transaction data (orders, payouts, supplier invoices, bank/accounting data) and to use the provided templates — accessing financial data is expected for this task. This is scope-appropriate, but it does require the user to provide sensitive financial exports (CSV, accounting reports, bank statements); the skill does not declare or use any secret/credential variables nor does it instruct the agent to access unrelated system files.
Install Mechanism
No install spec and no code files — instruction-only content. Nothing will be downloaded or written to disk by an installer.
Credentials
The skill requests no environment variables, credentials, or config paths. The only implied requirement is user-supplied financial data (Shopify/Stripe exports, invoices, bank/accounting reports), which is proportional to the stated purpose.
Persistence & Privilege
always is false, and the skill does not request persistent or elevated privileges or attempt to modify other skills or system settings. Normal autonomous invocation is allowed by default but does not appear excessive here.
Assessment
This skill is a set of templates and instructions for building 13‑week cash forecasts and is internally consistent. Before using it: (1) Do not share live credentials — export only the necessary CSVs/reports (orders, payouts, supplier invoices, payroll) rather than giving account login details. (2) Redact any personal identifiers you don't want included in the forecast. (3) Confirm any connectors or third‑party integrations separately (the skill itself declares none). (4) Review the forecast outputs before sharing externally (investors/lenders) since the agent may process sensitive financial numbers. If the agent asks for direct bank or platform logins, treat that as unnecessary and refuse; provide exported reports instead.Like a lobster shell, security has layers — review code before you run it.
latestvk97bwm73fqk1smnvaq8gb03chs83w62d
License
MIT-0
Free to use, modify, and redistribute. No attribution required.