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

72

Quality

90%

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

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.

An efficient, well-structured instruction body with a precise layout spec and an explicit self-check, though it omits any starter HTML/SVG code and an explicit error-retry loop. Strong progressive disclosure for a compact single-purpose skill.

Suggestions

Add a minimal starter HTML skeleton or one inline-SVG chart example so the layout spec is copy-paste ready rather than prose-only.

Turn the Self-check into an explicit feedback loop: 'If a number does not tie to a chart/table, fix it and re-check before emitting the artifact.'

Optionally reference a small CHARTS.md or ACCOUNTS.md for the SVG chart and top-accounts table patterns if the spec grows beyond the single screen.

DimensionReasoningScore

Conciseness

Lean ~30-line body that assumes Claude's competence — it never explains what a P&L, KPI, or SVG is, and every line is actionable instruction with no padding.

5 / 5

Actionability

Highly concrete layout spec — exact KPI cards (Revenue, Net new MRR, Gross margin, Cash runway), chart types (inline SVG line+area, bar), and table columns — but provides no starter HTML or SVG template, leaving a minor gap for a code-producing skill.

4 / 5

Workflow Clarity

Five clearly sequenced steps culminating in a checklist-style 'Self-check' validation step, but it lacks an explicit fix-and-retry feedback loop, stopping just short of the anchor-5 bar.

4 / 5

Progressive Disclosure

A single-purpose skill well under 50 lines with clean sections (Workflow, Output contract) and a clearly signaled one-level reference to DESIGN.md; per the simple-skills note, well-organized sections suffice for a 5.

5 / 5

Total

18

/

20

Passed

Description

95%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 tight, well-constructed description that names concrete output components and pairs them with explicit, distinctive trigger phrases including multilingual variants. Minor room to frame elements as actions rather than components.

DimensionReasoningScore

Specificity

Lists several concrete report elements — 'masthead with KPIs, revenue and burn charts, P&L summary table, top-line highlights, and an outlook paragraph' — but frames them as components rather than explicit actions, leaving a minor gap versus comprehensive action coverage.

4 / 5

Completeness

Explicitly answers both 'what' (the report's contents) and 'when' via 'Use when the brief mentions "financial report", "Q3 report", "MRR review", "P&L", or "财报"', matching the anchor-5 pattern of concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonym variants ('financial report', 'Q3 report'), a domain abbreviation ('P&L'), a metric phrase ('MRR review'), and a multilingual term ('财报'); no file-extension concept applies to this artifact domain.

5 / 5

Distinctiveness Conflict Risk

Clear finance-reporting niche with distinctive triggers (P&L, MRR review, 财报) that minimize overlap with generic report or dashboard skills.

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.

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.