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

74

Quality

92%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-organized instruction-style body with a clear sequenced workflow and an explicit self-check. Its main gap is the absence of any executable HTML example or skeleton for a code-producing skill, leaving actionability short of fully copy-paste-ready.

Suggestions

Add a minimal starter HTML skeleton (head, a palette-token CSS block, and the masthead + one KPI card) so the output contract demonstrates the actual HTML structure to copy.

Show one concrete inline-SVG snippet (e.g. the revenue trend line+area) so chart construction guidance becomes executable rather than descriptive.

Pair the step-5 self-check with a short fix-and-retry note (e.g. 'if a number doesn't tie, re-label or move it to a caption before emitting') to close the validation loop.

DimensionReasoningScore

Conciseness

The body is lean with no padding and no explanation of concepts Claude already knows (it assumes HTML/CSS competence and just specifies the report). Not level 2, since there is no unnecessary explanation to tighten — every section (workflow, output contract) earns its place.

3 / 3

Actionability

Guidance is concrete on what to build (named KPI cards, chart types, table rows, a self-check) but, for a skill whose output is an HTML file, provides no executable HTML example or skeleton. This matches anchor 2 (concrete guidance but incomplete, missing key details) rather than level 3's copy-paste-ready examples.

2 / 3

Workflow Clarity

A clear 5-step sequence culminating in an explicit self-check ("every number ties to a labelled chart or table; deltas show direction and percentage; accent colour used at most twice") serves as a validation checkpoint and checklist. Not level 2: validation is explicit and present, and the operation is non-destructive so a full fix-retry loop is not required to cap the score.

3 / 3

Progressive Disclosure

Under 50 lines with well-organized sections (Workflow, Output contract) and no need for external references, which the rubric explicitly permits to score 3. Not level 2: content is appropriately compact and sectioned rather than a monolithic wall.

3 / 3

Total

11

/

12

Passed

Description

100%

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, third-person, and answers both what the skill produces and when to use it, with a strong set of natural trigger terms including a multilingual one. It is a model concise description with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete report components — "masthead with KPIs, revenue and burn charts, P&L summary table, top-line highlights, and an outlook paragraph" — matching the anchor for several specific concrete actions. It is not the level below, which would only name a domain and a few actions without this breadth.

3 / 3

Completeness

Explicitly answers both what (the report's structural pieces) and when ("Use when the brief mentions 'financial report'... or '财报'"). Not level 2, where the 'when' is missing or only implied — here the trigger guidance is explicit.

3 / 3

Trigger Term Quality

Provides natural user-facing triggers ("financial report", "Q3 report", "MRR review", "P&L", "财报") with good coverage including common variations and a multilingual term. It is above level 2 because it captures several real phrasings a user would say rather than a single keyword.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear finance-report niche with distinct triggers unlikely to fire for unrelated skills. It is not level 2 because the domain and triggers are specific enough to avoid overlap with generic report skills.

3 / 3

Total

12

/

12

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.

Validation15 / 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.