CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

month-end-close

Use when running, planning or speeding up a month-end (or quarter-end) close — building or reviewing the close checklist and calendar, reconciling a bank statement or sub-ledger to the general ledger, writing or reviewing flux (variance) explanations, or finding why the close takes too many days. Orders close tasks by dependency and finds the critical path, proves each reconciliation and ages what is left, and refuses to sign off material fluctuations explained with boilerplate.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is month-end-close in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered skill body: lean, concrete, and self-verifying through blocking exit codes and an enumerated gate checklist, with an appropriately split bundle and clear navigation. The only notable gap is the absence of an explicit fix-and-re-run feedback loop around the exit-4 gates.

Suggestions

Add one line after the gates section stating the recovery loop explicitly, e.g. 'On exit 4, fix the listed condition (assign an owner, book the entry, quantify the explanation) and re-run — exit 0 is the only pass.'

Align the workflow example filenames with the shipped example assets (use --plan assets/close_plan.example.json or note that close_plan.json follows assets/close_plan.example.json) so the commands run verbatim against the bundle.

State what exit code 2 ('at risk' / 'items' / 'evidence') means for the user — whether it requires action or is informational — since only exit 4's conditions are enumerated.

DimensionReasoningScore

Conciseness

The ~80-line body is lean and every section is functional: three commands, terse step explanations, a gates checklist, an exit-code table, and an annotated file listing. It assumes Claude's competence — it states this skill's rules and script behavior rather than explaining what a reconciliation or critical path is.

5 / 5

Actionability

All three scripts get fully executable commands with realistic argument values (--gl-balance 52708.60, --as-of 2026-10-31, --pct 10), an exit-code table per script, and a note that all support --sample and --output json, so the common cases are copy-paste runnable.

5 / 5

Workflow Clarity

The three steps are clearly sequenced with one command each, and validation is explicit (numbered blocking gates plus per-script exit codes including '4 blocked'). It falls between anchors 4 and 5 because error recovery is a checklist of conditions rather than a feedback loop — the gates say what blocks but never say 'fix the item and re-run until exit 0'.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with well-signaled, one-level-deep references: the 'References and assets' section annotates each of the three reference files with its scope and source count, and all eight referenced bundle files (references, scripts, assets) exist on disk with no nested reference chains.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: explicit trigger clause with concrete scenarios, third-person statement of capabilities, natural domain terminology with synonyms, and a clearly delineated niche. It matches or exceeds the quality of the good reference examples.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'building or reviewing the close checklist and calendar, reconciling a bank statement or sub-ledger to the general ledger, writing or reviewing flux (variance) explanations', plus 'orders close tasks by dependency and finds the critical path, proves each reconciliation and ages what is left' — giving comprehensive coverage with no vague filler.

5 / 5

Completeness

It opens with an explicit 'Use when running, planning or speeding up a month-end (or quarter-end) close' trigger clause with concrete scenarios, and then explicitly states what the skill does ('Orders close tasks by dependency... proves each reconciliation... refuses to sign off material fluctuations explained with boilerplate'). Both what and when are explicit.

5 / 5

Trigger Term Quality

Natural terms an accounting user would actually say are comprehensively covered: 'month-end (or quarter-end) close', 'close checklist', 'bank statement', 'sub-ledger', 'general ledger', 'flux (variance) explanations' (explicit synonym pairing), and 'finding why the close takes too many days'.

5 / 5

Distinctiveness Conflict Risk

A clear niche — running the accounting close itself — with triggers (close checklist, bank-to-GL reconciliation, flux explanations, close duration) that would not fire for adjacent financial-analysis, SaaS-metrics, or budgeting skills; conflict risk is minimal.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

finance/skills/month-end-close/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.