CtrlK
BlogDocsLog inGet started
Tessl Logo

cs-note

attention 短规则追加。触发:一两行、长期有效、每次会话都必须知道的项目规则;详细经验走 cs-keep,结构性决策走 cs-domain。

67

Quality

80%

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-note/SKILL.md
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.

The body is highly actionable with a concrete template, thresholds, and a sequenced workflow with built-in checkpoints. Its only real weakness is repetition of a few key rules across sections, which inflates length for a single-purpose skill.

Suggestions

State the 'AGENTS.md/CLAUDE.md are not a substitute; use cs-docs-neat for external-entry sync' rule once in 目标文件 and reference it from 容易踩的坑 instead of repeating the full rationale three times.

Merge the 150-line and 其他≥5 soft-cap guidance into a single checkpoint location (流程 step 5) and drop the duplicate statement in 固定分节结构.

DimensionReasoningScore

Conciseness

The body is focused and free of generic concept explanations, but several points are restated across sections (the AGENTS.md/CLAUDE.md-not-a-substitute rule appears in 启动必读, 目标文件, and 容易踩的坑; the 150-line soft cap appears in both 固定分节结构 and 流程), so it could be tightened.

2 / 3

Actionability

Concrete file paths, a copy-paste-ready fixed-section markdown skeleton, an exact entry format with worked examples, and numeric thresholds (150 lines, 5 条) give fully executable, specific guidance.

3 / 3

Workflow Clarity

The 流程 section is a clearly sequenced 5-step process with explicit gating checkpoints (judge-whether-to-enter in step 1, dedup query in step 3, soft-cap checks in step 5) plus a Failure Behavior branch.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the skill is self-contained and well-organized into clearly labeled sections (启动必读, Spec, 目标文件, 流程, 容易踩的坑, 退出条件), matching the simple-skill allowance for well-organized single-file content.

3 / 3

Total

11

/

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.

The description cleanly states the skill's purpose and trigger, and explicitly differentiates it from sibling skills, which prevents conflict. It is slightly under-specified on concrete actions and its trigger phrasing is criteria-based rather than user-natural.

Suggestions

Add 1-2 concrete verbs to the description (e.g. 'append a one-line fact to a fixed section, after deduping against existing entries') so the capability reads as comprehensive rather than a single action.

Reword the trigger around phrases a user would actually say (e.g. 'Use when the user drops a short, permanent project gotcha like 先 gen 再编译 or 别用 npm install') rather than abstract criteria.

DimensionReasoningScore

Specificity

Names a concrete action ("attention 短规则追加") and routing to cs-keep/cs-domain, but does not enumerate the multiple specific operations (locate anchor, classify section, dedup, append) — closest to 'names domain and some actions, but not comprehensive'.

2 / 3

Completeness

Clearly answers what ("attention 短规则追加") and when (explicit "触发:" guidance), matching the anchor requiring both an explicit what and an explicit trigger.

3 / 3

Trigger Term Quality

Has an explicit "触发:" clause with descriptors like "一两行、长期有效、每次会话都必须知道", but these are meta-criteria rather than the natural phrasings a user would actually say, so common variations are missing.

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche by contrasting against cs-keep (detailed experience) and cs-domain (structural decisions), making mis-triggering unlikely.

3 / 3

Total

10

/

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.