CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stock-analysis

财务和投资分析师在进行个股研究时,当需要深度研判买卖点与趋势,使用本技能可实时获取行情,计算MACD/RSI等技术指标,精准识别缺口与支撑压力位,智能预测未来3天走势并输出专业操作建议,大幅提升投研决策效率。

Quality

72%

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 ./skills/stock-analysis/stock-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 presents a clear, actionable pipeline with real, well-signposted bundle files, but it is noticeably padded — the gap-analysis rules are restated four times, dependencies are duplicated, and the three usage examples are redundant. Workflow sequencing is sound but lacks validation checkpoints (fetch failure, insufficient history for MA60 with the 30-day default).

Suggestions

Consolidate the gap-analysis guidance (up gap = support, down gap = resistance, size/recency/volume caveats) into a single section — it currently appears in steps 4, 5, 6, and again in 注意事项.

Drop the duplicated dependency block in 前置准备 (already in frontmatter) and reduce the three near-identical 使用示例 to one, noting that only the code format changes between A股/港股/美股.

Add validation checkpoints to the workflow: what to do when data fetching fails (e.g., retry with alternate code formats per references/stock_code_format.md) and confirm sufficient history for the indicators being computed (the default 30 days cannot yield MA60).

DimensionReasoningScore

Conciseness

Gap-analysis semantics (up gap = support, down gap = resistance) are repeated four times — in step 4 ('向上缺口:通常构成支撑位...向下缺口:通常构成压力位'), step 5 ('缺口支撑压力'), step 6 ('缺口相关的操作提示'), and again as five bullets under 注意事项 restating the same points ('向上缺口...通常在回调时可能构成支撑'). The dependency block is duplicated from the frontmatter, and the three 使用示例 are near-identical command sequences that add little beyond the first. This is several padded sections, matching the 2 anchor ('noticeably verbose') rather than 3 ('some unnecessary explanation').

2 / 5

Actionability

Concrete, executable guidance throughout: named scripts with parameters and defaults ('scripts/fetch_stock_data.py --stock_code ... --days 默认30天', 'analyze_stock.py --data_file ...'), enumerated analysis outputs (MA5/MA10/MA20/MA60, MACD, RSI, support/resistance), and worked command lines in the examples ('fetch_stock_data.py --stock_code 000001 --days 30'). Minor gaps keep it below 5: the interpreter invocation is omitted ('调用' rather than a copy-paste command) and the output file naming convention is only implied by the examples.

4 / 5

Workflow Clarity

The six-step sequence is clearly numbered and ordered with per-step inputs/outputs, but validation checkpoints are missing or implicit: step 1 says to verify the code format, yet there is no guidance for handling fetch failures or empty/partial data, and no check that the returned history is sufficient (the default --days 30 cannot produce the listed MA60 moving average). This matches the 3 anchor ('steps listed but validation gaps; checkpoints missing') rather than 4, whose example includes an explicit verify step after each risky operation.

3 / 5

Progressive Disclosure

Structure is good: a well-labeled 资源索引 points to scripts/fetch_stock_data.py, scripts/analyze_stock.py, and references/stock_code_format.md — all of which exist as real bundle files — each annotated with its purpose, and the code-format detail is properly offloaded to the reference (one level deep, no nested references). It falls short of the 5 anchor because the repeatedly inlined gap-analysis material is content that should be consolidated or split out, leaving minor organization gaps.

4 / 5

Total

13

/

20

Passed

Description

78%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 explicitly covers both what the skill does and when to use it, with concrete, domain-specific actions and good natural trigger terms in Chinese. The main weakness is modest buzzword padding ('智能', '精准', '大幅提升效率') that adds claims without information.

DimensionReasoningScore

Specificity

The description lists several concrete actions — '实时获取行情' (fetch real-time quotes), '计算MACD/RSI等技术指标' (compute MACD/RSI indicators), '识别缺口与支撑压力位' (identify gaps and support/resistance), '预测未来3天走势' (predict next 3 days), '输出专业操作建议' (output operational advice) — which is comprehensive coverage. However, buzzword padding like '智能预测' (intelligently predict), '精准识别' (precisely identify), and '大幅提升投研决策效率' (greatly improve decision efficiency) is vague fluff the guidelines say to penalize, keeping it below the 5 anchor.

4 / 5

Completeness

Both 'what' and 'when' are explicitly present: the what is the concrete action list, and the when is '在进行个股研究时,当需要深度研判买卖点与趋势' (when doing single-stock research and needing to judge buy/sell points and trends). It falls short of the 5 anchor because the 'when' clause names a condition rather than concrete user-facing trigger phrases (e.g., 'when the user provides a stock code and asks for trend analysis'), and the audience framing ('财务和投资分析师') is narrower than actual usage.

4 / 5

Trigger Term Quality

Natural terms a Chinese-speaking analyst would actually say are well covered: '个股研究' (single-stock research), '买卖点' (buy/sell points), '趋势' (trend), '行情' (quotes), 'MACD/RSI', '支撑压力位' (support/resistance), '走势' (movement), '操作建议' (trading advice). A few common variations are missing — e.g., '技术分析' (technical analysis), 'K线' (candlesticks), '股票代码' (stock code) — so it sits between the 3 and 5 anchors, closer to 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and distinct: technical analysis of individual stocks with specific indicators (MACD/RSI), gap identification, support/resistance levels, and 3-day movement prediction. These are specific, unambiguous triggers with minimal overlap risk against other skills, matching the 5 anchor ('clear niche with distinct triggers'). It is clearly above the 4 anchor because the indicator and gap-analysis specifics make mistaken triggering very unlikely.

5 / 5

Total

17

/

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

anbeime/skill

Path

skills/stock-analysis/stock-analysis/SKILL.md

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.