CtrlK
BlogDocsLog inGet started
Tessl Logo

finance-report

Quarterly / monthly financial report — masthead with KPIs, revenue and burn charts, P&L summary table, top-line highlights, and an outlook paragraph. Use when the brief mentions "financial report", "Q3 report", "MRR review", "P&L", or "财报".

76

Quality

96%

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

100%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 single-file skill body: a numbered workflow with a concrete self-check, exact layout and content specifications, and a literal output contract, all with no wasted tokens. Nothing in the body explains what Claude already knows, and every instruction is directly executable.

DimensionReasoningScore

Conciseness

The ~33-line body contains zero concept explanations and zero padding; every line is an instruction ('Produce a single-screen financial report in one self-contained HTML file'). Every token earns its place.

5 / 5

Actionability

Concrete, executable guidance throughout: exact KPI names ('Revenue, Net new MRR, Gross margin, Cash runway'), specified chart types ('inline SVG line + area', 'inline SVG bar'), defined table rows (Revenue / Gross profit / Opex / Net), and a literal copy-paste output contract with the artifact tag. Fully actionable for an instruction-only skill.

5 / 5

Workflow Clarity

A clear 5-step sequence ending in an explicit validation self-check checklist ('every number ties to a labelled chart or table; deltas show direction and percentage; accent colour used at most twice'). Not a 4: the validation checkpoint is explicit and specific, not merely implied. No destructive or batch operations, so no cap applies.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external bundle references (references/, scripts/, assets/ are absent and none are needed); sections are well-organized (Workflow, Output contract). Per the simple-skill guidance, this earns a 5 on well-organized sections alone.

5 / 5

Total

20

/

20

Passed

Description

92%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: concrete artifact components, an explicit 'Use when' clause with natural trigger phrases in two languages, and a well-delineated niche. The only weakness is a handful of missing natural synonyms (e.g., 'quarterly report', 'finance report') in the description itself, though several appear in the frontmatter triggers list.

DimensionReasoningScore

Specificity

Enumerates five concrete deliverables — 'masthead with KPIs, revenue and burn charts, P&L summary table, top-line highlights, and an outlook paragraph' — giving comprehensive, specific coverage of what the skill produces. Not a 4, since there are no minor gaps in the component coverage.

5 / 5

Completeness

Explicitly answers both what (the enumerated report components) and when ('Use when the brief mentions "financial report", "Q3 report", "MRR review", "P&L", or "财报"') with concrete trigger phrases. Matches the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

Natural user phrases are present ('financial report', 'Q3 report', 'MRR review', 'P&L', '财报'), but common variations such as 'quarterly report', 'finance report', and '财务报告' are missing from the description itself. Matches anchor 4: good coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

A clear finance-reporting niche with domain-distinct triggers (P&L, MRR, 财报) that are unlikely to fire for other skills. Minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.