CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

journal-entry-prep

Prepare journal entries with proper debits, credits, and supporting documentation for month-end close. Use when booking accruals, prepaid amortization, fixed asset depreciation, payroll entries, revenue recognition, or any manual journal entry.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./finance/skills/journal-entry-prep/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

The body is a well-organized accounting reference with genuinely useful operational content (checklists, approval thresholds, error catalog), but it is held back by inline re-explanations of standard accounting knowledge, no sequenced preparation workflow, no worked examples, and no progressive disclosure via bundle files despite its length.

Suggestions

Trim sections that restate knowledge Claude already has (depreciation method definitions, the ASC 606 five steps, prepaid category examples) down to one-line pointers, keeping only the operational considerations.

Add a sequenced month-end workflow (identify accruals → calculate → prepare entry with documentation → route per approval matrix → reviewer runs checklist) so validation checkpoints are embedded in the process order rather than scattered across sections.

Move the per-entry-type detail into references/ files (e.g., accruals.md, depreciation.md) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links, which would also let the body shed its inline bulk.

DimensionReasoningScore

Conciseness

The operational content (documentation requirements, approval matrix, review checklist, error list) earns its place, but several sections re-explain knowledge Claude already has: the straight-line formula and method definitions under "Depreciation methods", the enumerated "ASC 606 five-step framework", the "Common prepaid categories" list, and definitional intros like "Accrue for goods or services received but not yet invoiced at period end". This is over the score-4 bar (more than minor trimmable over-explanation) but not the heavily padded score-2 level, since most sections carry non-derivable procedural guidance.

3 / 5

Actionability

Guidance is concrete and usable: explicit debit/credit skeletons per entry type, a threshold-based approval matrix, a 12-item review checklist, and an enumerated error list. For an instruction-only skill this is mostly actionable with a minor gap — there is not a single worked example (e.g., a sample salary accrual calculation with working days or a filled-out memo), so it stops short of the fully-executable score-5 anchor while clearly exceeding the incomplete score-3 anchor.

4 / 5

Workflow Clarity

The sections are topical, not sequenced — there is no explicit preparer workflow (identify needed entries → calculate → prepare with documentation → submit per approval matrix → reviewer validates). Validation exists (the review checklist and common-errors list are checkpoints) but is embedded in separate sections rather than sequenced, and journal posting is a consequential batch-style operation, so the score is capped at 3 per the missing-sequenced-validation guideline.

3 / 5

Progressive Disclosure

There are no bundle files at all (no references/, scripts/, or assets/ exist), so all ~180 lines of detail live inline in SKILL.md. Headers organize it well, but entry-type deep-dives that could be separate reference files are inlined, and there are no reference pointers of any kind — matching the score-3 anchor of good structure with content that could be split out left inline, and falling short of the score-4 anchor's appropriately split content with clear references.

3 / 5

Total

13

/

20

Passed

Description

83%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.

A strong description that explicitly states what the skill does and when to use it, with concrete, natural trigger terms from the accounting domain. It falls just short of top marks on specificity and trigger coverage due to a few missing synonyms and its single-task framing.

DimensionReasoningScore

Specificity

"Prepare journal entries with proper debits, credits, and supporting documentation for month-end close" lists several concrete actions (debits/credits, supporting documentation, month-end close), but coverage stays within a single task rather than multiple distinct actions like the score-5 anchor. It is well above the minimal/generic level of scores 2-3 because every named action is concrete and domain-grounded.

4 / 5

Completeness

Both questions are explicitly answered: the "what" ("Prepare journal entries with proper debits, credits, and supporting documentation for month-end close") and the "when" with concrete trigger phrases ("Use when booking accruals, prepaid amortization, fixed asset depreciation, payroll entries, revenue recognition, or any manual journal entry"). This mirrors the score-5 anchor structure and cannot be score 4, since the "when" clause is already explicit and specific.

5 / 5

Trigger Term Quality

"Use when booking accruals, prepaid amortization, fixed asset depreciation, payroll entries, revenue recognition, or any manual journal entry" covers the natural phrases an accounting user would say, plus "month-end close". A few common variations are missing (e.g., "general ledger", "JE", "closing entries"), so it falls just short of the comprehensive synonym coverage of the score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The journal-entry/month-end-close niche is clear and distinct from most skills, with domain-specific triggers (accruals, prepaid amortization, revenue recognition). Minor overlap risk remains with closely related finance skills (e.g., account reconciliation or a broader close-checklist skill), and "any manual journal entry" is broad within that domain, so it is mostly distinct rather than a clear minimal-conflict niche.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

anthropics/knowledge-work-plugins

Path

finance/skills/journal-entry-prep/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.