CtrlK
BlogDocsLog inGet started
Tessl Logo

cs-onboard

CodeStable 接入。触发:初始化/迁移/搭骨架,自动判断空仓库或已有文档。

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/codestable/skills/cs-onboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong procedural skill: highly actionable executable commands, excellent workflow sequencing with validation checkpoints and resume loops, and no filler. Its two weaknesses are repetition that inflates length and a progressive-disclosure gap where several bundle files the procedure depends on are referenced but not actually present, plus inline content (the OCR guide) that would read better as a reference file.

Suggestions

Ship the missing referenced bundle files (reference.md, codestable.gitignore, gates/, and tools/ with codestable-runtime-sync.py and codestable-doctor.py) alongside SKILL.md, since the onboarding procedure cannot execute without them.

De-duplicate the repeated 'cp -rf not Read+Write' and 'gates/reference must overwrite' rules into a single stated-once convention to tighten conciseness.

Move the optional open-code-review configuration guide (lines 219-263) into a separate reference file and keep only a one-line lazy-load pointer in SKILL.md, reducing inline bulk while preserving the opt-in behavior.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence (no basic-concept explanations), but at ~290 lines it repeats guidance several times — the 'cp -rf, not Read+Write' rule appears at lines 128, 191, and 288, and the 'gates/reference must overwrite' rule repeats at lines 79, 173, and 287 — so it could be tightened.

2 / 3

Actionability

It provides fully executable, copy-paste-ready commands for both macOS/Linux and Windows (cp -rf, python3 .../codestable-runtime-sync.py --root . --source-skill-dir ... --force, ocr config set provider anthropic, etc.) with real flags and a clear instruction to ls-locate the skill directory.

3 / 3

Workflow Clarity

Multi-step paths are explicitly sequenced (空仓库 steps 1-4, 迁移 steps 1-7) with explicit validation checkpoints (runtime sync --check --json, 'ocr llm test' must show ✓, ls verification, doctor self-check), formalized HumanCheckpoint→resumeOnboard feedback loops, and a 退出条件 checklist.

3 / 3

Progressive Disclosure

The well-organized references/ folder (13 files) is pointed to one level deep (e.g. shared-conventions.md, system-overview.md), but the body heavily references execution-critical bundle files that are missing from the actual bundle — reference.md (lines 122/209), codestable.gitignore (lines 120/182), gates/ (lines 122/181), and tools/ with codestable-runtime-sync.py and codestable-doctor.py (lines 104/183/261) — and the large optional OCR section (lines 219-263) is inline rather than split out.

2 / 3

Total

10

/

12

Passed

Description

75%

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 compact, third-person description that explicitly answers both 'what' and 'when' with a trigger clause, giving it strong completeness and distinctiveness. Specificity and trigger-term coverage are only moderate because the listed actions are generic verbs and omit several capabilities and phrasings a user might naturally invoke.

Suggestions

Add one or two more concrete capabilities to the description (e.g. runtime refresh, legacy-directory compat) so specificity reflects the full skill rather than just init/migrate/scaffold.

Broaden the trigger list with natural user phrasings beyond 初始化/迁移/搭骨架, such as "接入项目" / "升级 runtime" / "兼容旧 easysdd 或 codestable 目录", to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ("CodeStable 接入") and several actions ("初始化/迁移/搭骨架", "自动判断空仓库或已有文档"), but the verbs are fairly high-level and not comprehensive — the body reveals more capabilities (refresh-runtime, legacy compat, OCR) than the description conveys.

2 / 3

Completeness

It states both what ("CodeStable 接入") and when via an explicit trigger clause ("触发:初始化/迁移/搭骨架"), satisfying the 'Use when...' equivalent requirement that would otherwise cap this at 2.

3 / 3

Trigger Term Quality

The explicit "触发:初始化/迁移/搭骨架" label surfaces natural developer terms, but coverage is thin and missing common variations a user might say (e.g. "接入项目", "升级 runtime", "兼容旧目录").

2 / 3

Distinctiveness Conflict Risk

The "CodeStable" scope gives it a clear niche with distinct triggers (初始化/迁移/搭骨架), making it unlikely to fire for a non-CodeStable skill.

3 / 3

Total

10

/

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.