CtrlK
BlogDocsLog inGet started
Tessl Logo

stock-analysis

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

68

Quality

83%

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

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.

The content is well-structured with executable script calls, three concrete market examples, and clean progressive disclosure to real bundle files. Its main weakness is redundant gap-analysis exposition repeated across several sections that should be consolidated.

Suggestions

Consolidate the gap-analysis guidance: explain 向上/向下缺口 support-resistance behavior once (in 注意事项 or a reference) instead of repeating it in steps 4, 5, 6, and the注意事项 section.

Remove the duplicate dependency block in 前置准备 since it is already declared in the YAML frontmatter.

Add an explicit validation/error-recovery checkpoint after data fetching (e.g., what to do if the API returns no data or an invalid stock code) to strengthen the workflow's feedback loop.

DimensionReasoningScore

Conciseness

Mostly efficient and does not explain basic concepts Claude already knows, but gap analysis is repeated across step 4, step 5, step 6, and a full '缺口分析要点' block in 注意事项, which could be consolidated; the 前置准备 dependency list also duplicates the frontmatter.

3 / 5

Actionability

Provides concrete, executable script invocations with parameters ('scripts/fetch_stock_data.py --stock_code ... --days ...', 'scripts/analyze_stock.py --data_file ...') and three copy-paste examples, but steps 4–6 ('综合技术指标和趋势分析', '对未来3天走势进行判断') remain descriptive rather than fully executable.

4 / 5

Workflow Clarity

A clearly numbered six-step sequence with a weak validation checkpoint in step 1 ('确保代码格式正确'); this is a non-destructive analysis skill so the destructive/batch cap does not apply, though explicit error-recovery feedback loops for failed data fetches are missing.

4 / 5

Progressive Disclosure

The body is an overview pointing to real, one-level-deep bundle files — scripts/fetch_stock_data.py, scripts/analyze_stock.py, and references/stock_code_format.md — all clearly signaled with purposes in the 资源索引 section, making navigation easy.

5 / 5

Total

16

/

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.

The description is comprehensive and well-targeted, clearly answering both what the skill does and when to use it with natural Chinese stock-analysis trigger terms. Its main weakness is buzzword over-claims ('精准', '智能', '大幅提升') that slightly inflate the otherwise concrete capabilities.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('实时获取行情', '计算MACD/RSI等技术指标', '识别缺口与支撑压力位', '预测未来3天走势', '输出专业操作建议'), but buzzword modifiers like '精准识别', '智能预测', and the over-claim '大幅提升投研决策效率' introduce fluff that the rubric penalizes.

4 / 5

Completeness

Clearly states the 'what' (fetch quotes, compute indicators, find gaps/support-resistance, predict trend, output advice) and an explicit 'when' trigger clause ('在进行个股研究时,当需要深度研判买卖点与趋势'), so it is not capped at 3.

5 / 5

Trigger Term Quality

Covers natural user phrasing for stock research — '个股研究', '买卖点', '趋势', '行情', '走势预测', '操作建议' — plus domain indicator names (MACD/RSI) and synonyms (行情/走势, 支撑压力位), giving comprehensive trigger coverage.

5 / 5

Distinctiveness Conflict Risk

The niche — individual-stock technical analysis with MACD/RSI, gap, and support/resistance prediction — is specific with distinct triggers and minimal overlap risk with other 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
anbeime/skill
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.