closing-entries-and-trial-balance
Skill2 starsChanged 3 months agoAGPL-3.0View on GitHub
Prepares the year-end closing entries that empty revenue, expense, gain and loss accounts and dividends, distributions or draws into retained earnings (or owner or member capital), and produces or audits the pre-closing and post-closing trial balance with retained-earnings tie-outs. Before proposing any entry it tests whether the platform has already closed the year, so retained earnings is never closed twice. Reads the trial balance, account types and equity through a connected Mosofin workspace when the user agrees, or works from an uploaded trial balance and chart of accounts. Use when the user asks to close the books for the year, prepare closing entries, roll income to retained earnings, produce a final or post-closing trial balance, check why a TB does not balance, or uploads a TB to review. Do not use for monthly close orchestration (use month-end-close-checklist). Read-only: produces proposed closing entries, trial balances, a tie-out workpaper and a coverage sheet, posts nothing and locks no period.
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
- 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
- recurring-transaction-builderSkill
- three-way-matchSkill
- vendor-statement-reconciliationSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 372,429 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.

