Bill Manager
v1.0.2Manage daily bills, expenses, and recurring payments with tracking, reminders, and analysis. Use when the user asks about bill management, expense tracking,...
⭐ 0· 128·1 current·1 all-time
byhaidong@harrylabsj
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (bill management, reminders, expense tracking, analysis) align with the provided SKILL.md and reference documents. All included files are templates, guidance, and workflows appropriate for a bill/expense management helper. Nothing in the manifest or SKILL.md asks for unrelated capabilities.
Instruction Scope
Runtime instructions are purely organizational: templates, reminder schedules, analysis frameworks, and manual workflows. The SKILL.md explicitly states it does not connect to bank/payment systems and requires manual data entry. It does not instruct the agent to read local files, access environment variables, or send data to external endpoints.
Install Mechanism
There is no install spec and no code files; this is instruction-only, so nothing will be written to disk or fetched at install time. This represents the lowest install risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. That matches the stated limitation that it performs organizational guidance only and does not integrate with external services.
Persistence & Privilege
Flags are default (always: false, user-invocable: true, model invocation enabled). There is no attempt to persist configuration, modify other skills, or require elevated presence.
Assessment
This skill appears coherent and low-risk: it provides templates and guidance only and does not request credentials or install code. Before installing, consider that (1) there is no provenance or homepage listed — if you require vendor accountability you may prefer a skill with a known author or homepage; (2) the skill does not automate payments or connect to banks — if you want automation you will need additional integrations which will require credentials; and (3) when using any personal-finance templates, avoid pasting full account numbers, passwords, or sensitive credentials into chat fields or into third‑party tools unless you trust them. If you want automation later, review any added integration for required env vars and external endpoints before granting access.Like a lobster shell, security has layers — review code before you run it.
latestvk97fsfs0pt3j3zhnfga39s8rns83aj6n
License
MIT-0
Free to use, modify, and redistribute. No attribution required.