CtrlK
BlogDocsLog inGet started
Tessl Logo

sn-ppt-creative

Use when a prepared PPT task with a current outline.md should be generated as an image-first presentation with one 16:9 image per slide and optional PPTX packaging.

64

Quality

79%

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-creative/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 high-quality, executable skill body: lean directive prose, copy-paste commands, a well-sequenced workflow with validation and recovery, and sensible file split. Main room for improvement is trimming the 硬规则 redundancy and moving more detail into reference files.

DimensionReasoningScore

Conciseness

Dense, directive prose that assumes Claude's competence (no explanation of what PPT/PPTX is) with concrete commands; the main redundancy is the 硬规则 checklist restating rules already stated inline, which keeps it just short of fully lean.

4 / 5

Actionability

Copy-paste-ready commands with exact paths, flags, and a concrete size ('2752x1536') for resume_scan.py, sanitize_prompt.py, build_pptx.py, and the image_generate.py fallback, plus an explicit output file layout.

5 / 5

Workflow Clarity

A clearly sequenced 4-step workflow with explicit validation/recovery checkpoints (resume_scan before resuming, sanitize_prompt per page, per-page heartbeat, record-failure-and-continue, partial-state handling) and a hard-rules checklist — including feedback loops for this batch operation.

5 / 5

Progressive Disclosure

Well-organized sections with clearly signaled, one-level-deep references to bundle scripts that exist (resume_scan.py, sanitize_prompt.py, build_pptx.py); minor gaps are the two externally-referenced files (capability-policy.md, image_generate.py) outside the bundle and some inline directive lists that could live in references.

4 / 5

Total

18

/

20

Passed

Description

70%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 solid, mostly concrete description with an explicit 'Use when' trigger and clear niche scoping. It could improve by covering more of the actual workflow actions and using more natural trigger synonyms.

Suggestions

Add a couple more concrete actions (e.g., writing per-slide prompts and a style spec) so specificity reaches comprehensive coverage.

Broaden trigger terms with user-natural variants like 'PowerPoint', 'slides', 'deck', and the '.pptx' file extension.

Reframe the 'when' condition so it references user-facing situations rather than the internal 'outline.md' artifact name.

DimensionReasoningScore

Specificity

Names the domain and a couple concrete actions ('generated as an image-first presentation with one 16:9 image per slide and optional PPTX packaging'), but coverage is not comprehensive — it omits the per-page prompt, style spec, and resume steps.

3 / 5

Completeness

Both 'what' (generate an image-first 16:9 deck with optional PPTX) and 'when' (explicit 'Use when a prepared PPT task with a current outline.md...') are present; the 'when' is concrete but leans on an internal artifact name rather than purely natural trigger phrasing.

4 / 5

Trigger Term Quality

Natural user-facing terms are present ('PPT task', 'presentation', 'slide', 'PPTX packaging'); a few common variants like 'PowerPoint' and the '.pptx' extension are missing, so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The 'image-first'/'one 16:9 image per slide' niche is distinct from generic PPT skills, but the broad PPT/PPTX trigger surface keeps some overlap risk with closely related sibling skills (Standard/Dynamic/Native).

4 / 5

Total

15

/

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.