CtrlK
BlogDocsLog inGet started
Tessl Logo

bedtime-story

内容创作者在需要哄睡3-12岁儿童或制作睡前音频内容时,可一键生成20个精选故事列表,或直接讲解指定寓言与成语。以0.6倍舒缓语速和亲切语气自动营造温馨哄睡氛围,轻松搞定高质量睡前陪伴。

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

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%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 exemplary instruction-only skill: fully actionable trigger-to-response mappings, a clearly sequenced conversational workflow with feedback loops, and clean progressive disclosure into two well-organized reference files. Its only real weakness is systematic repetition of tone/pacing rules across three sections.

DimensionReasoningScore

Conciseness

The body is operational rather than pedagogical, but the same tone constraints (语速0.6倍, 亲切温馨) are restated across 语气与表达规范, 讲解要求, and 注意事项>语气控制 — roughly six repetitions of identical rules that could be consolidated into one authoritative section.

3 / 5

Actionability

Guidance is fully concrete for an instruction-only skill: exact trigger phrases, exact list format (序号 + 名称 + 出处), verbatim opening/closing lines ("小朋友们好呀,今天我们一起来听《XXX》的故事~"), explicit multi-select formats ("3、7"/"3,7"), and five complete dialogue examples covering the common cases.

5 / 5

Workflow Clarity

The flow is explicitly sequenced (需求识别 → 列表生成 → 选择确认 → 讲解 → 可选分支) with an explicit checkpoint (等待用户选择) and a feedback loop (回复"不喜欢" → 立即重新生成列表); no destructive or batch operation applies, so no validation cap is triggered.

5 / 5

Progressive Disclosure

The interaction logic lives in SKILL.md while the story library and tone details are split into two clearly signaled, one-level-deep reference files (references/story-collection.md, references/tone-guide.md) that both exist and contain exactly what the 资源索引 section promises.

5 / 5

Total

18

/

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 answers both what and when with mostly concrete actions in a well-defined niche, and correctly uses third person. Its weaknesses are missing natural trigger phrasing (notably the skill's own trigger phrase "我要听故事") and a slightly padded closing sentence.

Suggestions

Add the natural trigger phrases users would actually say (e.g. "我要听故事", "讲故事", "睡前故事") to the 'when' clause, mirroring the body's 触发条件 section.

Trim marketing filler such as "轻松搞定高质量睡前陪伴" and replace it with a concrete capability (e.g. regenerating the list on "不喜欢", or multi-select sequential playback).

State explicitly when to regenerate the list versus narrate directly, so the 'when' guidance is trigger-phrase-level rather than purely scenario-level.

DimensionReasoningScore

Specificity

Lists several concrete actions with specifics ("一键生成20个精选故事列表", "直接讲解指定寓言与成语", "0.6倍舒缓语速"), but the trailing "轻松搞定高质量睡前陪伴" is marketing fluff and capabilities like list regeneration and multi-select are not covered, keeping it below the comprehensive anchor.

4 / 5

Completeness

Both 'what' (generate 20-story list, narrate fables/idioms at 0.6x pace) and 'when' ("在需要哄睡3-12岁儿童或制作睡前音频内容时") are answered, but the 'when' is scenario-based rather than concrete trigger phrases, so it is not fully explicit.

4 / 5

Trigger Term Quality

Relevant keywords are present (哄睡, 睡前, 寓言, 成语, 故事, 3-12岁), but the natural phrases a user would actually say — "我要听故事", "讲故事", "听故事", which the body itself lists as triggers — are missing from the description.

3 / 5

Distinctiveness Conflict Risk

A clear niche — bedtime fable and idiom narration for ages 3-12 with soothing pacing — makes it mostly distinct with only minor overlap risk against generic storytelling or idiom-teaching skills.

4 / 5

Total

15

/

20

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.

Validation — 16 / 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.