CtrlK
BlogDocsLog inGet started
Tessl Logo

cs-issue-fix

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

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-issue-fix/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 an efficient, well-organized dispatcher shim with a clear sequenced workflow and an explicit failure checkpoint. Its only weakness is actionability: the 'load cs-issue' step is a directive rather than a concrete, executable mechanism.

DimensionReasoningScore

Conciseness

The ~24-line body is a lean shim with no padding and no explanation of concepts Claude already knows; every line earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

It gives concrete directives (load the master protocol by installed skill name, carry requested_stage: fix, stop-and-report on failure) but provides no executable command or concrete load mechanism, fitting 'some concrete guidance but incomplete'.

2 / 3

Workflow Clarity

The four-step execution sequence is clearly ordered and includes an explicit failure checkpoint (step 4: stop and report if the master protocol cannot load), meeting the anchor for clear sequence with validation steps.

3 / 3

Progressive Disclosure

Under 50 lines with no bundle files needed, the content is organized into well-signaled sections (执行规则, 维护规则) and explicitly defers detailed rules to cs-issue and its references/, satisfying the simple-skill anchor.

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 is concise and clearly signals its deprecated-compatibility role, but it relies on technical skill-name jargon rather than natural trigger terms and lacks an explicit user-facing 'Use when' clause. It is adequate for a deprecation shim but scores low on trigger quality and completeness.

Suggestions

Add an explicit natural-language trigger, e.g. 'Use when an old prompt or call still references cs-issue-fix; for new work use cs-issue directly.'

Replace the skill-name-only trigger with phrases a user would actually say (e.g. 'fixing an issue', 'issue fix stage') to improve trigger_term_quality beyond technical jargon.

Clarify the 'what' with one more concrete action (e.g. 'loads the cs-issue protocol and continues at the fix stage') to lift specificity toward multiple concrete actions.

DimensionReasoningScore

Specificity

Names a concrete action ('转交 cs-issue --stage fix') and a domain (兼容入口), but lists only a single forwarding action rather than multiple specific concrete actions, so it falls short of anchor 3.

2 / 3

Completeness

It states what (compatibility entry forwarding to cs-issue --stage fix) and a when ('旧 cs-issue-fix 调用用'), but the when is deprecation-maintenance framing rather than an explicit 'Use when...' user-need trigger, so it does not reach anchor 3.

2 / 3

Trigger Term Quality

The only 'trigger' is the technical skill name '旧 cs-issue-fix 调用' — jargon a user would not naturally say — with no natural-language keywords, matching the 'technical jargon or overly generic' anchor rather than anchor 2.

1 / 3

Distinctiveness Conflict Risk

It occupies a clear narrow niche (legacy compatibility only), but by design overlaps heavily with its sibling 'cs-issue' skill, fitting the 'somewhat specific but could still overlap' anchor.

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.