Audit
A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.
npx -y skills add bromso/metapowers --skill auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Perform a deep-dive review of specific accounts or transactions
SKILL.md
2.2 KB, as published. Nobody here has run it
Audit
Audit specific accounts or transactions for "$ARGUMENTS". Examine supporting documentation, test balances, and identify discrepancies or irregularities.
Prerequisites
None — utility skill, run anytime. More effective when ledger data is available from Phase 3 or later.
Process
-
Define audit scope:
- Which accounts or transaction types are being audited?
- What period is covered?
- What is the audit objective? (accuracy, completeness, existence, valuation, disclosure)
- What materiality threshold applies?
-
Gather evidence:
- Pull account balances and transaction details from the ledger
- Request supporting documentation (invoices, contracts, confirmations)
- Identify the population and select a sample (statistical or judgmental)
-
Perform audit procedures:
- Vouching — trace recorded transactions back to source documents (tests existence/occurrence)
- Tracing — trace source documents forward to recorded transactions (tests completeness)
- Recalculation — independently recalculate key amounts
- Confirmation — verify balances with third parties (banks, customers, vendors)
- Analytical procedures — compare to expectations, prior periods, or industry benchmarks
-
Document findings:
- For each finding, record:
- Condition — what was found
- Criteria — what was expected
- Cause — why the discrepancy exists
- Effect — financial impact
- Recommendation — corrective action
- For each finding, record:
-
Write the artifact to
.metapowers/accounting/$ARGUMENTS/audit.mdwith sections:- Audit Scope & Objectives — what was audited and why
- Procedures Performed — tests conducted and samples selected
- Findings — each finding with condition, criteria, cause, effect, recommendation
- Conclusion — overall assessment of account accuracy and reliability
Output
The audit written to .metapowers/accounting/$ARGUMENTS/audit.md. Present a summary highlighting:
- Number of findings by severity
- Total financial impact of discrepancies
- Key recommendations