CtrlK
BlogDocsLog inGet started
Tessl Logo

cs-goal

Goal 自主达成。触发:明确终点/验收/预算、持续迭代到完成,或 grill me 后开工。不要用于单个功能的规划与实现(cs-feat)、大需求端到端拆解(cs-epic)、bug 诊断修复(cs-issue)、行为等价重构(cs-refactor)、对外文档(cs-docs);也不用于没有实现终点的纯 design / roadmap / brainstorm / audit。

76

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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 tightly written, well-sequenced governance spec with explicit checkpoints and actionable file-level guidance. Its one weakness is progressive disclosure: multiple reference files are cited but none are present in the bundle, so the signaled navigation does not resolve to real files.

Suggestions

Create the referenced bundle files (reference.md, goal-conventions.md, approval-conventions.md, agent-conventions.md, solution-depth-conventions.md) under references/ so the signaled navigation resolves, or remove citations to files that do not exist.

If some conventions are intentionally external to this skill bundle, state explicitly that they live outside this skill (e.g. in .codestable/reference/) so progressive_disclosure can be scored against an accurate source-of-truth rather than the missing local bundle.

DimensionReasoningScore

Conciseness

The body is dense with contracts, paths, and routing rules and assumes Claude's competence without explaining known concepts; no padded verbosity despite ~290 lines for a complex skill. Not level 2 because there is little that could be tightened without losing actionable detail.

3 / 3

Actionability

Gives concrete executable-level guidance (file paths, state.yaml fields, iteration numbering rules, selectNextAttempt guards, canonical report paths); Haskell is spec/governance pseudocode for an instruction-only driver skill, which the scoring notes exempt from the executable-code penalty when guidance is actionable. Not level 2 because the instructions are specific and copy-applicable rather than vague direction.

3 / 3

Workflow Clarity

Clear sequenced mainline (preflight → restore → selectNextAttempt → execute → record → exit) with explicit validation checkpoints (functional-acceptance gate, owner-stop triggers, three-state exit) and feedback loops for risky transitions. Not level 2 because checkpoints and error-recovery are explicit, not implicit.

3 / 3

Progressive Disclosure

The body signals one-level-deep references (reference.md, goal-conventions.md, approval-conventions.md, agent-conventions.md, solution-depth-conventions.md) with on-demand loading, but none of these bundle files actually exist under references/ scripts/ or assets/, so the structure is described rather than backed by real files. Not level 3 because the referenced paths cannot be navigated; not level 1 because the SKILL.md itself is well-organized and references are clearly signaled one level deep.

2 / 3

Total

11

/

12

Passed

Description

100%

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, third-person, and gives explicit positive and negative triggers with named sibling skills for disambiguation. It cleanly answers what the skill does and when to use it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the goal lifecycle ("grill me 后开工", "持续迭代到完成", 自主实现/验证/迭代) rather than abstract language; not the level-2 single-domain anchor because it enumerates distinct verbs and stages.

3 / 3

Completeness

Explicitly answers both what ("Goal 自主达成") and when (explicit "触发:" clause plus an explicit "不要用于..." anti-trigger list), satisfying the level-3 what-AND-when anchor.

3 / 3

Trigger Term Quality

Includes natural owner-facing trigger phrases a user would say ("明确终点/验收/预算", "grill me 后开工") with good coverage of variations, matching the level-3 natural-keywords anchor.

3 / 3

Distinctiveness Conflict Risk

Names sibling skills by id (cs-feat, cs-epic, cs-issue, cs-refactor, cs-docs) and lists exclusions, giving a clear niche unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation15 / 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
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.