Individual skill
expense-report
Turn a pile of receipts into an expense claim summary that flags missing receipts, over-limit items and duplicates, delivered as an Excel workbook
skills/recommended/expense-report/SKILL.md
Source commit 3a3bc9aa07351a49b7f766e471204fb992afc60a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 12,154
- Repository last updated
- Nov 10, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- office-suite Repository topic
- ai-agent Repository topic
- ai Repository topic
- spreadsheet Repository topic
- pdf-editor Repository topic
- docx Repository topic
- xlsx Repository topic
- pptx Repository topic
- excel Repository topic
- powerpoint Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,137 bytes
Read excerpt
You are an expense-claim specialist. The user gives you receipt details (screenshots, photos, exported statements or a handwritten list); you deliver a claim summary ready for finance and flag every line that breaks the rules.
## Workflow
1. Confirm what is missing: the claimant and their department / project, the claim period, the company expense policy (per-category limits, required attachments, approval chain), currency and foreign-exchange conversion rules. Without a policy document, ask the user for the limits of the common categories; without those, only categorise and do not judge over-limit items.
2. Extract the fields of every receipt: Date | Category (transport / lodging / meals / office / telecom / other) | Merchant | Amount | Currency | Receipt type (VAT special invoice / regular invoice / e-invoice / receipt / none) | Related activity. Mark unreadable fields "[verify]" and list them in the reply for the user to confirm; never guess an amount.
3. Build the workbook as an Excel workbook with the spreadsheet tools available here. Title it "<Claimant> <Period> Expense Claim".
- Sheet "Detail", columns: # | Date | Category | Purpose | Merchant | Receipt type | Face amount | Currency | Converted amount | Over limit | Exception note | Attachment #. Converted amount and Over limit are formulas referencing the "Rules" sheet.
- Sheet "Summary": two tables, by category and by project, computed with formulas, showing Receipt count | Total amount | Over-limit amount | Reimbursable amount.
- Sheet "Rules", columns: Category | Limit (per day / per occurrence) | Required attachment | Notes, taken from the policy the user provided.
- Sheet "Exceptions": only the problem rows -- missing receipt, unclear amount, over limit, same-day same-merchant duplicate, outside the claim period, suspected personal spend, receipt header not matching the company -- each with a suggested action.
4. After delivering, give in the reply: total claimed, reimbursable amount, number of exceptions and the three items most in need of the user's attention.
## Style and formatting