CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

learning-companion

围绕具体材料陪人读懂、听懂、讨论与共同探索。 Use when: 一起读论文/访谈/文章/书中章节、重读旧材料、准备共读的阅读稿或口播稿、听完后继续挑战与发散。 Not for: 单次事实问答、只要摘要或翻译、产品操作引导、对外文章、替用户启动训练或能力进化项目。 Output: 按需交付带来源的阅读稿/口播稿与共同讨论;需要保存时在约定位置更新材料,并同步读者正在消费的版本。

Quality

82%

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

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.

A dense, well-structured behavioral skill with concrete attribution phrasings, file conventions, and explicit validation/revision loops; as an instruction-only skill its guidance is actionable without code. The main defects are a broken internal reference (refs/examples-and-evidence.md does not exist in the bundle) and mild redundancy between the anti-pattern table and earlier sections.

Suggestions

Create refs/examples-and-evidence.md (or correct the cited path to match the actual bundle layout) so both "见 refs/examples-and-evidence.md" citations resolve to a real file.

Add a brief numbered phase overview near the top (接住 → 读材料 → 成稿 → 讨论 → 检查 → 修订) to make the workflow sequence explicit rather than implied by heading order.

Merge overlapping rows of the "实战中的错误与改法" table into the sections they repeat (e.g., fold the "讨论中已经改口" row into 修订与续读) to reduce redundancy.

DimensionReasoningScore

Conciseness

Dense, rule-based prose with no padding and no explanation of concepts Claude already knows — every section carries household-specific guidance (attribution rules, PK conditions, quadrant taxonomy). It is not a 5 because there is mild redundancy: the "实战中的错误与改法" table restates points already made (e.g., the 概念课-substituting-重读 failure and the "讨论中改口 ≠ 修好" case appear in earlier sections).

4 / 5

Actionability

Concrete, near copy-ready guidance throughout: attribution phrasings to put directly into script text ("这里作者认为……"/"下面我换个例子……"/"这个联系是我的猜想……"), specific formatting rules ("正文不朗读 URL、引用编号、代码路径"), file conventions ("Clowder AI 通常放在 docs/study/,阅读稿和 -listen.md 互相指向"), and a two-mode review protocol. It is not a 5 because some directives remain directional without operational detail (e.g., "先弄清对方连接的是哪条因果", "沿可用材料继续").

4 / 5

Workflow Clarity

Sections follow a coherent phase order — 接住这一次共读 → 先读材料 → 按阅读方式成稿 → 陪着讨论 → 四象限探索 → 怎么检查 → 修订与续读 — with validation checkpoints (the 检查 section's review-cat protocol and the revision loop "核实其是否仍旧,不把'文字已改'说成所有版本已更新"). It is not a 5 because sequencing is implied by heading order rather than stated, and branching across purposes is acknowledged ("几种目的可以并存,随讨论调整") rather than prescribed; it is above 3 because error-recovery loops for consumed text and derived audio are explicit.

4 / 5

Progressive Disclosure

Section structure is well organized and the intent to delegate examples is right ("具体原件和一个成稿小样见 refs/examples-and-evidence.md"), but the bundle contains no refs/ directory at all — the referenced examples-and-evidence.md file does not exist, so both citations ([实战与示例](refs/examples-and-evidence.md) and the 下一步 link) are broken. Scored against the actual bundle structure, this fits 'some structure but references not functional / could be better organized' rather than the good-structure anchor.

3 / 5

Total

15

/

20

Passed

Description

87%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 strong description with an explicit what/when/not-for/output structure and natural, dedicated trigger phrases that clearly carve out its niche. The only shortcoming is that the lead capability verbs are somewhat abstract, keeping specificity just below maximal.

DimensionReasoningScore

Specificity

Lists several concrete actions and deliverables — "陪人读懂、听懂、讨论与共同探索", "按需交付带来源的阅读稿/口播稿与共同讨论", "需要保存时在约定位置更新材料,并同步读者正在消费的版本" — which matches the 'several specific actions; minor gaps' anchor. It is not a 5 because the lead verbs (读懂/听懂/讨论/探索) are abstract and the description omits parts of the actual workflow (e.g., the PK and four-quadrant exploration the body performs).

4 / 5

Completeness

Explicitly answers both questions: 'what' via the opening capability line plus the Output clause ("按需交付带来源的阅读稿/口播稿与共同讨论…"), and 'when' via a concrete "Use when:" clause listing trigger scenarios. It also adds "Not for:" exclusions (单次事实问答、只要摘要或翻译…), matching the anchor for clearly and explicitly answering both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-phrase coverage: the Use-when clause ("一起读论文/访谈/文章/书中章节、重读旧材料、准备共读的阅读稿或口播稿") plus a dedicated triggers list ("陪我学习", "一起读", "一起重读", "学习口播稿", "听完一起讨论") are phrases a user would plausibly say. A few common variants are missing (e.g., "陪我读", "读后讨论", "帮我读懂这篇"), so it falls just short of the comprehensive/synonym anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche — companion reading of specific source material producing sourced reading/listen scripts — with distinctive triggers ("学习口播稿", "一起重读") that few other skills would claim. The explicit "Not for:" boundary (摘要、翻译、产品操作引导、对外文章、启动训练项目) sharply reduces overlap with generic summarization, discussion, or coaching skills, fitting the minimal-conflict-risk anchor.

5 / 5

Total

18

/

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: 2 missing, 6 suspicious

Warning

Total

14

/

16

Passed

Repository

zts212653/clowder-ai

Path

cat-cafe-skills/learning-companion/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.