CtrlK
BlogDocsLog inGet started
Tessl Logo

a-stock-prediction

A股个股次日(T+1)走势预测 skill。当用户输入A股股票代码(如 600519、000858、300750、688981、430090)或公司名称(如"贵州茅台"、"宁德时代"、"比亚迪"),并要求预测次日走势、给出交易计划、评估盈亏概率时,触发本 skill。skill 会用 mcp__MiniMax__web_search 搜证大盘环境、龙虎榜、北向资金、融资融券、主力资金流、板块联动、公告与消息面等,按"四维分析框架"(大盘环境 30% / 资金行为 30% / 技术面 25% / 消息面 15%)交叉验证,产出可量化的方向预测(看多/看空/震荡 + 概率百分比 + 价格区间),并写入当前项目 markdown 目录下的 `a-stock-{代码}-{YYYY-MM-DD}.md`。输出包含详细逻辑推导链、中间结果与最终结果概率、专业术语小白解释、mermaid/ascii/svg 图表。适用场景:盘后复盘想做次日的方向判断与交易计划;不适用:长线基本面估值(改用 finance-core-analysis)、日内高频交易、港股/美股(改用 us-stock-prediction)。

71

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, well-sequenced workflow skill: every step has executable queries, formulas, thresholds, and a delivery checklist with rework loops, and the bundle of six references plus a template is genuinely one level deep and clearly signaled. The main costs are token redundancy (rules restated across the workflow diagram, risk rules, anti-pattern table, and checklist) and inline detail that duplicates the reference files, making SKILL.md longer than an overview needs to be.

Suggestions

Consolidate repeated rules: state the ≤65% probability clamp, the 年线/高开>7% red lines, and the T+1 position sizing rule once each in 风险铁律, and have the 反模式 table and 自检清单 reference them instead of restating them — this trims the biggest token redundancy.

Replace the ~25-line ASCII workflow diagram with a one-line ordered list of the 7 steps, since each step is immediately detailed in its own section anyway.

Slim SKILL.md toward an overview: move the step 3 per-dimension scoring examples and step 4 probability/price-band formulas fully into references/four-dimension-framework.md and references/scoring-system.md (keeping only the weights, the -2..+2 scale, and the clamp rule inline), letting the existing well-signaled references carry the detail.

DimensionReasoningScore

Conciseness

The body is dense with operational specifics and avoids explaining concepts Claude already knows, but it is noticeably repetitive and could be tightened: the ≤65% probability clamp appears three times (step 4, 风险铁律 2, 反模式 table), the ~25-line ASCII workflow diagram restates the seven section headings that follow it, and the 反模式 table overlaps heavily with 风险铁律 (年线, 高开>7%, 65% clamp, T+1 仓位). The 自检清单 then recaps both sections again.

3 / 5

Actionability

Guidance is fully executable throughout: copy-ready search query templates ('{股票代码} 今日 龙虎榜'), explicit scoring weights and -2..+2 anchors, concrete formulas (仓位金额 = 账户净值×2% ÷ (入场价−止损价) × 入场价; 价格区间 via ATR × 1.28), a fixed report skeleton, exact file naming, and worked example output in step 7. No vague directions remain.

5 / 5

Workflow Clarity

The 7-step workflow is strictly sequenced with explicit validation checkpoints and feedback loops: P0→P1→P2 search priority with '没查到则预测置信度降一级', forced confidence downgrade on hedging signals, a hard clamp rule, a 15-item 自检清单 gated by '未通过任何一项 = 重新写,不能交付', and a 反模式 table requiring rework. This matches the top anchor: clear sequence, explicit validation, error-recovery loops, and a checklist.

5 / 5

Progressive Disclosure

Structure is good: six reference files plus a report template in assets/, each existing on disk and one level deep, all well-signaled in the 资源引用 section with content descriptions and in-line pointers at each step. Slightly below the top anchor because the 367-line body still inlines material duplicated in the bundle — the step 3 scoring table and step 4 probability/price formulas repeat what references/four-dimension-framework.md and references/scoring-system.md hold — so SKILL.md is more than a lean overview.

4 / 5

Total

17

/

20

Passed

Description

92%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 very strong description: it states what the skill does in concrete, quantified terms, gives explicit natural-language triggers with real codes and company names, and carves out a distinct niche with explicit non-goals and redirects. The only minor gap is absence of a few colloquial phrasings users might use when asking about next-day direction.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions: '用 mcp__MiniMax__web_search 搜证大盘环境、龙虎榜、北向资金、融资融券', a quantified '四维分析框架(大盘环境 30% / 资金行为 30% / 技术面 25% / 消息面 15%)', '方向预测(看多/看空/震荡 + 概率百分比 + 价格区间)', and a concrete output file pattern 'a-stock-{代码}-{YYYY-MM-DD}.md'. Coverage is comprehensive across search, scoring, output format, and chart types with no gaps.

5 / 5

Completeness

It explicitly answers both 'what' (four-dimension weighted analysis producing direction + probability + price range, written to a named markdown file) and 'when' ('当用户输入A股股票代码...或公司名称...并要求预测次日走势、给出交易计划、评估盈亏概率时,触发本 skill'), plus explicit 适用场景 and 不适用 with redirects to sibling skills.

5 / 5

Trigger Term Quality

Good natural trigger coverage: stock codes ('600519、000858、300750、688981、430090'), company names ('贵州茅台'、'宁德时代'、'比亚迪'), and user actions ('预测次日走势、给出交易计划、评估盈亏概率') are all phrases users would actually say. A few common colloquial variants ('明天会涨吗', '值不值得买', '能不能追') are missing, which keeps it just below the comprehensive-synonym anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (A股 T+1 next-day prediction) with explicit boundaries that redirect overlapping requests elsewhere: '长线基本面估值(改用 finance-core-analysis)、日内高频交易、港股/美股(改用 us-stock-prediction)'. Code-range examples (600/000/300/688/430) further constrain triggering to A-shares, minimizing conflict risk.

5 / 5

Total

19

/

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.

Validation — 16 / 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.