CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reconciliation

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

Quality

79%

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/reconciliation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 methodology reference with concrete templates, categorization rules, and escalation thresholds that make it genuinely actionable. Its weaknesses are mild redundancy explaining standard accounting concepts, no explicit re-verification feedback loop after adjustments, and no progressive disclosure — all content is packed into one long file with no references.

Suggestions

Trim definitions of concepts Claude already knows (outstanding checks, deposits in transit, basic bank rec mechanics) and remove the opening paragraph that duplicates the frontmatter description, keeping only the value-add categorization, aging, and escalation frameworks.

Move the per-reconciliation-type deep dives, aging report format, and escalation threshold tables into one-level-deep reference files (e.g., references/bank-rec.md, references/aging.md), leaving SKILL.md as a concise overview with clearly signaled links.

Add an explicit validation feedback loop: after preparing an adjusting entry for a Category 2 item, re-run the GL-to-subledger or bank comparison and confirm the difference reaches $0.00 before sign-off.

DimensionReasoningScore

Conciseness

The body is mostly efficient structured tables and numbered lists, but it defines textbook concepts Claude already knows (e.g., 'Outstanding checks: Checks issued and recorded in GL, pending bank clearance', 'Deposits in transit: Deposits made and recorded in GL, pending bank credit') and the opening paragraph restates the frontmatter description. The padding is more than minor, so it sits at anchor 3 rather than 4.

3 / 5

Actionability

For an instruction-only skill the guidance is largely concrete: numbered processes per reconciliation type, a copy-paste standard bank reconciliation format template, and tables mapping aging buckets and thresholds to specific actions ('Prepare adjusting journal entry', 'Escalate to management'). Minor gaps — no worked example with real numbers and no commands for pulling balances from an ERP — keep it below anchor 5's fully copy-paste-ready standard.

4 / 5

Workflow Clarity

Each reconciliation type has a clearly sequenced numbered process, and checkpoints exist: the standard format ends in an explicit 'Difference: $0.00' validation target, the escalation table mandates 'Cannot close — must resolve or document' for any unreconciled difference, and aging buckets define follow-up actions. It falls short of anchor 5 because there is no explicit re-verification loop (e.g., re-run the comparison after an adjusting entry) — recovery is implied through 'investigate' rather than a validate-fix-retry cycle.

4 / 5

Progressive Disclosure

The single file is well-organized with clear section headers, but at ~175 lines everything is inlined and no reference files exist — the per-type deep dives, aging report format, and escalation threshold tables could live in one-level-deep reference files per the rubric's rationale that SKILL.md should be an overview pointing to detailed materials. Structure is present but content that should be separate is inline, matching anchor 3; it is above anchor 2 because nothing is buried and the material is usable as a single overview.

3 / 5

Total

14

/

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: it uses third-person imperative voice, names concrete actions with specific data sources, and provides an explicit 'Use when...' trigger clause covering all three reconciliation types. Its only gaps are unmentioned sub-capabilities (aging, escalation) and a few missing trigger synonyms.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'comparing GL balances to subledgers, bank statements, or third-party data' plus 'identifying and categorizing reconciling items' — each tied to specific objects. It falls short of anchor 5 because the skill's body also covers aging analysis, trending, and escalation workflows, none of which the description mentions.

4 / 5

Completeness

It explicitly answers both questions: the first sentence states what the skill does ('Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data') and the second gives an explicit 'Use when...' clause with concrete triggers. This matches the anchor 5 example pattern exactly, so it is not the weaker anchor 4 whose 'when' is only implicit or generic.

5 / 5

Trigger Term Quality

Triggers include natural phrases users would say: 'bank reconciliations', 'GL-to-subledger recs' (including the slang 'recs'), 'intercompany reconciliations', and 'reconciling items'. A few natural variations are missing (e.g., 'month-end close', 'balance sheet reconciliation', 'account rec'), keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The accounting-reconciliation niche is clearly staked out with domain-specific triggers (GL, subledger, intercompany, bank recs) that no general-purpose skill would claim. Minimal conflict risk, matching anchor 5 rather than anchor 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

18

/

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

anthropics/knowledge-work-plugins

Path

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