CtrlK
BlogDocsLog inGet started
Tessl Logo

bedtime-story

为3-12岁儿童提供温馨亲切的睡前寓言故事和成语典故讲解。支持用户唤醒后提供故事列表选择,或直接讲解指定故事/成语。讲解时保持亲切温馨的语气、0.6倍正常语速、通俗易懂的表达,为小朋友营造舒适的睡前氛围。

62

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 ./skills/bedtime-story/bedtime-story/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and highly actionable with concrete phrases, formats, and a clear sequenced workflow backed by two real reference files. Its only weakness is redundant restatement of tone/completeness constraints across the steps and notes sections.

Suggestions

Deduplicate the repeated constraints (语速0.6倍, '全文讲解,不精炼,不删减') by stating them once and referencing them from 操作步骤 and 注意事项.

Consider trimming the five examples to the two most representative to reduce token overhead.

DimensionReasoningScore

Conciseness

It is mostly efficient and does not explain concepts Claude already knows, but it repeats constraints (语速0.6倍, '全文讲解,不精炼,不删减', 亲切温馨) across 操作步骤 and 注意事项, so it is not fully lean.

2 / 3

Actionability

Provides concrete, copy-ready templates: exact opening/closing phrases, list format (序号+故事名称+出处), multi-select handling ('3、7'/'3,7'), per-input processing logic, and 5 worked examples — fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

The standard flow is clearly sequenced (唤醒识别→列表生成→选择确认→故事讲解→成语讲解) with explicit input-handling branches and a regenerate feedback loop ('不喜欢'→new list); no destructive operations require validation.

3 / 3

Progressive Disclosure

The body is an overview with a 资源索引 section signaling two one-level-deep references (story-collection.md, tone-guide.md), both verified to exist as real bundle files, matching the anchor for well-signaled single-level references.

3 / 3

Total

11

/

12

Passed

Description

60%

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 specific about capabilities and tone constraints but lacks an explicit 'Use when...' trigger clause, which caps both completeness and trigger-term quality. Adding natural user phrases such as '我要听故事' would lift it toward the top level.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user says 我要听故事 or asks for a fable/idiom (成语典故) at bedtime.'

Surface natural trigger variations ('讲个故事', '听成语') directly in the description rather than only in the body.

Clarify the activation context ('when the skill is invoked') instead of the vague '用户唤醒后'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('提供故事列表选择', '直接讲解指定故事/成语', '保持亲切温馨的语气', '0.6倍正常语速'), matching the anchor for naming several specific actions rather than vague language.

3 / 3

Completeness

Clearly answers 'what' (提供寓言故事和成语典故讲解) but 'when' is only implied via '支持用户唤醒后'; per guidelines a missing explicit 'Use when...' trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant keywords (故事, 成语, 睡前) but lacks explicit natural trigger phrases a user would say (e.g. '我要听故事'), which appear only in the body; missing common variations keeps it at 2 rather than 3.

2 / 3

Distinctiveness Conflict Risk

The niche is specific (3-12岁, 睡前, 寓言+成语) but the bare 故事/成语 triggers could overlap with general storytelling or idiom-explanation skills, so it is not a clear 3.

2 / 3

Total

9

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
anbeime/skill
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.