CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

journal-entry

Prepare journal entries with proper debits, credits, and supporting detail. Use when booking month-end accruals (AP, payroll, prepaid), recording depreciation or amortization, posting revenue recognition or deferred revenue adjustments, or documenting an entry for audit review.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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-structured, domain-appropriate instruction skill: concrete per-type debit/credit guidance, an explicit output template, and a real validation checklist. It stays lean by not re-teaching accounting basics, but falls just short of top marks for lacking a worked numeric example, an explicit error-recovery loop after the checklist, and a few cleanliness issues (strikethrough placeholders, redundant intro).

Suggestions

Add an explicit error-recovery step after the review checklist, e.g., "If any check fails, correct the entry and re-run the full checklist before presenting" — this closes the workflow feedback loop and would justify a 5 on workflow clarity.

Include one short worked example with numbers (e.g., straight-line depreciation of a single asset for one month) so the calculation guidance is fully concrete.

Fix the stray strikethrough placeholders ("~~erp or ~~data warehouse") and remove the opening sentence that duplicates the frontmatter description, tightening conciseness.

DimensionReasoningScore

Conciseness

The body is lean: it does not re-explain accounting concepts Claude already knows (what depreciation or deferred revenue is), instead listing only task-specific steps and an output template. Minor trims are possible — the opening line "Prepare journal entries with proper debits, credits, supporting detail, and review documentation" repeats the frontmatter description, and stray strikethrough artifacts ("If ~~erp or ~~data warehouse is connected") add noise. Not 5 due to these small redundancies; not 3 because there is no padded or unnecessary explanation.

4 / 5

Actionability

Concrete, instruction-specific guidance throughout: per-entry-type debit/credit mappings (e.g., "Debit: Depreciation expense (by department/cost center) / Credit: Accumulated depreciation"), and a copy-paste-ready journal entry table template with defined columns plus a supporting-detail and reversal block. Not 5 because the calculation steps ("Calculate accrual amounts from PO receipts, contracts, or estimates") lack a single worked numeric example; not 3 because the guidance is specific and executable, not pseudocode.

4 / 5

Workflow Clarity

A clear five-step sequence (Gather Source Data, Calculate the Entry, Generate the Journal Entry, Review Checklist, Output) with an explicit 11-item validation checkpoint ("Before finalizing, verify: Debits equal credits ..."), which is a genuine validation step rather than an implicit one. Not 5 because there is no explicit error-recovery loop (nothing says what to do when a checklist item fails, e.g., fix and re-verify); not 3 because checkpoints are explicit, not missing. The destructive/batch cap does not apply since the skill prepares entries for review rather than posting them.

4 / 5

Progressive Disclosure

A single-file skill (~130 lines) with well-organized sections (Usage, Arguments, Workflow with five numbered subsections) and no bundle files to score against; nothing is deeply nested or buried. Not 5 because the file exceeds the simple-skill threshold and the per-type calculation details (five entry types) sit inline where they could be offloaded to reference files, and the [CONNECTORS.md](../../CONNECTORS.md) reference points outside the skill directory and cannot be verified; not 3 because structure is clear and navigation is easy.

4 / 5

Total

16

/

20

Passed

Description

87%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: concise third-person statement of what the skill does, followed by an explicit and specific 'Use when...' clause covering five realistic entry-type triggers. The only gaps are a few natural synonyms (month-end close, GL, JEs) and the omission of review-documentation capabilities that the body actually delivers.

Suggestions

Add one or two common synonyms such as "month-end close" or "general ledger (GL)" to the when-clause to broaden natural trigger coverage.

Mention that the skill also produces supporting calculations and audit-review documentation, since that capability is a core part of the body workflow.

DimensionReasoningScore

Specificity

"Prepare journal entries with proper debits, credits, and supporting detail" names the domain plus several concrete action components, and the when-clause enumerates five concrete entry types ("month-end accruals (AP, payroll, prepaid)", "depreciation or amortization", "revenue recognition or deferred revenue adjustments", "documenting an entry for audit review"). Not 5 because the what is a single action with components rather than a list of multiple distinct capabilities (review documentation and prior-period comparison from the body are absent); not 3 because coverage goes well beyond 1-2 generic actions.

4 / 5

Completeness

Explicitly answers both: what ("Prepare journal entries with proper debits, credits, and supporting detail") and when ("Use when booking month-end accruals ... or documenting an entry for audit review") with a list of concrete trigger scenarios. This matches the anchor-5 example structure of clear what followed by an explicit 'Use when...' clause with concrete triggers; the when-clause is present and highly specific, ruling out 4.

5 / 5

Trigger Term Quality

Uses natural phrases an accountant would actually say: "month-end accruals", "payroll", "prepaid", "depreciation or amortization", "revenue recognition", "deferred revenue", "debits, credits", "audit review". Not 5 because common variations like "month-end close", "general ledger"/"GL", "JEs", or "journal entry" (singular) are missing; not 3 because keyword coverage is good and domain-natural, not just "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

Clear accounting niche with distinct triggers (accruals, depreciation, deferred revenue, audit documentation) that are unlikely to fire for unrelated skills. Third-person voice ("Prepare journal entries") is used correctly. Minimal overlap risk with any general bookkeeping or document skill.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 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: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

anthropics/knowledge-work-plugins

Path

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