CtrlK
BlogDocsLog inGet started
Tessl Logo

regulatory-knowledge

金融监管知识库:A股涨跌停/ST退市新规/融券、港股T+0/做空机制、美股PDT/熔断、加密监管政策、跨境税务基础

48

Quality

61%

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/regulatory-knowledge/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 well-organized, information-dense reference whose specialized regulatory data (thresholds, fee schedules, tax tiers, dated rule changes) is exactly what Claude cannot be trusted to recall. Its weaknesses are structural: ~300 lines all inlined in SKILL.md with no progressive disclosure, non-executable pseudocode where runnable backtest-constraint code would fit, and no validation checkpoint for the analysis workflow it prescribes.

Suggestions

Split the four per-market sections (A股/港股/美股/加密) into references/ files (e.g., references/a-share.md, references/us.md) and keep SKILL.md as an overview plus the 约束矩阵 and output format — the file currently inlines ~295 lines of reference detail with no external files.

Replace the 涨跌停/T+1 pseudocode blocks with an executable pandas snippet a backtest engine can actually call, or drop the unused 'pip install pandas numpy' dependency section if no runnable code is intended.

Add a validation checkpoint to the 分析框架 workflow, e.g. 'verify the backtest reproduces historical limit-up non-fills on a known date range before trusting strategy returns', so the prescribed compliance analysis has a feedback loop.

DimensionReasoningScore

Conciseness

The dense tabular format carries genuinely specialized, time-sensitive data (维持担保比例 thresholds, 2023 印花税减半, dividend-tax holding tiers) that earns its tokens. But the 约束矩阵 repeats material already covered in 核心概念, and sections like 美股交易时间 and the 7%/13%/20% circuit-breaker levels are basics Claude already knows. This is 'mostly efficient but includes some unnecessary explanation or could be tightened', not the noticeably-padded level 2.

3 / 5

Actionability

There is real concrete guidance — the 跨市场合规检查清单, exact A股 cost breakdown (佣金 0.025%, 印花税 0.05%), and a filled-in output-report template — but the only code is non-executable pseudocode ('if daily_return >= limit_up: buy_signal无法执行, 推迟到次日'), and the 'pip install pandas numpy' dependency is used by nothing in the skill. Matches 'some concrete guidance but incomplete; pseudocode instead of executable code'.

3 / 5

Workflow Clarity

The 分析框架 section provides a numbered sequence (约束矩阵 → 合规检查清单 → 税务影响) and a concrete output format, giving an analyzable path. However, checkpoints are missing: nothing tells the reader how to verify a backtest correctly encodes a rule (e.g., comparing simulated fills against limit-up days), so it sits at 'steps listed but validation gaps'. This is an analysis/reference skill, not a destructive or batch operation, so no hard cap applies.

3 / 5

Progressive Disclosure

Sections are well-organized with clear ##/### headers, but the file is ~295 lines of per-market reference detail (A股, 港股, 美股, 加密 each ~40-60 lines) with zero external reference files — content that naturally belongs in per-market reference files is fully inlined. This is over the 50-line threshold where organized-sections-alone would justify a 5, matching 'some structure but could be better organized; content that should be separate is inline'.

3 / 5

Total

12

/

20

Passed

Description

56%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 identifies a specific, distinctive domain with strong natural trigger terms, but it reads as a topic catalog rather than a capability statement: it says what the skill contains, never what it does or when to invoke it. Adding an explicit action verb pair and a 'Use when...' clause would move it from adequate to strong.

Suggestions

Add an explicit 'when' clause, e.g. 'Use when backtesting multi-market strategies, setting compliance/risk parameters, or evaluating tax impact of trading strategies' — its absence currently caps completeness at 3.

Convert the topic list into concrete actions, e.g. 'Provides exchange trading-rule constraints (A股涨跌停/T+1, 港股T+0, 美股PDT/熔断, crypto policy) for backtest engines, compliance checks, and tax-aware return calculations' instead of the noun-phrase '金融监管知识库'.

Include the skill's primary use-case keywords 回测 (backtest) and 合规 (compliance) as trigger terms, since those are the scenarios the body targets but the description never mentions.

DimensionReasoningScore

Specificity

The description enumerates sub-domains ("A股涨跌停/ST退市新规/融券", "港股T+0/做空机制", "美股PDT/熔断", "加密监管政策", "跨境税务基础") but the only action framing is "知识库" — a statement of what it is, not what it does. This matches the anchor 'names the domain but actions are minimal or generic'; a score of 3 would require at least 1-2 concrete action verbs, which are absent.

2 / 5

Completeness

The 'what' is clear (a regulatory knowledge base covering four markets plus cross-border tax), but there is no 'Use when...' clause or any equivalent trigger guidance, capping completeness at 3 per the rubric guidelines. Not 4 because the 'when' is entirely absent rather than merely implicit-but-present.

3 / 5

Trigger Term Quality

Terms like 涨跌停, ST退市, 融券, T+0, 做空, PDT, 熔断 are natural phrases a quant user would say, with good cross-market coverage. Not 5 because common variations tied to the skill's actual use cases (回测/backtest, 合规/compliance, 港股通) are missing.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (exchange trading rules for quant trading) with distinctive triggers like PDT, 涨跌停, and 融券 that few other skills would claim. Not 5 because '跨境税务基础' and '加密监管政策' have some overlap risk with general finance/tax/compliance skills.

4 / 5

Total

13

/

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
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.