CtrlK
BlogDocsLog inGet started
Tessl Logo

sn-ppt-dazzle

需要把演示 / 幻灯片 / PPT / slides 做成单文件 HTML 动态 deck(动效、跨页过渡、键盘翻页、1280×720)时使用。本 skill 非入口:使用前必须先确认 sn-ppt-entry 与 sn-ppt-story 两个前置 skill 可用,依次执行 entry(建 DECK_DIR / task_pack.json)→ story(生成 outline.md)完成后才可开始;前置缺失或未完成时停止并回报,严禁绕过(如改用生图+手写 HTML 等方式)。

68

Quality

84%

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

81%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 highly actionable, well-sequenced workflow with concrete code, parameters, and validation loops; its main weakness is verbosity from restating the same design-discipline guidance across multiple sections rather than a token-efficiency problem of over-explaining known concepts.

Suggestions

Consolidate the repeated anti-slop / anti-套路 / fancy≠3D guidance into a single canonical section (e.g. §0 or §7) and cross-reference it instead of restating it in §3, §5, and §7 — this is the largest conciseness win.

Consider moving the §8 particle-parameter table and engineering pitfall catalog into a reference file (e.g. references/engineering-pitfalls.md) so SKILL.md reads more like an overview, lifting progressive_disclosure toward 5.

Tighten the §5 self-check by grouping the 12 hard-fault items and the layout-hygiene items into terse checklists with shared rationale, rather than multi-sentence prose per item.

DimensionReasoningScore

Conciseness

Packed with non-obvious specifics, but the anti-slop / anti-套路 / 招牌兑现 guidance is restated across §0, §3, §5, and §7 — noticeable redundancy that could be consolidated.

3 / 5

Actionability

Provides copy-paste render commands, an exact Three.js r128 CDN URL, a concrete particle-parameter table, and an explicit slideInits[N] registration pattern with a full CSS/HTML architecture contract.

5 / 5

Workflow Clarity

Six stages are explicitly sequenced with validation checkpoints (smoke in §3, per-page render→look in §4, render --all + contact_sheet in §5), a 3-round edit→render→look feedback loop, and a 12-item self-check list.

5 / 5

Progressive Disclosure

style-families.md and fancy-cookbook.md are pushed one level deep with a §9 reference index and inline "when to read" hints, but SKILL.md itself is a ~40KB monolith rather than a lean overview pointing to detail.

4 / 5

Total

17

/

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 specific, well-triggered description that clearly states both what the skill produces and when to use it, with strong distinctiveness via named prerequisites and an anti-bypass guard. The only gap is coverage of adjacent file-format terms.

DimensionReasoningScore

Specificity

Lists concrete deliverable features ("动效、跨页过渡、键盘翻页、1280×720" single-file HTML deck) rather than vague abstractions; not 5 because it characterizes the output instead of enumerating a comprehensive action list.

4 / 5

Completeness

Explicitly answers both what (single-file HTML dynamic deck with named features) and when ("…时使用" with concrete triggers), reinforced by prerequisite and non-entry guard detail.

5 / 5

Trigger Term Quality

Covers natural synonyms users say ("演示 / 幻灯片 / PPT / slides") plus "动态 HTML"; held below 5 because adjacent terms like .pptx, deck, or Keynote are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche with named prerequisite skills (sn-ppt-entry, sn-ppt-story) and an explicit bypass guard, making wrong-skill triggering unlikely.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

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.