CtrlK
BlogDocsLog inGet started
Tessl Logo

report-generate

Professional financial research report generation — standard structure (summary / views / main body / risks / recommendation), Markdown formatting standards, rating system, and terminology guide.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/report-generate/SKILL.md
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.

The body is a strong, actionable specification: concrete templates, quantitative rating thresholds, and explicit formatting standards make it highly actionable and well-sequenced with quality checklists. Its only notable gaps are a few trimmable reference sections and the absence of any external reference files to offload the longer reference material.

DimensionReasoningScore

Conciseness

The body is information-dense — tables, templates, and concrete standards rather than padded prose — and largely avoids explaining concepts Claude already knows; minor trim opportunities exist (e.g. the abbreviations table and sample data inside the backtest template), keeping it just below fully lean.

4 / 5

Actionability

It provides copy-paste-ready report templates, quantitative rating thresholds (Sharpe > 1.5, max drawdown < 20%), explicit number/table formatting rules, and concrete file inputs ("read metrics.csv and equity.csv"), covering the common report types comprehensively.

5 / 5

Workflow Clarity

A clear sequence exists in "Preparation Before Writing" and "Writing Principles", and the "Output Format" / "Notes" sections function as verification checklists (≥3 risk warnings, disclaimer mandatory, data consistency); it is not a 5 because there is no explicit validate-and-retry feedback loop, though report generation does not strictly require one.

4 / 5

Progressive Disclosure

The single-file skill is well-organized into clearly headed sections that are easy to navigate; it stops short of 5 because no bundle reference files are used, so terminology/templates that could be split out are all inlined in one ~260-line file.

4 / 5

Total

17

/

20

Passed

Description

58%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 clearly conveys what the skill produces and names several concrete components, giving it solid specificity and distinctiveness. Its main weakness is the missing explicit "when to use" trigger guidance, which caps completeness and leaves trigger-term quality at a mid level.

Suggestions

Add an explicit trigger clause, e.g. "Use when generating financial research reports, stock/industry analysis, or backtest commentary."

Include natural user-facing synonyms such as "investment report", "analyst report", and "equity research" alongside "financial research report".

Lead with the core action verb phrase ("Generate professional financial research reports") before enumerating the structural and formatting components.

DimensionReasoningScore

Specificity

The description names the domain ("Professional financial research report generation") and lists several concrete components — "standard structure (summary / views / main body / risks / recommendation), Markdown formatting standards, rating system, and terminology guide" — giving multiple specific coverage areas, though they read as topics rather than distinct actions.

4 / 5

Completeness

It clearly answers "what" the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3 with the "when" missing rather than merely implied.

3 / 5

Trigger Term Quality

Relevant domain keywords appear ("financial research report", "rating", "Markdown") but natural trigger phrases a user would say (e.g. "research report", "investment report", "analyst report", "Use when generating a research report") and common synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

"Professional financial research report generation" with a specific structure and rating system is a mostly distinct niche with only minor overlap risk against generic report or finance skills; it is not a 5 because no explicit trigger phrasing sharpens the boundary.

4 / 5

Total

14

/

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
HKUDS/Vibe-Trading
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.