CtrlK
BlogDocsLog inGet started
Tessl Logo

cs-req

能力愿景维护。触发:起草/回填/更新 requirements,或 design/acceptance 需要 req delta。不要用于单个功能实现方案(cs-feat design)、大需求拆解排期(cs-epic)、开放式发散讨论(cs-brainstorm)、领域术语/ADR建模(cs-domain)。

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/codestable/skills/cs-req/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.

The skill body is highly actionable with concrete templates, a well-sequenced workflow, and strong validation checkpoints. Its main weaknesses are cross-section redundancy that hurts conciseness and a monolithic structure that underuses progressive disclosure.

Suggestions

De-duplicate the single-target rule and sibling-skill boundaries, which recur in 启动必读, Spec, 适用场景, 硬性边界, and 常见错误 — state once and reference.

Move 常见错误 and 和其他工作流的关系 into a separate reference file (one level deep) to shrink SKILL.md and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes competence without explaining basics, but several concepts (single-target rule, non-use cases, sibling-skill relationships) are restated across 启动必读, Spec, 适用场景, 硬性边界, and 常见错误, so it could be tightened.

2 / 3

Actionability

Provides concrete, copy-paste-ready templates (frontmatter YAML, body section skeleton, 变更日志), exact file paths (requirements/{slug}.md, VISION.md), specific commands (grep -r, git log), and a逐条 self-check checklist — fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

Phase 1–6 is a clear sequence with explicit validation checkpoints (Phase 4 自查清单, Phase 5 用户 review, Phase 6 落盘), a 退出条件 checklist, and a Spec encoding HumanCheckpoint/NeedsHuman feedback loops, matching the top anchor.

3 / 3

Progressive Disclosure

Sections are well-organized and external references (shared-conventions.md, requirement-example.md) are clearly signaled with paths, but the ~300-line SKILL.md is monolithic with no bundle files splitting content (e.g., 常见错误, 和其他工作流的关系) that could live one level deep.

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.

The description clearly communicates purpose, trigger conditions, and boundaries against sibling skills, with explicit use-when guidance. It is slightly held back by abstract mode labels and jargon-heavy trigger phrasing rather than natural user language.

Suggestions

Replace abstract mode labels ('能力愿景维护') with concrete user-facing actions (e.g., '起草、回填、更新需求文档') to lift specificity.

Add natural-language trigger phrasings a user would actually say (e.g., '写需求', '补一份需求', '刷新需求') alongside the internal 'req delta' jargon.

DimensionReasoningScore

Specificity

Names the domain ('能力愿景维护') and three concrete modes ('起草/回填/更新 requirements'), but the actions are high-level mode labels rather than the granular concrete operations seen in top anchors.

2 / 3

Completeness

Explicitly states both what it does ('能力愿景维护') and when to trigger it ('触发:起草/回填/更新 requirements,或 design/acceptance 需要 req delta'), plus an explicit not-use clause, satisfying both what and when.

3 / 3

Trigger Term Quality

Includes relevant trigger terms ('requirements', 'design/acceptance', 'req delta') and sibling skill names, but coverage of natural phrasings a user would say is partial and mixed with internal jargon.

2 / 3

Distinctiveness Conflict Risk

The '不要用于...' clause explicitly carves out cs-feat design, cs-epic, cs-brainstorm, and cs-domain, giving a clear niche unlikely to trigger the wrong sibling 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.