CtrlK
BlogDocsLog inGet started
Tessl Logo

a-stock-predictor

预测A股个股次日走势,输出图文并茂的 Markdown 分析报告(含详细逻辑推导、中间结果、概率量化与操作建议),面向散户与专业投资者均适用。触发条件:用户输入A股股票名称或代码(6位数字,如600519、000858),并希望获得次日走势预测;关键词包括"预测明天走势"、"明天能涨吗"、"A股分析"、"帮我分析XX股票"、"明天该买吗"、"次日预测"、"做T建议"、"短线操作"、"明日行情"、"值得持有吗"、"止盈止损怎么设"等。即使用户只说"帮我看看贵州茅台明天怎么走"或"600519明天能不能买",也应使用本 skill。输出 Markdown 文件保存到当前项目 markdown/ 目录,要求逻辑清晰、概率可量化、图文并茂,投资小白也能看懂。

64

Quality

76%

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

Quality

Content

62%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 delivers an unusually concrete, well-sequenced methodology — literal search templates, quantified scoring thresholds, probability mapping, risk rules, and a self-check checklist — but it is a 570-line monolith with no progressive disclosure: scoring rubrics, report template, glossary, and chart specs are all inlined, and a glossary of concepts Claude already knows pads the token cost. It would score near the top after splitting into reference files and trimming known-concept explanations.

Suggestions

Split the five-dimension scoring rubrics, report template, visualization specs, glossary, and special-case rules into separate files under references/ (e.g., references/pace-scoring.md, references/report-template.md, references/glossary.md) and keep SKILL.md as a concise overview linking to them one level deep.

Trim or move the 专业术语词典 — entries like T+1, 涨停板, MACD, KDJ, and 均线 explain concepts Claude already knows; keep only the instruction that report output must annotate terms on first use.

Replace the placeholder 使用示例 ("P=XX/20") with one fully worked example using real numbers (e.g., a completed 贵州茅台 scoring pass, total score, scenario probabilities, E(r), and risk parameters) to make the end-to-end process copy-paste concrete.

DimensionReasoningScore

Conciseness

At ~570 lines the body is noticeably verbose: it includes a glossary of concepts Claude already knows (T+1, 涨停板, MACD, KDJ, 均线, 融资余额), editorial commentary ("A股最核心的量化信号", "A股最重要的均线"), and elaborate ASCII-art boxes with {placeholders} that could be far terser. The genuinely novel PACE scoring material is diluted by this padding, matching the 'noticeably verbose; several unnecessary explanations or padded sections' anchor rather than the mostly-efficient score-3 anchor.

2 / 5

Actionability

Highly concrete for an instruction-only skill: ten literal search-query templates, numeric scoring thresholds ("北向单日净买>10亿 → 强烈利多(8分)"), a score-to-probability conversion table, an E(r) formula with explicit decision rules ("若 E(r) > 0.5% 且 P_A/P_C > 1.5…"), a full report skeleton, and an exact file-naming convention. It falls short of 5 only because the worked example ("使用示例") is placeholder text ("P=XX/20") rather than a concrete end-to-end case with real numbers.

4 / 5

Workflow Clarity

The six-step 执行流程 is clearly sequenced (parse input → 8+ parallel searches → per-dimension scoring with mandatory stated reasoning → score-to-probability/scenario mapping → risk parameters → report output), backed by explicit validation: a 12-item pre-output 质量检查清单, a data-completeness feedback path ("标注缺失 → 降低置信度 → 该维度取中间分"), and consistency checks ("三情景概率合计 = 100%"). This matches the anchor for clear sequencing with explicit validation steps, feedback loops, and checklists; this is an analysis skill, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

There are no bundle files (no references/, scripts/, or assets/ exist) and no external references at all — the entire five-dimension scoring rubric, report template, visualization specs, glossary, and special-case rules are inlined in one 570-line SKILL.md. The many well-labeled ## sections keep it navigable (above the minimal-structure score-2 anchor), but content that clearly belongs in separate reference files (scoring rubrics, report template, glossary) is fully inline, so it cannot score 4 or 5.

3 / 5

Total

14

/

20

Passed

Description

91%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: it explicitly answers what and when, includes an unusually rich set of natural Chinese trigger phrases and input formats, and is clearly scoped to A-share next-day prediction. Its only weaknesses are verbosity/redundancy in the phrasing and minor trigger overlap with generic trading-advice skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "预测A股个股次日走势,输出图文并茂的 Markdown 分析报告(含详细逻辑推导、中间结果、概率量化与操作建议)" and "输出 Markdown 文件保存到当前项目 markdown/ 目录" — giving what and how, with minor gaps (the scoring methodology is only hinted at by "概率量化"). It is not a clean 5 because the phrasing is padded with redundant qualifiers ("概率可量化" vs "概率量化", "图文并茂" stated twice) and audience fluff ("面向散户与专业投资者均适用"), which the verbosity guideline penalizes.

4 / 5

Completeness

Both questions are explicitly answered: what ("预测A股个股次日走势,输出图文并茂的 Markdown 分析报告…") and when ("触发条件:用户输入A股股票名称或代码(6位数字…),并希望获得次日走势预测") with concrete trigger phrases and worked examples. This clearly matches the anchor for explicit what AND when with concrete trigger phrases, not merely the weaker 'when' of score 4.

5 / 5

Trigger Term Quality

Comprehensive natural-phrase coverage users would actually say: "预测明天走势"、"明天能涨吗"、"明天该买吗"、"帮我分析XX股票"、"做T建议"、"止盈止损怎么设"、"值得持有吗", plus the code format ("6位数字,如600519、000858") and even implicit phrasings like "帮我看看贵州茅台明天怎么走". This matches the anchor for comprehensive synonym coverage including input formats.

5 / 5

Distinctiveness Conflict Risk

The niche is clear — A股 (mainland China A-shares), 6-digit codes like 600519, next-day (次日) prediction — so conflict risk is low. It falls just below 5 because some trigger keywords ("短线操作"、"值得持有吗"、"止盈止损怎么设") would also fire for a generic stock-analysis or trading-advice skill, giving minor overlap risk with closely related skills.

4 / 5

Total

18

/

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

skill_md_line_count

SKILL.md is long (579 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

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.