CtrlK
BlogDocsLog inGet started
Tessl Logo

financial-report-analyst

深度解读企业财报,将财报 PDF 或 URL 转化为面向普通投资者的专业分析报告,以 Markdown 格式保存到当前项目的 markdown/ 目录。 触发条件:用户上传或提供财报 PDF、提到"分析财报"/"读财报"/"解读财报"/"看看这家公司"/"帮我分析一下 XX 公司",或任何需要深入理解一份财务报告的场景。 输出一份犀利、有逻辑支撑的投资参考报告,涵盖:核心收入分析、财务健康诊断、隐蔽风险雷区排查、行业竞争格局、前瞻性估值,以及明确的投资参考建议。 即使用户只说"帮我看这份年报"但内容是财报,也应使用本 skill。

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/skills_for_claude_web/financial-report-analyst/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-sequenced, actionable analytical skill with concrete quantitative guidance and a clear output template. Its main weakness is progressive disclosure: a reference file exists but is never invoked from the body, and the content is denser than it needs to be.

Suggestions

In Step 4 (前瞻性关键问题拆解), explicitly link to references/advanced-frameworks.md (e.g. '科技/AI/Robotaxi 公司参见 advanced-frameworks.md') so the bundled reference is actually discovered and used.

Tighten Step 2's eight-pitfall section by collapsing the four 隐蔽 pits into a single condensed table or moving detailed thresholds into the reference file, reducing token load.

Add a brief validation checkpoint after Step 2 (e.g. '确认八大坑位均已给出 ✅/⚠️/🚨 结论后再进入估值') to turn the implicit scan into an explicit validate-before-proceed loop.

DimensionReasoningScore

Conciseness

Mostly efficient and well-structured with purposeful tables and checklists, though the eight-pitfall and key-question sections run long and could be tightened in places without losing substance.

4 / 5

Actionability

Provides concrete quantitative thresholds (OCF/净利润 >1, 商誉/净资产 >30%, 其他应收款/总资产 >5%) plus specific file-naming and mkdir commands, with only minor gaps where analytical judgment is left underspecified.

4 / 5

Workflow Clarity

A clear eight-step sequence (Step 0–7) with explicit per-pitfall conclusion labels (✅/⚠️/🚨), though it lacks a rigorous validate→fix→retry feedback loop for the risk-scan and output-writing steps.

4 / 5

Progressive Disclosure

A one-level-deep reference (advanced-frameworks.md) exists, but the body never signals or links to it in the workflow, leaving the main content somewhat monolithic and the reference effectively disconnected.

3 / 5

Total

15

/

20

Passed

Description

88%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 that clearly states both what the skill does and when to use it, with concrete trigger phrases and specific output capabilities. Minor improvements possible around trigger synonym coverage and tightening the distinctiveness against generic analysis skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '将财报 PDF 或 URL 转化为...分析报告', plus six specific analytical outputs (核心收入分析、财务健康诊断、隐蔽风险雷区排查、行业竞争格局、前瞻性估值、投资参考建议) — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (深度解读财报并产出分析报告) and when (dedicated 触发条件 clause with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural trigger phrases users would actually say ('分析财报'/'读财报'/'解读财报'/'看看这家公司'/'帮我分析一下 XX 公司'), but coverage is Chinese-only and a few common variations/synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Clearly niched to financial-report analysis with distinct triggers, but the broad 'analysis' framing could create minor overlap with general data-analysis skills.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
digoal/blog
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.