本文へ移動
cccskills
無料GitHub で公開

expense-reimbursement

Full lifecycle expense reimbursement: single invoice intake and staging, batch aggregation to generate reimbursement drafts, approval workflow, ledger and dashboard. Trigger when user mentions reimbursement, expenses, invoices, travel reimbursement, approval workflow, or needs to organize / verify / approve expense records. Also applies when user needs to enter invoices, view reimbursement dashboards, ledgers, or compliance checks.

インストール方法を見る

含まれるファイル(8)

  • SKILL.md1.9 KB
  • evals/evals.json2.1 KB
  • references/batch-reimbursement.md6.3 KB
  • references/feishu-base.md1.6 KB
  • references/invoice-intake.md2.3 KB
  • references/ledger-dashboard.md5.1 KB
  • references/sample-invoice.jpg1.1 MB
  • scripts/invoice_intake.py11.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Expense Reimbursement

Overview

Single invoice intake (staging) → Batch aggregation (draft + approval) → Ledger & Dashboard (reports)

Interaction Principles

  • Default to execute, ask only on error: after receiving an invoice, auto-complete parsing, writing, and uploading. Only interrupt if critical fields are missing or config is missing.
  • Results-oriented: after completion, show a "saved" summary directly. No intermediate "pending confirmation" states.
  • Config-first: use the Base token already configured in reference files. Do not ask user for it repeatedly.

Built-in Scripts

All invoice intake Base operations are handled by scripts/invoice_intake.py. Do not manually construct lark-cli commands.

  • AI handles: parsing invoice, determining expense type, generating reason description
  • Script handles: user identity, Base location, timestamp conversion, dedup, writing, attachment upload

See references/invoice-intake.md Step 4 for details.


Routing Rules

User ScenarioRead File
Submit an invoice, stage it firstreferences/invoice-intake.md
End-of-month batch aggregation, generate reimbursement draft, initiate approvalreferences/batch-reimbursement.md
View ledger, summary reports, budget analysisreferences/ledger-dashboard.md

When intent is unclear, ask: "Do you want to stage an invoice first, or organize and submit a reimbursement form for approval now?"

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

ai-tutor

無料

AI 初学者导师。抓取 AI 大厂最新博客(Anthropic/OpenAI/Cursor),提炼成结构化深度精读笔记,直接存入 CherryStudio 笔记目录。笔记包含术语百科、核心原理解析(含关键图表)、学习重点、知识关联和行业简报。调用方式:/ai-tutor(默认 Anthropic),/ai-tutor openai,/ai-tutor cursor。

日本語の概要は準備中です。原文の説明を表示しています。

CherryHQ/skills62026年6月29日 更新

标书文档分析与评估。当用户上传招标文件(.pdf/.docx/.doc/.xlsx)或明确要求「分析标书」「评估投标」「检查合规性」「标书评分」「废标风险」「技术方案评估」时使用。支持解析、评分计算、合规检查、废标风险识别,自动生成 Markdown 报告。版本 3.0

日本語の概要は準備中です。原文の説明を表示しています。

CherryHQ/skills62026年6月29日 更新

投标书模板填充引擎。当用户明确要求「填模板」「写标书」「出标书」「生成投标文件」「标书填充」「套模板」「做标书」,或提供了脱敏 DOCX 模板需要填充时使用。扫描模板中的占位符和虚拟文本,提取招标信息、收集投标人数据、构建替换映射、执行填充,输出可直接提交的成品标书。覆盖商务标+技术标+报价书全部章节。

日本語の概要は準備中です。原文の説明を表示しています。

CherryHQ/skills62026年6月29日 更新

cv-expert

無料

This skill should be used when the user asks to "优化简历", "resume optimization", "简历诊断", "tailor resume to JD", "改简历", "resume review", "简历优化助手", or when the user mentions "校招", "社招", "ATS", "JD匹配", "Word批注", shares a .docx resume path alongside a job description, or wants to match their resume to a specific job posting. Also triggers on "resume expert", "HR feedback", "interview prep with resume".

日本語の概要は準備中です。原文の説明を表示しています。

CherryHQ/skills62026年6月29日 更新

面试复盘 skill(求职者视角)。把一次已结束的面试,从「文字记录」沉淀成结构化复盘:逐题诊断 + 5 维评分 + 更优回答范本 + 下一场准备清单,最终产出一份飞书复盘文档。当用户说"面试复盘"、"复盘一下面试"、"刚面完 XX 帮我盘下"、"这场面试哪答崩了"、"面试问答记录帮我分析"时触发。区别于 resume-optimizer / cv-expert(面试前优化简历),本 skill 处理「面完之后」。

日本語の概要は準備中です。原文の説明を表示しています。

CherryHQ/skills62026年6月29日 更新

Discuss a community-edition product requirement with the user, draft a bilingual (Chinese + English) PRD for review, then — after explicit user approval — create the English-only issue on GitHub (<OWNER/REPO>). Use whenever the user wants to turn a requirement (from a Feishu doc, a meeting note, a customer ask, or a rough idea) into a GitHub issue. Triggers on phrases like "create requirement doc", "create a requirement", "put this requirement on GitHub", "create new feature issue", "draft an issue for...", or anytime the user describes a product feature/improvement they want tracked. The format is opinionated (Background / Goal / Spec / Verification / Related, NO implementation details, draft shown bilingually for human review, issue itself written in English only).

日本語の概要は準備中です。原文の説明を表示しています。

CherryHQ/skills62026年6月29日 更新

CherryHQ のスキルをすべて見る

このスキルの問題を報告する