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.

73

Quality

92%

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

92%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: concrete commands, explicit blocking gates that serve as validation checkpoints, and clean separation of overview from reference detail. The only slack is minor duplication between the gates and Hard rules sections and a slightly padded intro.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, but 'Hard rules' partially duplicates the gates (gate 4's preparer/reviewer segregation restated as 'a key control with no reviewer or reviewed by its preparer'), and the three-sentence motivational intro ('A slow close is rarely slow everywhere...') could be trimmed to one.

4 / 5

Actionability

Fully executable copy-paste commands with realistic example values ('--gl-balance 52708.60 --source-balance 47144.72 --as-of 2026-10-31 --preparer Sam --reviewer Lee'), an exit-code table per script, and noted '--sample' and '--output json' flags cover the common cases.

5 / 5

Workflow Clarity

The three steps are numbered, commented, and each explained, with an explicit validation checklist ('The gates block on (exit 4)') and remediation guidance for failures (unmatched source-only items mean 'book a journal entry'; stale differences 'point back to last month's reconciliation').

5 / 5

Progressive Disclosure

The body is a pure overview (workflow, gates, rules, script table) with clearly signaled one-level-deep references, each annotated with its content ('task order, critical path, days-to-close benchmarks...'), and input formats split into assets.

5 / 5

Total

19

/

20

Passed

Description

92%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 when-clause with concrete trigger situations, third-person capability statements covering the full workflow, and a distinct accounting-close niche. Only minor synonyms are missing from an otherwise strong trigger vocabulary.

DimensionReasoningScore

Specificity

Multiple concrete actions with comprehensive coverage of the close domain: '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'. Not 4 — coverage has no significant gaps.

5 / 5

Completeness

Explicitly answers both: 'Use when running, planning or speeding up a month-end (or quarter-end) close' (when) and the concrete capability list plus 'Orders close tasks by dependency and finds the critical path, proves each reconciliation and ages what is left' (what).

5 / 5

Trigger Term Quality

Good natural coverage — 'month-end (or quarter-end) close', 'close checklist', 'reconciling a bank statement', 'flux (variance) explanations' — with synonym glosses. Not 5: a few common natural phrases users would say are missing ('close the books', 'account reconciliation', 'financial close').

4 / 5

Distinctiveness Conflict Risk

A clear niche — running the accounting close itself with reconciliations, flux review, and close-calendar critical path — that is unlikely to capture requests meant for generic planning, financial-analysis, or document skills.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 8 missing

Warning

referenced_paths_exist

Referenced path issues: 22 missing

Warning

Total

13

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/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.