CtrlK
BlogDocsLog inGet started
Tessl Logo

convertible-bond

A股可转债分析——转股/纯债/期权三维估值、下修/强赎/回售博弈、双低策略与转债轮动选债框架

53

Quality

67%

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/convertible-bond/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 delivers strong domain substance — A-share-specific clause thresholds, a decision matrix, concrete screening criteria, and an output template — but it is a monolithic, explanation-heavy document. The strategy engine is unexecuted pseudocode, workflows lack validation checkpoints, and everything lives in one file rather than being progressively disclosed.

Suggestions

Remove the duplicate 转股价值 formula (keep one occurrence) and cut textbook explanations of basic mechanics (纯债价值含义 bullets), keeping only A-share-specific thresholds and conventions Claude would not know.

Make the strategy layer executable or delete the stub: either implement ConvertibleBondEngine.generate (double-low computation, Top-N selection, monthly rebalance) with real tushare field names, or drop the class and specify the signal rule in prose with concrete numbers.

Add validation checkpoints to the rotation/backtest workflow (e.g., verify 转股价/强赎公告 fields are present and non-null after fetching, cross-check 双低值 against price and premium before ranking).

Split detail into one-level-deep reference files (e.g., references/clause-playbooks.md for 下修/强赎/回售 game details, references/backtest.md for the 回测框架) and keep SKILL.md as a concise overview with clearly signaled links.

DimensionReasoningScore

Conciseness

The body is dense and mostly signal (clause trigger thresholds, decision matrix, output template), but it re-explains textbook convertible-bond mechanics Claude already knows — e.g., the 转股价值 formula appears twice (lines 31-32 and 72) and bullets like "纯债价值越高 → 债底保护越强 → 下跌空间有限" are explanatory padding. Not a 2 because there is no generic library/tutorial padding and most sections carry A-share-specific detail Claude cannot infer.

3 / 5

Actionability

There is one complete executable function (bond_floor) plus concrete numeric thresholds (双低筛选: <130, 价格<115, 溢价率<30%, 评级≥AA-) and a concrete output-format template. However, the core strategy engine (ConvertibleBondEngine) is a pseudocode stub with 'pass', and data retrieval via tushare is mentioned without any executable code — key details are missing.

3 / 5

Workflow Clarity

The 轮动流程 gives a real 5-step sequence (筛选→打分→排名→选Top 15-20→月调仓) and 下修/强赎/回售 analyses are ordered, so a sequence exists. But there are no validation checkpoints anywhere (no data-quality checks, no signal sanity checks), and the monthly batch rebalancing/backtest workflow falls under the rubric's batch-operation cap of 3. Not a 2 because step 1 does embed an implicit filter (剔除已退市/已公告强赎/评级<A+) and the sequence is coherent and well-defined.

3 / 5

Progressive Disclosure

The file is well-sectioned (概述/基础概念/三维估值/条款博弈/双低策略/轮动/输出格式/注意事项) with no nested or dead references, but it is a single ~250-line monolith: the detailed clause-game playbooks and the backtest framework are inline content that would fit better in separate reference files. There are no bundle files at all, so all detail must load into context on every invocation. Not a 2 because the structure and section headers make it genuinely navigable; not a 4+ because nothing is split out and the file exceeds the size where a single file can score 5.

3 / 5

Total

12

/

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 rich in natural domain trigger terms, carving out a distinct niche with minimal conflict risk. Its main weakness is the absence of any explicit 'Use when...' guidance, which caps its completeness and leaves trigger conditions to inference.

Suggestions

Append an explicit trigger clause, e.g. '适用于:用户询问可转债/转债的估值、下修/强赎/回售条款、双低选债或转债轮动回测时使用' (equivalent of 'Use when...').

Lead with action verbs in third person (e.g. '对A股可转债进行…估值、判断…条款博弈、构建…策略') to make the capability list read as concrete actions rather than noun phrases.

Add one or two common synonyms users actually say, such as standalone '转债' and 'convertible bond', to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("A股可转债分析") and lists several concrete capability areas — "转股/纯债/期权三维估值", "下修/强赎/回售博弈", "双低策略", "转债轮动选债框架" — which map directly onto the skill's scope. Not a 5 because these are noun phrases rather than explicit actions and coverage of the body's full scope (e.g., risk caveats) is implied rather than stated.

4 / 5

Completeness

The "what" is clear and multi-part (three-dimensional valuation, clause-gaming analysis, double-low strategy, rotation framework), but there is no "Use when / 适用于..." trigger clause, so "when" is entirely absent. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3; it is not a 2 because the "what" is concrete, not vague.

3 / 5

Trigger Term Quality

Contains the natural terms a Chinese-speaking user would say when needing this skill: "可转债", "转股", "纯债", "下修", "强赎", "回售", "双低", "轮动", "估值". Not a 5 because a few common synonyms/variations are missing (e.g., "转债" alone, "申购/打新", "信用风险", English "convertible bond").

4 / 5

Distinctiveness Conflict Risk

A clear niche (A-share convertible bonds) with highly distinct triggers — "下修", "强赎", "回售", "双低" are vocabulary unique to convertibles and would not fire a generic stock/bond analysis skill. Not a 4 because overlap with generic A-share equity or fixed-income skills is minimal given these clause-specific terms.

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.

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.