expense-policy

GitHub

用于撰写清晰、实用的公司费用与报销政策,涵盖覆盖范围、限额、审批流程及不可报销项。旨在帮助员工自信消费并减少财务沟通成本。需根据公司规模等上下文生成,金额标记为待确认,非法律或税务建议。

exports/openclaw/expense-policy/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

撰写费用政策 制定报销政策 创建差旅与费用(T&E)政策 制定支出指导方针

Install

npx skills add mohitagw15856/pm-claude-skills --skill expense-policy -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/exports/openclaw/expense-policy -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@expense-policy

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill expense-policy -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "expense-policy",
    "homepage": "https:\/\/mohitagw15856.github.io\/pm-claude-skills\/skill\/expense-policy.html",
    "metadata": {
        "openclaw": {
            "emoji": "🧾"
        }
    },
    "description": "Write a clear company expense & reimbursement policy. Use when asked to write an expense policy, a reimbursement policy, a travel & expense (T&E) policy, or spending guidelines. Produces a practical policy — what's covered, limits by category, the approval and submission process, timelines, and what's not reimbursable — that's fair, easy to follow, and reduces finance back-and-forth. Not tax\/legal advice."
}

Expense Policy Skill

A good expense policy answers the questions people actually have — "can I expense this, how much, and how do I get paid back?" — before they have to ask. This skill writes a clear, fair policy with category limits and a simple process, so employees spend confidently and finance isn't chasing receipts.

Note: this is a drafting aid, not tax, legal, or accounting advice. Tax treatment of reimbursements, per-diem rules, and what's deductible vary by jurisdiction — have it reviewed by finance/an accountant. Set the amounts to your company's actual budget.

Working from a brief

Given "an expense policy for a 50-person startup", produce the full policy anyway — use sensible, clearly-labelled default limits (set your amount) and a standard process, marking company-specific choices. Never present limits or tax treatment as authoritative; flag them to set/confirm.

Required Inputs

Ask for these only if they aren't already provided (else use a labelled default):

  • Company context — size, remote/office, and how generous/lean the culture is.
  • Categories — what's commonly expensed (travel, meals, software, home office, client entertainment).
  • Limits & approvals — any existing per-category limits and who approves what.
  • Process & tools — how expenses are submitted (tool/spreadsheet), reimbursement method, and timelines.

Output Format

Expense & Reimbursement Policy

  • Purpose & principles — the spirit (spend as if it's your own money; reasonable, business-related), in a line or two.
  • What's reimbursable — by category, with limits (set your amount):
Category What's covered Limit / guidance Approval
Travel (flights/hotels) e.g. economy; $X/night manager
Meals business meals $X/day or per-meal manager
Software/tools work subscriptions up to $X manager/IT
Home office equipment $X one-time manager
  • What's not reimbursable — the clear exclusions (personal items, alcohol policy, fines, etc.).
  • Approval — who approves, and the threshold where extra sign-off is needed.
  • How to submit — the step-by-step (receipts required over $X, submit within N days, the tool used).
  • Reimbursement — method and timeline (e.g. next payroll / within N days).
  • Travel specifics — booking process, per-diems if used, and advances.
  • Misuse — what happens if the policy is abused.

Mark all amounts (set your amount) and add a note to confirm tax treatment with finance.

Quality Checks

  • Each common category has clear coverage and a limit (or a labelled placeholder)
  • The approval thresholds and approvers are explicit
  • The submission process (receipts, deadlines, tool) is step-by-step
  • Reimbursement method and timeline are stated
  • Non-reimbursable items and misuse consequences are covered
  • Amounts and tax treatment are flagged to set/confirm, not asserted

Anti-Patterns

  • Do not leave limits vague ("reasonable") with no number or guidance — that creates the disputes
  • Do not bury the process — people need to know exactly how to get paid back
  • Do not assert tax/per-diem rules as fact — flag for finance to confirm by jurisdiction
  • Do not omit what's not covered — the exclusions prevent the awkward conversations
  • Do not make it so strict it signals distrust, or so loose it has no teeth — aim for fair and clear

Based On

Finance-operations practice — clear, category-based expense policies with limits, approval workflow, and a simple submission/reimbursement process.

Version History

  • 54fad50 Current 2026-07-19 12:19

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
bdf76920
Indexed
2026-07-19 12:19

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 19:26
浙ICP备14020137号-1 $방문자$