Skip to content
CodelessOps

CodelessOps · Projects · Skills and plugins

The month-end close, packaged as skills for Claude.

Four skills that run a close inside a standard Claude licence: bank reconciliation, variance report, management pack and a sealed audit binder, with a reviewer gate between every step. The kit is public, MIT licensed, and runs on a fictional company.

This page is short on purpose. The kit works today; the plugin work that builds on it has just started, and I'll add to this page as it ships.

01 · What works today

Say "run the May close", and it runs.

Close checklist

Runs the steps in order. A step that hasn't been signed does not release the next one.

Bank reconciliation

Statement against cashbook, with last month's rec brought forward. Stale items go to a person as a question.

Variance report

Actuals against budget. A script computes every figure, and only the flagged lines get commentary.

Management pack

Fills the pack template from the signed outputs of the first two steps and checks every figure.

The case study The runbook a finance team would receive

02 · The rules it follows

Built so an auditor can follow the work.

The model never computes a figure

Every number comes from a bundled Python script. The model runs the steps, explains them and asks.

In the kit

Nothing moves without a reviewer's initials

Each step stops and presents the output document itself. Judgment calls are put to the person as explicit questions.

In the kit

The audit trail is the point

Every sign-off adds a sealed record to a close log: a hash of the signed file, the reviewer and the time. Close-out compiles the binder from those records.

In the kit

Known answers check the kit

Six checks re-derive the close's key facts from the raw inputs. If a change turns one red, the change is rejected.

In the kit

03 · What I'm building next

From four skills to plugins a team can install.

Join up with Anthropic's finance skills

Start from what Anthropic publishes for finance, and fit my close skills around it.

In progress

One run log for every plugin

A shared directory each plugin writes to, one record per run, so a team can see what ran, what was flagged and who signed.

In progress

Package it as a plugin

One install in place of four uploads, with setup steps a finance team can follow.

In progress

04 · Tried it?

Tell me what it got wrong.

If you run the kit, or your close has a step it doesn't cover, I'd like to hear about it.