audit-evidence-support

Builds, validates, and delivers PBC audit evidence packages with traceable versioning.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/lwokeray/cowork-plugins --skill audit-evidence-support-lwokeray
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-evidence-support
Source: https://github.com/lwokeray/cowork-plugins/tree/main/plugins/finance-cowork/skills/audit-evidence-support
Command: npx skills add https://github.com/lwokeray/cowork-plugins --skill audit-evidence-support-lwokeray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Audit teams struggle to turn auditor PBC requests into complete, reproducible, and access-controlled evidence packages. This Skill organizes evidence requests, verifies completeness and accuracy, ties evidence to financial statements, and tracks delivery without altering original records. ## Core Features & Use Cases - PBC and Evidence Register: Creates a stable tracker with unique request IDs, owners, due dates, evidence criteria, and status from Requested through Accepted or Rejected. - Completeness and Accuracy Checks: Validates system reports, spreadsheets, and IPE against parameters, control totals, populations, and tie-outs to GL or subledger sources. - Packaging and Delivery Control: Builds evidence indexes, cross-references, version registers, redaction reviews, and delivery logs with recipient and permission previews. - Use Case: An auditor requests Q2 AP aging plus three sample invoices with payment proof. The Skill assembles the system-generated aging, ties it to the AP subledger, builds the transaction chain for each sample, and delivers a versioned package with a receipt. ## Quick Start Ask the assistant to organize the Q2 audit PBC list, verify the received evidence, and package it for delivery to the auditor.

Frequently Asked Questions about audit-evidence-support

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a PBC evidence package for external auditors?▼

Define each request with a unique ID, owner, due date, and evidence criteria, then collect source-system records and verify completeness and accuracy. Build an evidence index with tie-outs and cross-references, preview recipients and permissions, and deliver only after approval.

How do I verify completeness and accuracy of an audit report or spreadsheet?▼

Check the report parameters, filters, period, entity, and extraction timestamp, then reconcile row counts and control totals against the source system or GL. For spreadsheets, inspect formulas, hidden content, hardcodes, and sample source-to-output traces.

What should I do when an auditor rejects an evidence item?▼

Keep the original delivery unchanged and mark it Rejected, then obtain a new version addressing the issue with documented changes. Re-run C&A and tie-out checks, review the new version, and deliver it with a delivery log linking both versions.

Can this skill modify or recreate original audit evidence?▼

No. Original evidence must remain unchanged; annotations, translations, or redactions are created as clearly labeled derived copies with source and transformation records. Fabricating, backdating, or deleting evidence is explicitly prohibited.

When should audit evidence not be shared externally?▼

Do not share when recipients, permissions, sensitivity labels, redaction rules, legal hold, or retention requirements are unclear. PII, payroll, tax, banking, or legally privileged data requires explicit approval from Legal, Privacy, or the data owner before any external delivery.