CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

excel-variance-analyzer

Analyze budget vs actual variances in Excel with drill-down and root cause analysis. Use when performing variance analysis or explaining budget differences. Trigger with phrases like 'excel variance', 'analyze budget variance', 'actual vs budget'.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 body is a lean, well-organized instruction-only skill with a clear step sequence, a concrete error-handling table, and an appropriately disclosed formulas reference. It is weakened by high-level steps with no inline executable detail, a referenced 'comparison template' that does not exist in assets/, and the absence of validation checkpoints in the workflow.

Suggestions

Ship the 'comparison template' in assets/ (or point step 1 at a concrete section of references/variance-formulas.md) so "Import budget and actual data into comparison template" resolves to a real artifact.

Inline the core formulas (Variance = Actual - Budget, Variance % = (Actual - Budget)/ABS(Budget), and the materiality IF flag) in the Instructions steps, or cite variance-formulas.md at the exact step where each formula is needed rather than only in Resources.

Add an explicit validation step, e.g. after step 5 verify that the waterfall bridge components sum to the total variance and that report totals reconcile to the source budget/actual data, with a fix-and-recheck loop if they do not.

DimensionReasoningScore

Conciseness

The ~50-line body is lean with tight sections (Prerequisites, Instructions, Output, Error Handling, Examples, Resources) and no explanation of concepts Claude already knows; every section carries actionable information, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Instructions like "Apply materiality thresholds for flagging" and "Generate variance waterfall chart" name specific steps but give no inline formulas, commands, or workbook structure (all executable detail is delegated to references/variance-formulas.md), and step 1's "comparison template" has no corresponding file in assets/, matching the 'some concrete guidance but incomplete; missing key details' anchor.

3 / 5

Workflow Clarity

The five-step sequence (import, calculate, flag, drill down, chart) is clearly ordered, but there are no validation checkpoints (e.g., verifying the waterfall bridge reconciles to total variance or totals tie to source data); the Error Handling table is post-failure remediation rather than a workflow checkpoint, matching the 'sequence present but checkpoints missing or implicit' anchor.

3 / 5

Progressive Disclosure

The body is well structured with a clearly signaled, one-level-deep reference ([`references/variance-formulas.md`](references/variance-formulas.md) for calculation templates) that exists in the bundle, matching the 'good structure; references mostly clear; minor organization gaps' anchor; the gaps are the missing 'comparison template' asset referenced in step 1 and placeholder boilerplate READMEs in scripts/ and assets/ that the body never uses.

4 / 5

Total

15

/

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.

The description explicitly and concisely states both what the skill does and when to use it, in third person, with natural trigger phrases and a distinct FP&A niche. Minor gaps remain in keyword synonyms and coverage of the skill's full action set.

DimensionReasoningScore

Specificity

"Analyze budget vs actual variances in Excel with drill-down and root cause analysis" names the domain plus three concrete actions (variance analysis, drill-down, root cause analysis), matching the 'several specific actions; minor gaps' anchor; it is not comprehensive since waterfall charting, materiality flagging, and executive reporting from the body are absent, and it exceeds the 1-2 actions of the score-3 anchor.

4 / 5

Completeness

It clearly answers 'what' ("Analyze budget vs actual variances in Excel with drill-down and root cause analysis") and 'when' ("Use when performing variance analysis or explaining budget differences") with concrete trigger phrases listed, exactly matching the anchor for explicitly answering both what AND when.

5 / 5

Trigger Term Quality

Explicit trigger phrases 'excel variance', 'analyze budget variance', 'actual vs budget' plus 'variance analysis' and 'budget differences' give good natural keyword coverage, but common variations like 'budget vs actual', 'over budget', 'spreadsheet', and '.xlsx' are missing, so it falls short of the comprehensive synonym/extension coverage anchor.

4 / 5

Distinctiveness Conflict Risk

The Excel budget-vs-actual FP&A niche with distinct triggers ('excel variance', 'actual vs budget') is specific and unlikely to fire for unrelated skills, matching the clear-niche/minimal-conflict anchor rather than the minor-overlap anchor (e.g., a generic spreadsheet or charting skill overlap is remote).

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/business-tools/excel-analyst-pro/skills/excel-variance-analyzer/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.