CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

accrual-schedule

Build the period-end accrual schedule — for each accrual, compute the entry, cite the support, and draft the JE. Use during month-end close; the JE is a draft for controller approval, not a posting.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is accrual-schedule in anthropics/financial-services

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary compact instruction skill: dense, policy-specific, and honest about safety boundaries (untrusted inputs, draft-only JE). The remaining gaps are minor — a worked example and an explicit tie-out/balance check would complete it.

Suggestions

Add a one-row worked example with real numbers (basis, period portion, already booked, resulting accrual) to make the derivation table fully copy-paste-ready.

Add a validation checkpoint before output, e.g. "Confirm each JE's Dr equals Cr and each this-period accrual ties to the schedule rows".

Clarify the deferred formula path — state how to resolve "or the policy's specific formula" when the policy list defines a non-standard calculation.

DimensionReasoningScore

Conciseness

The 33-line body is lean and assumes competence: a field-derivation table, a JE template, and firm-specific policy (untrusted invoices, auto-reversing memos, do-not-post) that Claude cannot already know. No concept explanations or padding; every token earns its place.

5 / 5

Actionability

Concrete per-field derivations ("Basis × (days in period ÷ days in basis period)"), an exact Dr/Cr/memo template, and an explicit data source ("from internal-gl MCP") make the guidance mostly executable. Minor gaps: no worked numeric example, and "or the policy's specific formula" defers one calculation path.

4 / 5

Workflow Clarity

The sequence is clear — derive fields per accrual, draft JEs for non-zero rows, output schedule plus JE block — with an explicit control ("Do not post — this is staged for controller sign-off"). It is a draft-only (non-destructive) skill, so the batch-cap does not apply, but validation is thinner than the top anchor: no tie-out/reconciliation check against GL totals and no Dr-equals-Cr confirmation.

4 / 5

Progressive Disclosure

Under 50 lines, no external references needed, and well-organized sections (derivation table, JE draft, output). No bundle files exist and none are referenced, so per the simple-skill note the well-organized single file matches the top anchor.

5 / 5

Total

18

/

20

Passed

Description

78%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: third-person, concrete, and honest about scope (draft-only, controller sign-off). Its only weakness is a single narrow trigger phrase and a few missing natural synonyms, which leave completeness and trigger coverage just short of the top anchors.

Suggestions

Broaden the "when" clause to cover adjacent trigger situations, e.g. "Use during month-end close or when asked to prepare accrual entries / accrued-expense JEs".

Spell out "journal entry" at least once alongside "JE" so users who don't use the abbreviation still match.

Add one or two natural synonyms such as "closing entries" or "accrued expenses" to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

"Compute the entry, cite the support, and draft the JE" lists several concrete actions on a named deliverable ("period-end accrual schedule"), but coverage has minor gaps — basis calculation and reversing-entry handling are not mentioned. Not the 5 anchor's comprehensive coverage, but well above 1–2 concrete actions.

4 / 5

Completeness

Both parts are explicit: the "what" (compute entry, cite support, draft JE) and the "when" ("Use during month-end close"), plus a scope boundary ("not a posting"). Sits between anchors 4 and 5 — the "when" clause is explicit but single-scoped and could name additional trigger situations, so 4 is the better fit.

4 / 5

Trigger Term Quality

Natural close-process phrases are present ("period-end", "accrual schedule", "month-end close", "JE", "controller approval"), matching the good-keyword-coverage anchor. A few natural synonyms are missing — "journal entry" spelled out, "closing entries", "accrue expenses".

4 / 5

Distinctiveness Conflict Risk

"Period-end accrual schedule" scoped to "month-end close" is a clear accounting niche with distinct triggers and minimal overlap risk with generic document or bookkeeping skills. Matches the clear-niche anchor.

5 / 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/financial-services

Path

plugins/vertical-plugins/fund-admin/skills/accrual-schedule/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.