CtrlK
BlogDocsLog inGet started
Tessl Logo

collective-participation

Use when: Collective 请求参与,或已接纳的 Work 需原处回流。Not for: 私人检索、任意投递或 owner 授权。Output: 获准上下文、具名原处回复与真实回执。

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

Quality

Content

78%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 compact, well-organized instruction skill with concrete tool references, a clear step sequence, and recovery/verification sections. It could push higher by adding exact call syntax and an explicit validate-then-proceed checkpoint.

Suggestions

Include the exact tool call signatures (arguments and expected return fields) so the guidance is copy-paste executable rather than descriptive.

Make the verification step an explicit gate before sending a reply (e.g. 'only call reply after confirming the refs match the current invocation') to strengthen the feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and direct, assumes competence, and avoids explaining concepts Claude already knows; a few framing sentences ('这里的身份、来源与权限由 Host 绑定') could be tightened slightly.

4 / 5

Actionability

Names the exact tools and the refs to pass (contextRef, returnRef, replyOperationRef) with concrete per-step guidance, but stops short of executable call syntax/parameters, leaving minor gaps.

4 / 5

Workflow Clarity

A clear numbered sequence (1–4) plus a dedicated recovery section and a 验证 section provide most checkpoints and a feedback loop, but the validation is framed as honest state-reporting rather than an explicit validate-before-proceed gate.

4 / 5

Progressive Disclosure

A short (~30-line) single-purpose skill with no bundle files and well-organized sections (workflow, recovery, verification); per the simple-skill note this is appropriately structured and navigable.

5 / 5

Total

17

/

20

Passed

Description

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

A well-structured description that explicitly covers what, when, and not-for with a distinct niche. Its main weakness is reliance on domain-specific jargon for the concrete actions, which narrows natural trigger coverage.

Suggestions

Add a couple of plain-language synonyms or phrasings alongside the Collective/Channel jargon so users outside the niche can still trigger it naturally.

Spell out the concrete actions in plainer terms (e.g. 'reply in the original channel', 'confirm delivery') rather than only abstract outputs.

DimensionReasoningScore

Specificity

Names the domain (Collective participation, Work flow-back) and several concrete outputs ('获准上下文、具名原处回复与真实回执'), but the actions lean on domain jargon rather than plainly concrete operations, so coverage is present but not comprehensive.

3 / 5

Completeness

Explicitly states what ('获准上下文、具名原处回复与真实回执'), when ('Use when: Collective 请求参与,或已接纳的 Work 需原处回流'), and a not-for boundary, fully answering both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes relevant domain keywords ('Collective 请求参与', 'Channel 参与', '回到原来源') that a user in this niche would say, but lacks common synonyms or variations and stays jargon-bound.

3 / 5

Distinctiveness Conflict Risk

Carves a clear niche (Collective/Channel participation with the cat_cafe tool family) and an explicit 'Not for' boundary, giving it distinct triggers with minimal conflict risk.

5 / 5

Total

16

/

20

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
zts212653/clowder-ai
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.