CtrlK
BlogDocsLog inGet started
Tessl Logo

sn-ppt-story

当前 PPT 任务已由 sn-ppt-entry 建好 DECK_DIR(task_pack.json 与 info_pack.json 已写入)后,必须由本 skill 将 query、全部用户材料与已完成 Research 编排为唯一可编辑的 outline.md 时使用。本 skill 是 entry → 出口(standard / dazzle / creative)之间的强制中间环节:不允许执行 Agent 跳过本 skill 直接依据 task_pack / info_pack 即兴编写大纲,不允许出口 skill 代写或改写大纲;前置产物缺失时停止并返回 sn-ppt-entry 补齐,不得自行补做研究。

60

Quality

73%

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/sn-ppt-story/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, actionable instruction skill with a clear sequenced workflow and explicit validation checkpoints, written efficiently without padding.

DimensionReasoningScore

Conciseness

Dense, mostly-necessary instruction that assumes Claude's competence and avoids explaining known concepts; minor redundancy between the inline constraints and the '不得做' list could be trimmed.

4 / 5

Actionability

Provides concrete, specific guidance — exact files to read, task_pack.state fields to update, a copy-ready outline.md markdown template, and a three-round self-review checklist — with only minor gaps for an instruction-only skill.

4 / 5

Workflow Clarity

The '新建' section gives a clear 6-step sequence and the '三轮 Story 自审' supplies explicit validation/checklist before writing; error-recovery detail (how to handle a failed self-review round) is implicit rather than fully spelled out.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections (输入边界, 输出和状态, 工作方法, outline.md 格式, 新建与修改, 与出口的契约, 不得做) with all content appropriately inline and easy to navigate; no bundle files are present or needed.

4 / 5

Total

16

/

20

Passed

Description

71%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 clearly defines a distinct, mandatory pipeline role and concrete behavior, but leans heavily on internal technical identifiers that users would rarely say, weakening trigger-term naturalness.

Suggestions

Lead with a natural-language 'Use when...' clause using user-facing phrases like '生成大纲' or '整理 PPT 大纲' before the pipeline-position detail.

Reduce front-loaded jargon (DECK_DIR, task_pack.json, info_pack.json) or push it after the core capability statement.

Add common synonyms a user might say (大纲、提纲、storyline、outline) directly into the description, not only the triggers list.

DimensionReasoningScore

Specificity

Names the concrete core action ('将 query、全部用户材料与已完成 Research 编排为唯一可编辑的 outline.md') plus explicit governance actions (stop and return to entry on missing prereqs, exit may not rewrite), giving several specific actions with minor coverage gaps.

4 / 5

Completeness

Explicitly states what it does (orchestrate inputs into the sole editable outline.md as a mandatory intermediate step) and when ('...时使用' after entry built DECK_DIR); the 'when' is concrete but tied to pipeline state rather than natural user phrasing.

4 / 5

Trigger Term Quality

Contains some relevant natural terms ('outline.md', '大纲', 'storyline' via triggers) but is dominated by internal jargon (DECK_DIR, task_pack.json, sn-ppt-entry, standard/dazzle/creative) and misses common user-facing synonyms.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche as the mandatory entry→exit intermediate step, explicitly distinguishing itself from sn-ppt-entry and downstream exit skills, with minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
OpenSenseNova/SenseNova-Skills
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.