CtrlK
BlogDocsLog inGet started
Tessl Logo

corporate-events

公司事件驱动分析:并购套利价差计算、大股东增减持信号、股权激励解读、定增配股影响评估、A股ST/退市预警

58

Quality

73%

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/corporate-events/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 dense, knowledgeable A-share event-driven playbook with genuinely useful non-generic content (empirical return tables, filter rules, worked calculations, an output template), weakened by the total absence of executable data-retrieval code despite declared dependencies, no validation checkpoints in the workflow, and a monolithic 260-line structure with no reference-file split for the rulebook detail.

Suggestions

Add a minimal executable data-retrieval snippet (e.g. tushare calls for 增减持/定增/激励公告) or drop the 'pip install pandas numpy' dependency line — currently code is promised but never shown, which is the main actionability gap.

Insert validation checkpoints into the workflow: verify announcement source freshness against 交易所官网/巨潮资讯 before acting, and sanity-check computed spreads against deal terms before sizing a position.

Move the detailed rulebooks (ST/退市 2024 rules, 股权激励 解读细则, the output-format template) into one-level-deep reference files under references/ and keep SKILL.md as a tighter overview with signaled links.

Isolate time-sensitive content (2024 ST 新规, 注册制-era notes, the 2023 spin-off example) into a versioned rules section so stale thresholds are easy to spot and update.

DimensionReasoningScore

Conciseness

The body is dense reference material that assumes domain competence — it never explains what M&A or an incentive plan is, and delivers A-share-specific knowledge Claude lacks (empirical excess-return ranges, 2024 ST rules, discount-rate thresholds) in tight tables and rule blocks. It sits at level 4 ('efficient; minor instances that could be trimmed') rather than 5 because time-sensitive specifics like "2024新规", "注册制后减少", and the dated 2023 spin-off example are not isolated in a rules-version section, and the sample output report adds length without being essential.

4 / 5

Actionability

Concrete, decision-ready guidance throughout: a worked spread calculation ("价差 = (25 - 23.5) / 23.5 = 6.38%"), quantitative filter rules ("排除: 被动减持(质押平仓)"), a fundraising-use scoring rubric (+3/-1), and a complete output report template with position sizes and stop levels. It misses level 5 because no executable code is provided despite a "pip install pandas numpy" dependency block and a mention that "tushare 提供增减持/股权激励/定增数据接口" — the data-retrieval step has no commands or code.

4 / 5

Workflow Clarity

There is a clear event timeline (T-30 → T → T+1..T+20 → T+N) and per-event analysis frameworks, giving a recognizable sequence, which places it above level 2. But no validation checkpoints exist anywhere — nothing on verifying announcement freshness (critical, since the notes warn third-party platforms lag), no cross-check of computed spreads against deal terms, and no error-recovery loop — matching level 3 ('sequence present but checkpoints missing or implicit') rather than 4.

3 / 5

Progressive Disclosure

The body is well-sectioned (概述 → 核心概念 → 分析框架 → 输出格式 → 注意事项) but is a ~260-line monolith with zero bundle files: no references/, scripts/, or assets/ exist, and substantial detail (ST/退市规则, 股权激励解读细则, 输出格式模板) that would sit better in one-level-deep reference files is inlined. This fits level 3 ('some structure but content that should be separate is inline'); the skill is far beyond the under-50-line simple-skill exception that would allow a 5 without external files.

3 / 5

Total

14

/

20

Passed

Description

71%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 dense, domain-specific description that names the skill's five concrete capabilities clearly and distinctively, but entirely omits explicit trigger guidance ('Use when...'). Adding a usage clause and a few more natural synonyms (借壳, 解禁, 回购) would lift completeness and trigger coverage.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks about A股 company announcements: 并购重组、增持/减持、股权激励、定增配股、ST/退市 risk."

Add common natural synonyms users would say — 借壳, 解禁, 回购, 摘帽 — so the description surfaces more entry-point phrasings.

Consider naming the output (an event-driven analysis report) so the 'what' also tells the user what they get.

DimensionReasoningScore

Specificity

The description lists five concrete, non-overlapping capabilities — "并购套利价差计算" (merger arb spread calculation), "大股东增减持信号" (major-holder increase/decrease signals), "股权激励解读" (equity incentive interpretation), "定增配股影响评估" (private placement/rights issue impact assessment), and "A股ST/退市预警" (ST/delisting warning) — which is comprehensive coverage of the domain's named sub-tasks. This matches the level-5 anchor ('lists multiple specific concrete actions; comprehensive coverage') and exceeds level 4 because no capability area of the skill body is missing from the description.

5 / 5

Completeness

The 'what' is clearly and specifically stated (the five capabilities above), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the when is only weakly implied by the domain vocabulary. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3, which is exactly the level-3 anchor ('has a clear what but when is missing or only weakly implied'); it is not level 4 because no explicit usage condition appears anywhere in the description.

3 / 5

Trigger Term Quality

Strong natural keywords an A-share analyst would actually say: 并购套利, 增持/减持, 股权激励, 定增, 配股, ST, 退市, A股. It falls at level 4 rather than 5 because common variations used in the body are absent from the description — e.g. 借壳, 解禁, 可交债, 回购, 摘帽 — leaving a few natural entry terms uncovered.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (China A-share corporate-event trading) with distinct trigger terms unlikely to fire for unrelated skills, matching 'mostly distinct; minor overlap risk'. It stops short of 5 because terms like 增持/股权激励/定增 could overlap with a broader A股量化 or 公告分析 skill covering the same events.

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

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.