CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

variance-commentary

Write flux commentary for every P&L and balance-sheet line over threshold — current vs prior period and vs budget, with the driver explained from underlying activity. Use for the month-end close package and management reporting.

Quality

89%

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

The canonical home for this skill is variance-commentary 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.

A lean, well-structured single-purpose skill with concrete threshold logic, an explicit output schema, and a good anti-fabrication fallback. Its only weaknesses are the undefined 'fixed floor' default and the absence of a numeric verification step.

Suggestions

Give the 'fixed floor' a concrete default value (or state that commentary is skipped if no materiality figure is provided) so the threshold rule is fully executable.

Add a verification step — recompute Δ amounts and percentages from the three values and confirm the flagged set matches the threshold — before writing the table.

Include a short worked example of the commentary table (one filled row) so the column schema is unambiguous in practice.

DimensionReasoningScore

Conciseness

Every section earns its place: the threshold rule, the column schema, a good/bad driver example, sourcing guidance, and the output spec — with zero padding and no explanation of concepts Claude already knows. Matches the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Guidance is concrete: exact flag logic with a default ('default 5% of the line or a fixed floor'), an explicit table schema, an example driver sentence, and a fallback phrase ('driver unclear — flag for controller'). The unspecified 'fixed floor' value keeps it from fully-executable 5, but it is well above the 3-anchor's pseudocode level.

4 / 5

Workflow Clarity

The sequence is clear and ordered (apply threshold → source driver via internal-gl MCP → build table → narrative) with an explicit error-recovery fallback for unclear drivers. It lacks a numeric verification step (e.g., recomputing Δ amounts/percentages before writing), which is the minor validation gap of the 4-anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references, and no bundle files exist; sections (Threshold, For each flagged line, Sourcing the driver, Output) are well organized. Per the simple-skill guideline this scores 5.

5 / 5

Total

18

/

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 with an explicit what-and-when structure and domain-specific trigger terms. Its only gaps are the missing common synonym 'variance' and the unspecified output format.

Suggestions

Add 'variance' to the description (e.g., 'variance/flux commentary') so users who say 'explain the variance' or 'variance analysis' trigger the skill.

Mention the output form (commentary table plus a short narrative) so the what is fully comprehensive.

DimensionReasoningScore

Specificity

The description states concrete scope and mechanics — 'for every P&L and balance-sheet line over threshold', 'current vs prior period and vs budget, with the driver explained from underlying activity'. It describes one task with several specific components rather than the multiple distinct actions of the 5-anchor, and the output format (table + narrative) is unstated, so it sits at 4.

4 / 5

Completeness

Both halves are explicit: the what ('Write flux commentary for every P&L and balance-sheet line over threshold — current vs prior period and vs budget, with the driver explained') and the when ('Use for the month-end close package and management reporting'), matching the 5-anchor pattern.

5 / 5

Trigger Term Quality

Good natural finance keywords: 'P&L', 'balance-sheet', 'budget', 'month-end close package', 'management reporting'. It misses the most common synonym 'variance' (the skill's own body title is 'Variance commentary'), so it falls short of the comprehensive synonym coverage of the 5-anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche — flux/variance commentary for the close package — with distinct finance-specific triggers; minimal overlap risk with generic reporting or spreadsheet skills.

5 / 5

Total

18

/

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/variance-commentary/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.