journal-entry-builder
Skill2 starsChanged 3 months agoAGPL-3.0View on GitHub
Builds balanced, import-ready journal entries for any accounting event — standard, accrual, deferral, adjusting, correcting, reclass, reversing, intercompany or closing — against the entity's real chart of accounts, and validates each one: debits equal credits, every account exists, signs match account types, the period is open, and no open accrual, open invoice or control account makes the entry wrong. Reads the books through a connected Mosofin workspace when the user agrees, or works from an uploaded chart of accounts, trial balance or GL export. Use when the user says 'book a JE for…', 'create a journal entry to record…', 'how do I record this transaction', 'make me an accrual JE', 'reclass these entries' or 'reverse this entry', or asks for an import-ready JE file. Do not use for GL coding decisions only (use gl-coding-assistant) or a full period close (use month-end-close-checklist). Read-only: produces proposed entries with narration, validation results and a coverage sheet, and posts 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-reviewSkill
- merchant-and-payment-processor-recSkill
- month-end-close-checklistSkill
- payroll-clearing-reconciliationSkill
- payroll-journal-entry-builderSkill
- payroll-reconciliationSkill
- prepaid-amortization-scheduleSkill
- recurring-transaction-builderSkill
- three-way-matchSkill
- vendor-statement-reconciliationSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 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.
3
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.

