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

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

93%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 concise, actionable accrual-schedule skill with a clear derivation table and a usable JE template, plus an explicit do-not-post safety boundary. The only gap is an explicit validation/feedback loop for edge cases like zero or negative accruals.

Suggestions

Add an explicit checkpoint for edge cases, e.g. 'If this-period accrual is zero or negative, note it and skip the JE; flag for controller review if it contradicts prior-period patterns.'

Dimension	Reasoning	Score
Conciseness	Lean table-driven body that assumes Claude's accounting competence; no padding or explanation of concepts Claude already knows, and every token earns its place.	5 / 5
Actionability	Provides a concrete field-by-field derivation table with explicit formulas (e.g. Basis × (days in period ÷ days in basis period)) and a copy-paste-ready JE template covering the common case.	5 / 5
Workflow Clarity	Clear per-accrual sequence and output spec, and it explicitly marks the JE as a draft not to be posted (a validation/safety checkpoint); however there is no explicit feedback loop for handling negative or zero accruals or re-derivation on error.	4 / 5
Progressive Disclosure	A short, single-purpose, under-50-line skill with well-organized sections and no need for external references; per the simple-skills note this scores 5.	5 / 5
	Total	19 / 20 Passed

Description

88%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 highly specific, well-scoped accounting skill description that clearly states both capabilities and the month-end-close trigger context. Trigger-term coverage is strong but could add a couple of natural synonyms for full marks.

Suggestions

Add a few natural synonyms users might say, e.g. 'Use when closing the books, computing period-end accruals, or drafting adjusting entries at month-end.'

Dimension	Reasoning	Score
Specificity	Names the domain (accrual schedule) and lists multiple concrete actions — compute the entry, cite the support, draft the JE — with comprehensive coverage of the workflow.	5 / 5
Completeness	Explicitly answers both what (build the accrual schedule; compute entry, cite support, draft JE) and when ('Use during month-end close') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('month-end close', 'accrual schedule', 'JE', 'controller approval'), but lacks synonyms or explicit period-end close variations a user might voice.	4 / 5
Distinctiveness Conflict Risk	Clear niche (period-end accrual schedule / draft JEs for controller approval) with distinct accounting-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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/agent-plugins/month-end-closer/skills/accrual-schedule/SKILL.md
Commit: 69cbc81

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.