CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

writing-plans

把已接受的愿景与需求转成接手者可实施、可验收的计划。 Use when: 跨组件、状态对象、依赖或实施顺序需要先理清,且没有足够的现成计划。 Not for: 路径已明确的简单改动、已有可执行计划、尚未接受的愿景决策。 Output: 目标与范围、关键契约/依赖、可执行工作单元和验证方式。

Quality

74%

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 ./cat-cafe-skills/writing-plans/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 an efficient, actionable instruction skill: project-specific rules, a ready-to-use plan skeleton, verified commands, and strong validation emphasis, with only minor token waste in dated provenance. Its one real defect is navigation — both an in-body reference to a non-existent shared-refs file and a removed-reference placeholder — which undercuts progressive disclosure.

Suggestions

Fix or remove the broken reference to ../.cat-cafe-shared-refs/delivery-intent-judgment.md (the file does not exist at that path relative to the skill) and delete the '*(internal reference removed)*' placeholder.

Move the dated incident provenance (F314 汉弗莱喵案 dates, thread-id citations) into a compact '来源/依据' footnote or separate reference file so the rules stay lean.

Add one short worked example for the cost/benefit rule (谁多付出什么、换来什么) to convert that directive from a requirement-statement into concrete guidance.

DimensionReasoningScore

Conciseness

The body is dense and project-specific (F314/F229 incident provenance, the Stateful Object Gate rules, real pnpm commands) and assumes Claude's competence — it never explains what a plan or a formatter is. Minor instances could be trimmed: the dated incident narration ("10-27 整层撤除", "You 10-29 批注认可") and dead placeholders like "`[thread-id]#private-source-id`" and "*(internal reference removed)*" earn little per token, which keeps it below anchor 5.

4 / 5

Actionability

Concrete, usable artifacts are provided: a copy-paste markdown plan skeleton, verified formatting commands ("pnpm check:fix", "pnpm biome format --write <files>", "pnpm check"), a numbered end-state splitting method, and a misconception/correction table. As an instruction-only skill the guidance is actionable, but several directives remain requirement-statements without a worked example (e.g., the cost/benefit rule "写清这个方案让谁多付出什么、换来什么" has no illustrative example), so it is not fully anchor 5.

4 / 5

Workflow Clarity

The flow is legible: judge whether input is already an implementable agreement (clarify if not), apply the must-do checklist and Stateful Object Gate, optionally follow the numbered 4-step end-state method, then the formatting contract and 下一步. Validation checkpoints are emphasized (per-unit verification, tdd for behavior risk, "终态验证:`pnpm check`"). It is not anchor 5 because no single explicit end-to-end sequence with error-recovery feedback loops is laid out; the sequence is distributed across sections.

4 / 5

Progressive Disclosure

Sections are well-organized and appropriately sized for an in-file guidance skill, but navigation is broken at its reference points: the one clearly-signaled reference "[原问题到交付的判断方法](../.cat-cafe-shared-refs/delivery-intent-judgment.md)" points to a path that does not exist relative to the skill, and "*(internal reference removed)*" is a dead placeholder. No bundle files (references/, scripts/, assets/) exist to offload detail. This sits between anchors 3 and 4: structure is good, but the referenced paths fail, which anchor 4's 'references mostly clear' does not cover.

3 / 5

Total

15

/

20

Passed

Description

67%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 is well-formed with explicit what/when/not-for structure and concrete deliverables, giving it strong completeness and reasonable distinctiveness. Its main weakness is trigger-term quality: the when-clause states conditions rather than natural user phrasings, and the natural keywords live only in the separate triggers field.

Suggestions

Mirror the natural trigger phrases from the triggers field (写计划, implementation plan, 拆分步骤) into the description's 'Use when' clause so users' actual wordings appear in the description itself.

Add common synonyms or variations users might say (e.g., 制定实施方案, break down tasks, 实施步骤拆分) to broaden keyword coverage.

Consider phrasing the when-clause partly in user-mention form (e.g., 'when the user asks for an implementation plan or task breakdown') to move completeness and distinctiveness to the top anchor.

DimensionReasoningScore

Specificity

The description states a concrete core action ("把已接受的愿景与需求转成接手者可实施、可验收的计划") and enumerates concrete deliverables ("Output: 目标与范围、关键契约/依赖、可执行工作单元和验证方式"), listing several specific items. It falls short of anchor 5 because capability coverage beyond producing a plan is narrow, but exceeds anchor 3 since it names more than 1-2 concrete actions/outputs.

4 / 5

Completeness

Both what ("把已接受的愿景与需求转成接手者可实施、可验收的计划" plus the Output list) and when (explicit "Use when:" clause, sharpened by a "Not for:" exclusion list) are explicitly present. It sits between anchors 4 and 5: the when is specific and condition-based rather than phrased as concrete user-mention triggers, so anchor 5's 'concrete trigger phrases' criterion is not fully met, but it is clearly more explicit than anchor 4 allows.

4 / 5

Trigger Term Quality

The when-clause ("Use when: 跨组件、状态对象、依赖或实施顺序需要先理清,且没有足够的现成计划") describes triggering situations with relevant domain terms (计划, 依赖, 状态对象, 实施顺序) but not the natural phrases a user would actually say. The natural keywords ("写计划", "implementation plan", "拆分步骤") exist only in the separate triggers frontmatter field, not in the description itself, so common variations and synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

The niche is clear — turning already-accepted vision/requirements into implementable, acceptance-ready plans for a hand-off implementer — and the "Not for: 路径已明确的简单改动、已有可执行计划、尚未接受的愿景决策" clause explicitly excludes adjacent situations, keeping overlap with general execution or simple-change skills minor. Not anchor 5 because distinctiveness rests on conditions rather than distinct trigger phrases inside the description.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

zts212653/clowder-ai

Path

cat-cafe-skills/writing-plans/SKILL.md

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.