recurring-transaction-builder
Skill2 starsChanged 3 months agoAGPL-3.0View on GitHub
Designs and validates recurring journal entries, bills, invoices and subscription schedules: computes every future occurrence (calendar rolls, escalations, memo variables), checks each account, counterparty and tax code against the live chart, checks whether the recurrence already exists, finds manually repeated transactions worth automating, and audits whether existing recurring entries actually ran. Reads the chart, counterparties, tax codes and posting history through a connected Mosofin workspace when the user agrees, or works from details the user supplies. Use when the user asks to set up a recurring entry or bill, generate the next 12 months of entries, automate a monthly entry, build a subscription invoice template, check whether a recurring entry ran, or asks what to automate. Do not use for one-off entries (use journal-entry-builder) or prepaid amortization (use prepaid-amortization-schedule). Read-only: produces a schedule specification for a person to load, and creates, posts or schedules nothing.
In this repository30 other files it gives its agents.
- accruals-and-deferralsSkill
- ap-accrual-cutoffSkill
- ap-aging-and-payment-runsSkill
- ar-aging-and-collectionsSkill
- balance-sheet-reconciliationsSkill
- bank-reconciliationSkill
- budget-vs-actual-analysisSkill
- cash-applicationSkill
- cash-flow-forecast-13-weekSkill
- closing-entries-and-trial-balanceSkill
- credit-card-reconciliationSkill
- credit-memo-and-refund-handlerSkill
- customer-invoicingSkill
- duplicate-invoice-detectionSkill
- expense-report-processorSkill
- financial-statement-builderSkill
- fixed-asset-register-and-depreciationSkill
- gl-coding-assistantSkill
- inventory-to-gl-reconciliationSkill
- invoice-data-extractorSkill
- journal-entry-builderSkill
- journal-entry-reviewSkill
- merchant-and-payment-processor-recSkill
- month-end-close-checklistSkill
- payroll-clearing-reconciliationSkill
- payroll-journal-entry-builderSkill
- payroll-reconciliationSkill
- prepaid-amortization-scheduleSkill
- three-way-matchSkill
- vendor-statement-reconciliationSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

