CtrlK
BlogDocsLog inGet started
Tessl Logo

cs-epic

Epic 主入口。用于大需求或系统级能力的端到端拆解与长程执行:planning、review、子 feature design(批量)、goal 包。不要用于单个功能(cs-feat)、bug 修复(cs-issue)、行为等价重构(cs-refactor)、对外文档(cs-docs)。

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

A well-structured, concise orchestration skill with clear sequencing, explicit validation checkpoints, and clean one-level-deep progressive disclosure. The main weakness is actionability: the authoritative spec is pseudocode and the one real command contains a path placeholder, so guidance is not fully copy-paste ready.

Suggestions

Resolve the placeholder in the executable command (e.g., give an absolute or discoverable path for codestable-workflow-next.py) so the workflow hook is copy-paste ready.

Where the Haskell spec encodes concrete rules, mirror the load-bearing ones as a short imperative checklist or table so they remain actionable without parsing the typed model.

DimensionReasoningScore

Conciseness

The body is dense and lean — compact Haskell-spec blocks and terse prose that assume Claude's competence, with no padding explaining basic concepts; every section earns its place.

3 / 3

Actionability

Provides one concrete executable command and exact file paths, but the core spec is Haskell-like pseudocode and the command path uses a placeholder ('<cs-onboard skill 目录>'), leaving it not fully copy-paste ready.

2 / 3

Workflow Clarity

The main pipeline is explicitly sequenced (preflight > parseEntryIntent > ... > exitRecoverable) with explicit validation checkpoints (HumanCheckpoint, design-review gates, batchLoopSettled, stateRecoverable) and fail-closed feedback loops for batch/destructive operations.

3 / 3

Progressive Disclosure

The body is an overview mapping each stage to one-level-deep references (references/{planning,review,goal}/protocol.md and support files, all present on disk) with explicit lazy-load discipline, splitting detailed protocols out of the main file.

3 / 3

Total

11

/

12

Passed

Description

85%

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 specific, well-scoped description that clearly defines the epic skill's niche and explicitly disambiguates it from siblings via negative scope. Trigger terms are more internal/jargon than natural user language, slightly weakening trigger-term quality.

Suggestions

Add natural-language triggers users would actually say (e.g., 'Use when the request is too large for one feature', 'when you need to break a big requirement into stages') alongside the internal skill names.

Consider adding an explicit 'Use when...' clause to make the positive trigger guidance unambiguous rather than relying on '用于...'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'planning、review、子 feature design(批量)、goal 包' and '端到端拆解与长程执行' — matching the 'Lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly states what it does ('端到端拆解与长程执行') and when to use it ('用于大需求或系统级能力') plus negative scope ('不要用于...'), answering both what and when with explicit triggers.

3 / 3

Trigger Term Quality

Includes some relevant terms ('大需求', '系统级能力') but leans on internal skill names (cs-feat, cs-issue) and jargon ('goal 包', '长程执行') rather than natural language a user would say; missing common natural variations.

2 / 3

Distinctiveness Conflict Risk

The explicit negative-scope list ('不要用于单个功能(cs-feat)、bug 修复(cs-issue)、行为等价重构(cs-refactor)、对外文档(cs-docs)') carves out a clear niche and disambiguates from sibling skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 deeper-than-1-level

Warning

Total

14

/

16

Passed

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.