travel-expense-audit
Audit travel / 差旅报销 claims against uploaded policy handbooks and rate tables (lodging caps, transport, per diem). Use for 差旅费审核, travel expense review, or lodging over-limit checks.
npx skills add vixues/LeAgent --skill travel-expense-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Travel expense audit ## Required inputs 1. Claim packet (forms, invoices, itinerary) 2. Policy / finance handbook (PDF/DOCX) — ask the user to upload if missing 3. Rate tables when lodging/transport caps are not in the handbook ## Before auditing Use **`ask_user` alone** if any of these are unclear: - Which handbook version applies - Whether lodging / meal / transport caps must all be checked - Output format (marked PDF notes vs Excel findings table) ## Workflow 1. Extract rule clauses that apply (especially **住宿费超标**). 2. Normalize claim line items (date, city, amount, category). 3. Check each line against caps; list pass/fail with cited rule text. 4. Emit a structured findings table; cite managed download URLs. ## Learning When the user points out a missed rule, add it to the skill notes / procedure so the next audit of the same org includes that check by default.
- Required inputs
- Before auditing
- Workflow
- Learning
What does the travel-expense-audit skill do?
Audit travel / 差旅报销 claims against uploaded policy handbooks and rate tables (lodging caps, transport, per diem). Use for 差旅费审核, travel expense review, or lodging over-limit checks.
How do I install it?
Run `npx skills add vixues/LeAgent --skill travel-expense-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vixues/LeAgent, a repository with 195 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.