CtrlK
BlogDocsLog inGet started
Tessl Logo

cs-roadmap

Deprecated 兼容入口:旧 cs-roadmap 调用用;转交 cs-epic --stage planning。新请求不要主动选择。

54

Quality

60%

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 ./plugins/codestable/skills/cs-roadmap/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 tight, well-structured delegation contract with a clear sequenced workflow and an explicit failure checkpoint. Its only real gap is that the mechanism for loading the target skill is stated directionally rather than as an executable instruction.

DimensionReasoningScore

Conciseness

The body is lean and purposeful: every line (entry intent, four execution rules, three maintenance rules) carries an instruction with no padding or re-explanation of concepts Claude already knows, matching the level-3 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

The execution rules give concrete directional guidance (load cs-epic, continue with requested_stage: planning, do not require re-invocation), but the actual mechanism for 'load cs-epic by installed skill name' is left implicit with no executable command or specific instruction, matching the level-2 'some concrete guidance but incomplete' anchor rather than fully copy-paste-ready.

2 / 3

Workflow Clarity

A clear four-step sequence is given and step 4 is an explicit failure checkpoint ('如果当前运行时无法加载主入口协议,停止并报告'), providing the error-recovery feedback loop the level-3 anchor rewards.

3 / 3

Progressive Disclosure

The skill is under 50 lines, owns no bundle files (references/scripts/assets absent), and is organized into well-signaled sections (执行规则, 维护规则), which the simple-skills scoring note permits to score 3 without external file references.

3 / 3

Total

11

/

12

Passed

Description

35%

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 clearly signals deprecation and a concrete forwarding action, but relies on internal jargon rather than natural user trigger terms and lacks an explicit 'Use when...' clause. It is functional for a compatibility shim but weak as user-facing discovery text.

Suggestions

Add natural user-facing trigger terms or a 'Use when...' clause (e.g., 'Use when an old cs-roadmap call or prompt arrives') so the skill surfaces for the right legacy requests.

Reword internal jargon like '兼容入口' and 'requested_stage: planning' into language a user would actually say, or pair them with plain-language equivalents.

State the when-condition explicitly rather than implying it through the deprecation framing, to lift completeness above the level-2 cap.

DimensionReasoningScore

Specificity

It names the domain ("兼容入口" for cs-roadmap) and a concrete action ("转交 cs-epic --stage planning"), but lists only a single forwarding action rather than multiple specific concrete actions, matching the level-2 anchor and falling short of the level-3 'lists multiple specific concrete actions'.

2 / 3

Completeness

It states what the skill does (forward to cs-epic --stage planning), but the 'when' is only implied via the legacy framing and there is no explicit 'Use when...' clause, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

The terms present ("兼容入口", "cs-roadmap 调用", "cs-epic --stage planning", "requested_stage: planning") are internal orchestration jargon, not natural keywords a user would actually say, matching the level-1 'technical jargon' anchor.

1 / 3

Distinctiveness Conflict Risk

It occupies a clear niche as a deprecated cs-roadmap shim, but by design it forwards to and overlaps with cs-epic, matching the level-2 'somewhat specific but could still overlap with similar skills' anchor rather than a fully distinct trigger.

2 / 3

Total

7

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
codestable/CodeStable
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.