accounting

Process receipts, track expenses in Google Sheets, reconcile records, and generate entertainment supplement tables for Field Museum procurement card accounting

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%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 content is a highly actionable, well-sequenced workflow with strong validation checkpoints and clean one-level-deep reference structure; the only notable weakness is some repetition of the fee-posting-after-close rationale that could be consolidated.

Suggestions

Consolidate the 'fee posts just after statement close' explanation, which is restated in step 1.3 branches (b), (d), (e) and Phase 3 step 4, into a single canonical note referenced where needed.

Consider moving the long international-fee branch tree (a)-(e) detail into references/smartdata_reports.md with a short decision summary inline, to keep SKILL.md closer to an overview.

Dimension	Reasoning	Score
Conciseness	The body is dense with domain-specific procedural knowledge Claude would not know (the 1% international fee, pairing rules, the expenses-CSV recipe) with no padding of concepts Claude already knows, but the 'fee posts just after statement close' rationale is restated across step 1.3 branches (b), (d), (e) and Phase 3 step 4, so minor trimming is possible.	4 / 5
Actionability	It provides copy-paste-ready commands (curl, python3 invocations, open -a Chrome), concrete Google Sheets CSV export URLs, an exact receipt-numbering format, a full 10-column expense table with how-to-determine guidance, and explicit paste instructions, fully covering the common cases.	5 / 5
Workflow Clarity	Five numbered phases with a structured Session Start, explicit validation checkpoints (confirm year, confirm spreadsheet, confirm-before-rename in Step 1.6), feedback loops (script validation.ok=false → continue treating fee as unconfirmed; failed fetch → ask user), and a status-report checklist (step 8) match the clear-sequence-with-validation anchor.	5 / 5
Progressive Disclosure	The SKILL.md overview holds the workflow while reference data is split into well-signaled, one-level-deep files — references/gl_codes.md, references/supplement_guide.md, references/smartdata_reports.md — all of which exist, and the 'Available Resources' section provides clear navigation to them.	5 / 5
	Total	19 / 20 Passed

Description

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

The description is specific and distinctive with a clear niche, but it omits any explicit 'when to use' trigger guidance and is missing several natural trigger synonyms, capping completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when processing p-card receipts, reconciling charges, checking fund/budget balances, or generating entertainment supplement tables.'

Add natural synonyms users actually say — 'p-card', 'procurement card', 'budget', 'fund', 'GL code' — to broaden trigger coverage.

Keep the third-person voice but consider naming the spreadsheet artifact (Google Sheets) earlier alongside 'expenses' to sharpen the trigger.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — 'Process receipts', 'track expenses in Google Sheets', 'reconcile records', and 'generate entertainment supplement tables' — covering the full workflow comprehensively, matching the score-5 anchor of multiple specific concrete actions.	5 / 5
Completeness	It clearly states what the skill does but includes no 'Use when...' clause or equivalent explicit trigger guidance, so per the cap a clear 'what' with no 'when' lands at 3 rather than higher.	3 / 5
Trigger Term Quality	Contains natural domain terms (receipts, expenses, Google Sheets, reconcile, procurement card, accounting) but lacks common synonyms a user might say — 'p-card', 'budget', 'fund', 'GL code' — and any file extensions, so it sits just below comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	'Field Museum procurement card accounting' carves out a narrow, distinctive niche with minimal overlap risk against other skills, matching the clear-niche anchor.	5 / 5
	Total	17 / 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: brunoasm/my_claude_skills
Path: accounting/SKILL.md
Commit: 5bdff99

Reviewed: 6 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.