Create a reusable accounting skill
A skill is reusable instructions for a procedure: when to use it, what to check, and what to return. It is not client-data memory and it does not replace your review.
The most reliable way to make one is to guide an AI app through the workflow once, correct its assumptions, and note the questions it should ask.
Turn a completed workflow into a skill
Section titled “Turn a completed workflow into a skill”At the end of a successful run, ask the app:
Turn the workflow we just completed into a reusable accounting skill named [skill name]. Include its inputs, steps, checks, output, stop conditions, and approval boundaries. Keep credentials and access tokens out of the skill. If this skill is for one client or company, you can name it or refer to its saved connection; if you plan to share the skill, make the client or company a clearly named input instead. Describe records and examples without copying real accounting data.
The app should turn the conversation into a procedure you can review. If it cannot create a skill directly, ask for instructions in a supported format.
Claude and Codex support reusable skills; availability and controls vary by product and workspace. See Claude’s skill guide and OpenAI’s skill guide for ChatGPT and Codex.
What a good skill contains
Section titled “What a good skill contains”- A clear trigger. Describe the accounting question or procedure, not a vague goal such as “help with month end.”
- Named inputs. Specify the company, period, accounts, thresholds, and files to provide.
- A fixed procedure. List the reports, records, comparisons, and checks in order.
- Stop conditions. Pause for a missing company, unsupported field, conflicting record, or human judgment.
- A review gate. Require a proposal and approval before any step can change data.
- A useful output. Define the summary, exceptions, evidence, or proposed changes to return.
Test before sharing
Section titled “Test before sharing”- Run it against a known period or safe test company and confirm the workspace and company.
- Check that its read-only findings match the accounting platform.
- Ask for a proposed change without approving it, then revise the stop conditions and output.
Keep the skill provider-neutral when the procedure can work across platforms. If it depends on a QuickBooks Online report or field, say so in the skill and link to QuickBooks Online: capabilities and limits.
Keep skills safe to share
Section titled “Keep skills safe to share”Client and company details are allowed when they are part of the skill’s intended scope. For a private skill, name the client or company—or refer to its saved connection—when that makes the procedure clearer. For a shared skill, make the client or company an input and confirm the selected workspace and company at the start. Keep credentials and access tokens in the connected workspace, not in the skill, and use sanitized examples instead of copied accounting records.
Share a skill only after you have reviewed its instructions. A skill can make a powerful workflow easier to repeat, but it should never silently broaden a person’s workspace access or remove the approval step for a write.