CtrlK
BlogDocsLog inGet started
Tessl Logo

cs-onboard

仓库接入 CodeStable:创建最小骨架,或为 v1 存量项目做无损升级说明。

58

Quality

66%

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

Quality

Content

78%Weight 40%Scale 1-5

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, instruction-only skill with concrete guidance and genuine validation/feedback for its risky .gitignore interaction. Its main gaps are the absence of literal executable commands and the long inline v1-directory list.

Suggestions

Provide literal shell commands for skeleton creation (e.g. `mkdir -p .codestable/lessons .codestable/work && touch .codestable/attention.md`) to make the guidance copy-paste ready.

Consider moving the enumerated list of v1 legacy directories into a short reference table so the hard-gate section reads even more concisely.

Make the workflow sequence explicit with a short numbered list (create → verify gitignore → report) to lift workflow clarity toward the top anchor.

DimensionReasoningScore

Conciseness

The body is dense and lean with no padding or explanation of concepts Claude already knows; every line is an actionable constraint, though the inline enumeration of v1 directories to preserve is long (necessary for the hard gate but could live in a reference), placing it just below the leanest anchor.

4 / 5

Actionability

Concrete, specific instruction guidance is present — exact filenames (attention.md, lessons/, work/), an explicit gitignore check, and a three-point user-facing upgrade message — but no literal shell commands are given, leaving a minor gap versus copy-paste-ready execution.

4 / 5

Workflow Clarity

A clear create → verify → report sequence exists with a real validation checkpoint ("创建后确认 .codestable/ 未被 .gitignore 忽略") and a feedback loop ("发现被忽略时停下报告,由用户决定"), plus a cleanup report of git status; it avoids the destructive-operation cap of 3 because validation is present, but the steps are not explicitly numbered like the top anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained with no need for external references (no references/scripts/assets bundles exist), and organized into well-signaled sections (骨架, 硬门槛, v1 升级说明, 收尾), matching the simple-skill exception that allows a 5 for well-organized content.

5 / 5

Total

17

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 states the skill's purpose and niche but is terse, jargon-heavy, and lacks an explicit "Use when..." trigger clause. It conveys what the skill does but not precisely when Claude should invoke it.

Suggestions

Add an explicit trigger clause, e.g. "Use when a repository needs to be onboarded to CodeStable or an existing v1 CodeStable project must be upgraded losslessly."

Include common user phrasings or synonyms (e.g. "接入 CodeStable", "初始化 .codestable", "升级 v1") so the trigger terms match what users naturally say.

List 1-2 more concrete actions (e.g. "creates .codestable/attention.md, lessons/, work/"; "reports retained v1 artifacts and git status") to raise specificity.

DimensionReasoningScore

Specificity

Names the domain (CodeStable onboarding) and two concrete actions — "创建最小骨架" and "为 v1 存量项目做无损升级说明" — but the actions are high-level rather than enumerating specific steps, matching the anchor that names 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

The "what" is stated clearly (create minimal skeleton / lossless v1 upgrade), but there is no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3 with only a weakly implied "when".

3 / 5

Trigger Term Quality

Relevant domain keywords like "仓库接入 CodeStable" and "v1 存量项目" are present, but the phrasing is technical jargon with no common synonyms or variations a user would naturally say, fitting the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

"仓库接入 CodeStable" carves a clear onboarding niche that is mostly distinct, though the broader CodeStable skill family (cs-keep, cs-epic referenced in the body) creates minor overlap risk with closely related skills.

4 / 5

Total

13

/

20

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.