mcpbeat Sign in

Internal Controls And Audit Agent Skill

Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. Use this to design controls for a process, prepare for an external audit, respond to an audit finding, set approval thresholds, or assess where a small team's segregation of duties is genuinely broken.

797 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
220
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/cbrock84/headcount --skill internal-controls-and-audit

The instruction itself

6 sections, as written by the author

Internal controls and audit

Controls exist because a single person who can initiate, approve and record a transaction can also

conceal one. Everything else is elaboration on that.

**This structures control design and audit readiness. Statutory audit requirements, and regimes such

as SOX where they apply, are matters for your auditors and qualified advisers.**

Segregation of duties

Four capabilities should not sit with one person: initiating a transaction, approving it,

recording it, and holding the asset. Any two combined is a risk; three is an unmonitored

opportunity.

Small teams cannot always separate these. That is a normal constraint and pretending otherwise

produces a fictional control matrix. Where separation is impossible, compensate visibly:

  • Review by someone outside the process, on a defined cadence rather than when convenient.
  • Exception reporting that goes to someone who is not the preparer.
  • Bank confirmations and reconciliations reviewed independently of whoever performs them.

Document the gap and the compensating control. An acknowledged, mitigated gap is a defensible

position; an unacknowledged one is a finding waiting to be written.

Design controls that leave evidence

A control that happened but left no trace did not happen, as far as an auditor can determine. Each

control needs a stated owner, frequency, what is examined, and an artifact produced as a by-product

of doing the work — not assembled afterwards for the audit.

Prefer preventive controls, which stop the transaction, over detective ones, which find it

afterwards. Prefer automated over manual: system-enforced approval limits do not have busy weeks.

Approval thresholds

Set limits by value and by risk, not value alone. A low-value payment to a new supplier deserves more

scrutiny than a large one to an established counterparty on contracted terms.

Watch for splitting — transactions repeatedly landing just under a threshold is the pattern the

threshold creates, and it is straightforward to monitor for.

Audit findings

Treat a finding as information. Fix the cause rather than the instance, and be skeptical of

remediation that consists of more careful behavior: the same conditions will reproduce the finding

with different people.

Related but distinct: legal-risk:corporate-governance owns board and entity governance,

legal-risk:enterprise-risk owns the risk framework. This skill owns controls over financial

reporting.

Never

  • Sign a control matrix that describes separation the team does not actually have.
  • Accept a control with no evidence produced in the ordinary course of performing it.
  • Remediate a finding with a commitment to be more careful.
  • Set approval limits on value alone and not monitor for splitting.

How to use it

Copy the folder

Take cbrock84/internal-controls-and-audit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.