CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

co-creation-docs

共创文档与已选头像原图归档交付:区分只审阅与授权落盘,再按冲突、治理风险、可逆性决定 direct push、PR 和验证。

Quality

72%

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/co-creation-docs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-structured, lean policy skill with concrete classifier and validation commands, clear decision tables, and explicit positive/negative/grey examples. Main residual gaps are the unsequenced avatar-archive lane and dense multi-point paragraphs that could be broken into lists.

DimensionReasoningScore

Conciseness

The body is dense, house-specific policy prose (e.g. "用户说 review 不等于授权落盘", "行数不入模型") that assumes Claude's competence and contains no padding of known concepts. Not 5 because a few run-on blocks (the PR-path governance paragraph, the avatar-archive prose) could be tightened.

4 / 5

Actionability

Concrete executable commands are provided ("pnpm classify:co-creation-docs -- --base origin/main --conflict none --reversibility one_commit", "node scripts/check-frontmatter.mjs --strict-delta --base origin/main") plus decision tables and enumerated criteria. Minor gaps remain: the avatar lane has no commands and "跑轻量增量校验" defers to elsewhere rather than inlining the command.

4 / 5

Workflow Clarity

Clear sequencing: intent gate → classification evidence → per-delivery numbered steps with explicit checkpoints (validation first, staged-diff check, evidence report), so the destructive/batch validation cap does not apply. Not 5 because the static_asset_archive lane is prose without an explicit step sequence and validate→fix→retry loops are not spelled out.

4 / 5

Progressive Disclosure

Single-file skill with well-organized sections (价值门禁 → 先判意图 → 分类证据 → 按输出交付 → 正反灰例 → Common Mistakes → 验证 → skill 区别 → 下一步) and no bundle files to reference. Not 5 because at ~110 lines the dense lanes (avatar archive, governance paragraph) could be split into reference files.

4 / 5

Total

16

/

20

Passed

Description

58%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 states a clear, fairly specific "what" with concrete delivery outcomes and risk factors, but lacks an explicit "use when" trigger clause and natural-utterance keywords, which caps completeness and trigger quality. Adding a use-when clause with everyday phrases (e.g. English/Chinese synonyms like "docs-only", "落盘这些文档") would lift both dimensions.

Suggestions

Append a "Use when…" clause to the description (e.g. 'Use when the user asks to co-create, land, or archive docs/selected avatar originals, or says docs-only / 落盘 / 提交文档') so completeness is not capped at 3.

Replace some decision-machinery jargon (冲突/治理风险/可逆性) with natural user-facing trigger phrases and their synonyms in both Chinese and English to improve trigger term quality.

State the avatar-archive lane's concrete actions (verify source, decode/visual check, direct push) as explicitly as the docs lane to close the specificity gap toward 5.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "区分只审阅与授权落盘" and "按冲突、治理风险、可逆性决定 direct push、PR 和验证" — routing review-vs-land authorization into concrete delivery outcomes. Not 5 because coverage has gaps (e.g. avatar-archive specifics beyond "归档交付", what the validation entails).

4 / 5

Completeness

It clearly answers "what" (delivery classification deciding direct push / PR / validation by conflict, governance risk, reversibility) but contains no "Use when…" clause or equivalent explicit trigger guidance in the description field, capping completeness at 3 per the judging guidelines. "When" is only weakly implied by "区分只审阅与授权落盘".

3 / 5

Trigger Term Quality

It contains some relevant terms ("共创文档", "头像原图", "direct push", "PR") but leans on decision-machinery jargon ("冲突", "治理风险", "可逆性") rather than natural user phrases, and misses common variations or synonyms users would say. Not 4 because a natural-utterance keyword layer is largely absent.

3 / 5

Distinctiveness Conflict Risk

The niche (co-creation docs landing plus selected-avatar archival routing) is mostly distinct with concrete decision factors. Not 5 because separation from adjacent generic commit/PR delivery skills is not fully explicit in the description alone, leaving minor overlap risk.

4 / 5

Total

14

/

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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

zts212653/clowder-ai

Path

cat-cafe-skills/co-creation-docs/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.