agentsclimarketplace

Controls

Skill bromso/metapowers/plugins/accounting/skills/controls

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.

Install
npx -y skills add bromso/metapowers --skill controls

Assembled 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

Design internal controls to prevent errors and fraud

SKILL.md

2.2 KB, as published. Nobody here has run it

Controls

Design internal controls for "$ARGUMENTS". Establish preventive and detective controls to safeguard assets, ensure accuracy, and maintain compliance.

Prerequisites

None — utility skill, run anytime. Most effective after Phase 1 (analyze) to understand the entity's operations and risk areas.

Process

  1. Assess control environment:

    • What processes handle cash, inventory, payroll, and financial reporting?
    • Where are the highest-risk areas for errors or fraud?
    • What controls currently exist (if any)?
    • What is the entity's size and complexity?

  2. Design preventive controls:

    • Segregation of duties — separate authorization, custody, and recording
    • Authorization controls — approval limits and signing authority
    • Physical controls — locks, safes, restricted access, inventory counts
    • IT controls — access permissions, password policies, audit logs
    • Documentation — standardized forms, sequential numbering, required fields

  3. Design detective controls:

    • Reconciliations — bank reconciliation, intercompany, sub-ledger to GL
    • Reviews — management review of reports, exception reports
    • Audits — internal audit schedule, surprise counts
    • Variance analysis — budget vs. actual monitoring

  4. Map controls to risks:

    • For each identified risk, assign one or more controls
    • Classify controls by type (preventive/detective) and frequency (daily/weekly/monthly/annual)
    • Identify any gaps where risks lack adequate controls

  5. Write the artifact to .metapowers/accounting/$ARGUMENTS/controls.md with sections:

    • Control Environment Assessment — current state and risk areas
    • Control Matrix — risks mapped to controls with type, frequency, and owner
    • Implementation Plan — priority order for implementing new or improved controls
    • Monitoring — how to verify controls are operating effectively

Output

The controls design written to .metapowers/accounting/$ARGUMENTS/controls.md. Present a summary highlighting:

  • Number of controls designed by type
  • Highest-risk areas and their mitigating controls
  • Implementation priorities

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.