Expense Claims Ops
v1.0.0Process personal/work expenses and reimbursement claims in a structured, low-friction workflow. Use when collecting receipts, categorizing spend, preparing c...
⭐ 0· 291·0 current·0 all-time
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 included reference files all match a lightweight expense-claims workflow. The skill requests no binaries, env vars, or config paths that would be unrelated to processing receipts, so there are no surprising capability requests.
Instruction Scope
SKILL.md describes collecting receipts, extracting line items, validating rules, and producing summaries/templates. All steps operate on user-provided inputs (receipt set, date range, policy). Instructions do not direct the agent to read system files, environment variables, or contact external endpoints.
Install Mechanism
No install spec or code files are provided (instruction-only). This minimizes disk writes and avoids pulling external code; nothing to install or execute beyond the agent following the prose.
Credentials
The skill declares no required credentials or environment variables, which is appropriate. One operational note: in practice, integrating with a company tool or email (mentioned as possible 'claim destination') will require credentials provided by the user — the skill itself does not request them, so any credential prompts will come from the agent or external integrations, not this skill.
Persistence & Privilege
always is false and the skill is user-invocable. There is no indication the skill will persist itself, modify other skills, or change system/agent-wide settings.
Assessment
This skill is instruction-only and internally consistent for processing expense items. Before using it, ensure you: (1) only feed it the receipts and fields you are comfortable sharing (don’t include sensitive personal documents), (2) provide any company-tool/email credentials only when you trust the agent/integration and understand where those credentials are stored/used, and (3) review the claim templates and schema included to confirm they match your organization's policy. Although no installs or secrets are requested by the skill itself, exercise the usual caution around sharing financial or personally identifiable data with any agent or integration.Like a lobster shell, security has layers — review code before you run it.
latestvk972jgrb4j2thz2bbr4ya865t5824ttj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.