360 Secure SkillHub
360 安全技能中心

Bookkeeping Reconciliation Helper

核心功能是协助搭建银行流水、发票、收据等与会计账簿的可重复对账流程,留存未匹配异常,提供定制化工作流、检查表、代码方案等。适用于财务运营团队、簿记员、小企业主或开发者做对账自动化场景。输入为用户的对账需求与约束,输出含定制解决方案、可复用检查表及验证说明,优先本地友好方案,确保用户可直接执行。

kyro-ma
kyro-ma
热度 16.02
最近更新 2026-06-22 16:02:05
分类:数据依赖:代码执行 / 读写文件 / 内部调用大模型应用场景:财务 / 数据处理 / 工作流 / 模板 ...

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add bookkeeping-reconciliation-helper
Metadata
name
bookkeeping-reconciliation-helper
description
Help users with Validated demand: Finance and operations teams need repeatable workflows for reconciling bank feeds, invoices, receipts, payment processor exports, and accounting ledgers without losing unmatched exceptions. This requirement is supported by 12 separate online signals across 2 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, bookkeeping, bank reconciliation, invoice matching, receipts, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.

Bookkeeping Reconciliation Helper

Requirement

Use this skill to help bookkeepers, accountants, finance operations teams, small business owners, and developers automating reconciliation workflows with:

Validated demand: Finance and operations teams need repeatable workflows for reconciling bank feeds, invoices, receipts, payment processor exports, and accounting ledgers without losing unmatched exceptions. This requirement is supported by 12 separate online signals across 2 source families, so it represents broader demand rather than a single isolated request.

Demand score: 90/100 (70/70 demand, 30/30 local feasibility). Evidence: 12 signals across 2 source families.

Read references/requirement-plan.md when source evidence, planning details, or review criteria are needed.

Workflow

  1. Restate the user's outcome, constraints, available inputs, and success criteria.
  2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.
  3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.
  4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.
  5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.
  6. Validate the output against the success criteria and list any remaining risks or follow-up work.

Expected Outputs

  • A tailored answer or artifact for the user's immediate situation.
  • A reusable checklist or workflow when the task is repeatable.
  • A verification note showing how the result was checked.

Validation

  • The output directly addresses the discovered requirement.
  • The user can act on the result without reading the original source post.
  • Assumptions, limits, and required inputs are visible.
  • The final response includes a short usage or next-step note when helpful.

Triggers

Keywords: software-and-data, bookkeeping, bank reconciliation, invoice matching, receipts, accounting ledger

Example trigger sentences:

  • Help me Finance and operations teams need repeatable workflows for reconciling bank feeds, invoices, receipts, payment processor.
  • I need a practical workflow for Finance and operations teams need repeatable workflows for reconciling bank feeds, invoices, receipts, payment processor.
  • Use $bookkeeping-reconciliation-helper to handle Finance and operations teams need repeatable workflows for reconciling bank feeds, invoices, receipts, payment processor.