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 "财报".

71

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 finance-report in nexu-io/open-design

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, directive skill body with a clear sequence and an explicit self-check. The main weaknesses are a missing recovery path after the self-check and an unresolved reference to DESIGN.md that isn't shipped in the bundle.

Suggestions

Add a one-line recovery instruction after the self-check (e.g., 'If any check fails, fix the section and re-verify before emitting the artifact') to close the feedback loop.

Clarify the DESIGN.md reference: state where it lives (bundle path or runtime-provided design system) and what to do if it is absent.

Add brief numeric conventions (delta sign/percentage format, plausible value ranges for a quarterly SaaS report) so the output is fully determined without guesswork.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and directive with zero padding — 'Tables, KPI cards, and chart strokes use palette tokens — never invent new ones' assumes competence and adds only what Claude wouldn't infer. Every token earns its place.

5 / 5

Actionability

Guidance is mostly executable — an ordered layout with named KPI cards ('Revenue, Net new MRR, Gross margin, Cash runway'), chart types ('inline SVG line + area'), table contents, and a concrete output contract. Minor gaps remain: no specifics on delta formatting, palette token names, or numeric plausibility ranges.

4 / 5

Workflow Clarity

Five clearly sequenced steps with an explicit self-check checkpoint ('every number ties to a labelled chart or table; deltas show direction and percentage; accent colour used at most twice'), but there is no guidance on what to do when the self-check fails, so the validation loop is not a full feedback loop.

4 / 5

Progressive Disclosure

The short body is well organized into Workflow and Output contract sections with no inlined content that belongs in separate files (no bundle files exist). However, step 1 instructs 'Read the active DESIGN.md' — a file not present in the bundle — leaving that reference's location and structure unresolved.

4 / 5

Total

17

/

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 deliverable inventory, explicit 'Use when' clause with natural and bilingual trigger phrases. The only gap is that a few natural keyword variants are not surfaced in the description text itself.

Suggestions

Fold the broader trigger list (e.g., 'finance report', 'quarterly report', '财务报告') into the description's 'Use when' clause so all natural variations appear where users and models actually read them.

Consider naming the output form (a single self-contained HTML report) in the description so the 'what' also communicates the deliverable format.

DimensionReasoningScore

Specificity

The description enumerates concrete deliverables — 'masthead with KPIs, revenue and burn charts, P&L summary table, top-line highlights, and an outlook paragraph' — giving comprehensive, non-abstract coverage of the skill's output.

5 / 5

Completeness

It explicitly answers both 'what' (the report structure and its sections) and 'when' ('Use when the brief mentions "financial report", "Q3 report", "MRR review", "P&L", or "财报"') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'financial report', 'Q3 report', 'MRR review', 'P&L', and the synonym '财报' are present, but common variations such as 'finance report', 'quarterly report', or 'earnings' are missing from the description itself (they only appear in the separate triggers field).

4 / 5

Distinctiveness Conflict Risk

A clear finance-report niche with distinctive triggers ('MRR review', '财报') makes it unlikely to fire for unrelated skills; conflict risk is minimal.

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.