CtrlK
BlogDocsLog inGet started
Tessl Logo

cs-feat-accept

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

66

Quality

78%

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-feat-accept/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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-structured, token-efficient delegation shim that gives concrete instructions, a clear sequenced workflow with a failure checkpoint, and appropriately defers all detail to the cs-feat main protocol.

DimensionReasoningScore

Conciseness

The body is lean and explicitly avoids duplicating cs-feat's rules ("不在本文件复制阶段流程、模板或 gate 规则"), with every line earning its place and no padding with concepts Claude already knows.

3 / 3

Actionability

As an instruction-only delegation skill it provides concrete, specific guidance — load cs-feat as the authoritative protocol by installed name, continue with the entry intent, and stop-and-report on load failure — which is actionable without code per the rubric's instruction-only allowance.

3 / 3

Workflow Clarity

The four numbered execution rules give a clear sequence with an explicit error-recovery checkpoint (rule 4: stop and report if the main protocol cannot load), satisfying the top anchor for a simple, well-organized skill.

3 / 3

Progressive Disclosure

Content is appropriately deferred to the authoritative cs-feat skill and its references/ rather than inlined, and the body is cleanly sectioned (执行规则, 维护规则), matching the top anchor for a short, single-purpose skill with no local bundle needed.

3 / 3

Total

12

/

12

Passed

Description

57%

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 correctly frames this as a deprecated compatibility forwarder with a clear niche, but it relies on a single technical trigger term and lacks an explicit "Use when..." clause, capping completeness and specificity below the top level.

Suggestions

Add an explicit trigger clause such as 'Use only for legacy cs-feat-accept invocations' to raise completeness.

Include a natural-language variation of the trigger (e.g., 'feature acceptance') alongside the command name to broaden trigger-term coverage.

Briefly state the concrete forward action in plain terms before the command syntax to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ("兼容入口"/compatibility entry) and a concrete action ("转交 cs-feat --stage accept"/forwards to cs-feat --stage accept), but it is a single delegation action rather than multiple specific concrete actions, so it does not reach the level-3 anchor.

2 / 3

Completeness

It states what it does (forwards to cs-feat --stage accept) and implies when ("旧 cs-feat-accept 调用用"/for old calls), but it lacks an explicit "Use when..." clause, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

The natural trigger term is the deprecated command name "cs-feat-accept", which is relevant but is technical command syntax with limited coverage of common variations, matching the level-2 anchor rather than broad natural-term coverage.

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche as a deprecated shim that forwards to cs-feat --stage accept and explicitly instructs that new requests should not proactively select it, making it unlikely to trigger for the wrong skill despite the sibling cs-feat relationship.

3 / 3

Total

9

/

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.