CtrlK
BlogDocsLog inGet started
Tessl Logo

sector-rotation

行业轮动分析——申万行业景气度评分、行业动量排名、产业链传导、估值/盈利/资金流多维比较框架

62

Quality

74%

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 ./agent/src/skills/sector-rotation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 is a concrete, actionable sector-rotation framework with real executable code and explicit numeric scoring rules. It is dense and efficient, though monolithic with no progressive disclosure into reference files.

Suggestions

Split the detailed scoring rubric and ETF code tables into a references/ file (e.g. references/scoring.md) and link from the overview to enable progressive disclosure.

Add an explicit validation/sanity-check step before emitting 超配/低配 recommendations (e.g. verify data freshness and cross-check 动量 vs 景气度 signals).

Trim the three full 产业链 examples to one canonical example plus a one-line summary of the others to reduce token weight.

DimensionReasoningScore

Conciseness

Dense tabular content that assumes Claude's knowledge of PE/PB/ROE/PMI with minimal padding; a few sections (three detailed 产业链 examples, repeated 周期股估值陷阱 explanation) could be trimmed.

4 / 5

Actionability

Provides an executable pandas sector_momentum function, concrete scoring rules with numeric thresholds, explicit composite-formula weights, specific ETF codes, and a copy-paste-ready output template.

5 / 5

Workflow Clarity

Clear sequenced flow from 景气度评分 → 动量排名 → 产业链传导 → 多维比较 → 配置建议 with explicit decision rules (Top 5 超配/Bottom 5 低配); checkpoints are implicit rather than explicit, though no destructive operation requires hard validation.

4 / 5

Progressive Disclosure

Well-sectioned with clear headers but the entire ~190-line framework is inlined in SKILL.md with no external reference files to split out detailed tables (e.g. the scoring rubric or ETF code list).

3 / 5

Total

16

/

20

Passed

Description

70%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 specific and distinctive, listing multiple concrete analytical actions tied to the A股 sector-rotation domain. Its main weakness is the missing explicit 'when to use' trigger clause.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about A股行业轮动、板块配置、行业景气度比较 or 超配/低配建议'.

Include a few natural synonyms (板块轮动、行业配置、申万一级) to broaden trigger-term coverage.

State the output explicitly in the description (e.g. '输出行业超配/低配建议') so the 'what' is fully concrete.

DimensionReasoningScore

Specificity

Names several concrete actions—'景气度评分'、'动量排名'、'产业链传导'、'估值/盈利/资金流多维比较'—with only minor gaps in coverage.

4 / 5

Completeness

A clear 'what' is present but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Good keyword coverage of natural terms a user would say (行业轮动、行业景气度、动量排名、产业链、估值、资金流), though a few synonyms like 板块轮动/行业配置 are missing.

4 / 5

Distinctiveness Conflict Risk

The 申万行业景气度/动量/产业链/资金流 framing carves a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

16

/

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
HKUDS/Vibe-Trading
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.