Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月12日 更新
無料GitHub で公開
pb-invoice-check
Check invoices and receipts line by line against your offers and list what matches, what differs and what has no offer. Nothing is paid or sent. Use for "check my invoices", "match invoices to offers", "does this invoice match the quote".
含まれるファイル（1）
- SKILL.md2.2 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Invoice check
What you get: invoices and receipts sorted and checked line by line against the matching offers.
Inputs
- An invoices folder with PDFs
- An offers folder — the
offer.mdfiles from pb-offer - A save folder — asked once; default
./pb-invoice-check-<date>/
Steps
- Ask once — save folder, invoices folder, offers folder →
run-log.md; list the PDFs.pdftotextis not installed, so you read each PDF with the harness PDF read; a PDF it cannot read becomes a row with statusunreadand the run continues — you may paste its text later - Per readable PDF →
invoices.csv, columns file, vendor, date, number, net, VAT, total, status — a field that is not on the invoice is?; every PDF in the folder has exactly one row - Match each invoice to an offer by vendor, client and items → matched offer named in
invoices.csv; no offer found → statusno offer - Write
check.md: per invoice match / mismatch (which line, how much it differs) / no offer / unread — every total recomputed from its lines; the recomputed value and the printed value are both shown - Show
invoices.csvandcheck.mdin full and apply your edits until you approve — approval logged
Nothing is paid or sent, so there is no GO step. The run only reads the two folders and writes into the save folder.
Run log: run-log.md in the save folder. One line per step as it completes (N. done|skipped|failed — file — check result). If a check fails, stop, write the failure into the log and tell the user.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月12日 更新
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月12日 更新
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月12日 更新
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月12日 更新
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
日本語の概要は準備中です。原文の説明を表示しています。
hybridlabor-api/aos62026年10月12日 更新