← VibooksCONTENT HISTORY

Update to Vibooks

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.4.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Record receipts, bills, invoices, expenses, sales, payments, refunds, and statement-backed activity from source documents into Vibooks. Use when a user provides a folder or set of bookkeeping documents and wants reviewable, source-aware entries created through proper subledger workflows.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 298
    }
  ],
  "name": "bookkeep-documents",
  "skill_md_contents": "---\nname: bookkeep-documents\ndescription: >\n  Record receipts, bills, invoices, expenses, sales, payments, refunds, and\n  statement-backed activity from source documents into Vibooks. Use when a\n  user provides a folder or set of bookkeeping documents and wants reviewable,\n  source-aware entries created through proper subledger workflows.\n---\n\n# Bookkeep Documents\n\nFollow the bundled `vibooks` skill for professional bookkeeping treatment,\nsource evidence, jurisdiction, tax, correction, and verification rules.\n\nThe plugin already provides the bundled Vibooks workflow. Do not install a\nduplicate standalone skill with `npx skills`; use the agent client's plugin\nmanager for plugin updates.\n\n1. Run `vibooks_readiness` when available and confirm the intended company,\n   book, accounting period, and source-document scope.\n2. Read the original receipts, bills, invoices, statements, and attachments.\n   Stop for material ambiguity in dates, counterparties, amounts, tax\n   treatment, payment state, or intended accounting treatment.\n3. Use first-class Vibooks workflows for invoices, bills, receipts, payments,\n   refunds, applications, transfers, payroll, and adjustments. Do not replace\n   them with generic journals when a supported workflow exists.\n4. Discover unfamiliar operations with `vibooks_ops`, then inspect contracts\n   with `vibooks_describe` and `vibooks_schema`.\n5. Before any write, summarize the intended records and confirm that the user\n   authorized that bookkeeping action. Pass `confirmMutation: true` to\n   `vibooks_invoke` only for that reviewed, authorized write.\n6. Attach or link source evidence where supported, read the result back, and\n   run workflow-specific verification before calling the batch complete.\n\nReport records created or corrected, evidence linked, exceptions requiring a\ndecision, and verification results. Do not claim tax filing, audit, or\nassurance work.\n"
}

SHA-256 of public snapshot: 7a4712d27ae5b412f4d50133cc03d699ea11fb2b089325f9c567155ed4f26cb5