Claude Cowork walkthrough

Build a finance plugin in Claude Cowork with your own slash commands

Every new AI chat starts with you explaining your chart of accounts again. A Cowork plugin fixes that: your role, accounts, workflows and safety rules live in one package, and /monthly-close runs the process your way. This walkthrough builds one from a template.

▶ Interactive · 8 steps5 minFor controllers, FP&A and accounting teams
Click through it. Use Next, the arrow keys or the dots. Orange boxes show where to look.Expand ⤢ for full screen

Illustrative recreation of the Claude Cowork desktop app with fictional sample data. Not the actual product; screens and labels can change as Cowork ships updates.

Eight screens from template to statements

Fill the template, create the plugin, check its commands and skills, run it, review the output.

  1. Know what a plugin holds

    Commands are workflows you trigger with a slash; skills are the standards those workflows follow.

  2. Fill in the plugin-builder template

    Role, tools, fiscal year, currency, number format and chart of accounts ranges.

  3. Define each workflow step by step

    Matching rules, tolerances, thresholds and outputs for each slash command.

  4. Add connectors and safety rules

    Which systems it may touch, plus never-post, never-delete and stop-and-ask rules.

  5. Create with Claude, then review commands

    Paste the prompt into Create with Claude, install the plugin and read each command.

  6. Encode your formats in skills

    Sign conventions, required layouts and critical checks live in the skills.

  7. Launch a command

    Set the working folder, then + > Plugins or / to pick a command.

  8. Review the statements and checks

    Confirm the balance check, the tie-outs and the verification tab, then improve the plugin.

How JayOh builds these

Process first, plugin second

We document the real close (accounts, steps, tolerances, approvals) before writing a single skill. That documentation is worth having even without AI. Related: RevOps for finance.

  • Process mapping. We write down the close as it actually runs, including the exceptions.
  • Plugin build. Commands per workflow, skills per standard, connectors scoped read-only.
  • Sample-data testing. Every command proven on redacted files first.
  • Iteration loop. Each close feeds fixes back into the skills.
Guardrails we set first

Keep a human in the loop

  • Never auto-post to the ledger or send outside finance.
  • Never delete source files.
  • Stop and ask when data looks incomplete.
  • Everything is a draft until a person approves it.
8screens in this walkthrough
3commands in the sample plugin
76.2%illustrative gross margin
0balance check difference

Common questions

Short answers before you set this up.

What is a Claude Cowork plugin?

A plugin packages slash commands (your workflows), skills (your standards and rules) and connectors into one installable unit, so Cowork runs a process your way without re-explaining it each time.

How do I create a plugin in Cowork?

Write a structured prompt describing your role, systems, workflows and safety rules, then use Plugins > + > Create with Claude. Claude produces a plugin file you upload and install, and you can edit its commands and skills afterwards.

Can a Cowork plugin post journal entries?

It can propose them. We recommend safety rules that forbid auto-posting and connector permissions that keep ERP write tools on needs-approval, so a person always posts.

Do I need fake data to start?

It is the safest way to begin. Build and test the plugin on redacted or synthetic files, then point it at real folders once results are consistent.

Want a close plugin built around your process?

JayOh maps your close, builds the Claude plugin and skills, and tests them on sample data before they touch your books.

Talk to JayOh