CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ppt

Create and export PPTX decks using the local HTML/JS PPT framework in `D:\SKILL\project\ppt`. Use this when you need to generate slides from a topic/outline, edit slide content via `projects/*.js`, preview as HTML, or export a `.pptx` without relying on an existing template.

Quality

70%

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 ./scientific-skills/Other/ppt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 authoring half of the body is genuinely strong — a complete executable example, exact commands, and concrete layout/palette rules. The skill is dragged down by a large block of generic templated filler sections, contradictory validation guidance, and an inline-only structure with no clear navigation to deeper component documentation.

Suggestions

Delete or drastically trim the generic boilerplate sections (Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Deterministic Output Rules, Completion Checklist) — they restate what Claude already knows and consume roughly half the token budget.

Resolve the contradiction between 'Validation Shortcut' (run validate_skill.py first) and 'Quick Validation' ('No local script validation step is required'), and either make the script perform a real check or remove it.

Document the schemas/usage of the remaining component types (comparison, timeline, stats) — ideally in a references/ file linked from the body — so the full component API is not left implicit.

DimensionReasoningScore

Conciseness

The core sections (When to Use through Implementation Details) are efficient, but roughly half the body is generic templated boilerplate — 'Required Inputs', 'Recommended Workflow', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', 'Deterministic Output Rules', 'Completion Checklist' — with lines like 'Return a structured deliverable that is directly usable without reformatting' and 'Validate required inputs before execution' that add nothing Claude doesn't already know. This matches anchor 2 ('several unnecessary explanations or padded sections'); not anchor 1 because no basic concepts (what PPT/HTML is) are explained, and not anchor 3 because the padding is extensive rather than incidental.

2 / 5

Actionability

Provides a complete, copy-paste-ready project file example ('const SLIDES = [...]'), exact executable commands ('python build_html.py demo-20260227', 'python convert_to_pptx.py demo-20260227'), and a concrete output location. Falls short of anchor 5 because component types 'comparison', 'timeline', and 'stats' are named without any schema or usage example, and the purpose of 'python scripts/validate_skill.py --help' is unclear since the script only prints a fixed 'ok' message with '--check'.

4 / 5

Workflow Clarity

The core sequence (create project file → 'python build_html.py' preview → 'python convert_to_pptx.py' export → output dir) is clearly numbered with concrete commands, but the validation checkpoints are contradictory and hollow: the 'Validation Shortcut' section says to run validate_skill.py first, while 'Quick Validation' states 'No local script validation step is required for this skill', and the script itself validates nothing. This fits anchor 3 ('sequence present but checkpoints missing or implicit'); not anchor 4 because the contradiction and no-op validation are real checkpoint gaps, not minor ones.

3 / 5

Progressive Disclosure

The body is well-sectioned with headers, and the one bundle reference ('scripts/validate_skill.py') is a real, clearly signaled file at the stated path. However, everything lives inline in SKILL.md with no well-signaled reference structure, the partial component API (only quote/valueCards/ending shown) has no pointer to fuller documentation, and the generic boilerplate sections dilute the organization. Matches anchor 3 ('some structure but could be better organized'); not anchor 4 because a substantial fraction of the inline content is misplaced filler rather than a minor gap.

3 / 5

Total

12

/

20

Passed

Description

78%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 strong description that explicitly states both capabilities and trigger conditions with concrete, deck-workflow-specific actions. Its weaknesses are the second-person trigger phrasing (penalized under the rubric's voice rule) and missing natural synonyms like 'PowerPoint' and 'presentation' that users commonly say.

Suggestions

Rephrase the trigger clause in third person, e.g. 'Use when the user asks to generate slides, edit `projects/*.js`, or export a `.pptx`' to avoid the second-person voice penalty.

Add natural synonyms such as 'PowerPoint', 'presentation', and 'deck' alongside 'PPTX decks' and '.pptx' to broaden trigger-term coverage.

Consider naming the layout/component capability (e.g., 'standardize slide layouts with predefined components') so the 'what' covers the styling features documented in the body.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Create and export PPTX decks', 'generate slides from a topic/outline, edit slide content via `projects/*.js`, preview as HTML, or export a `.pptx`' — which would fit anchor 4, but the trigger clause 'Use this when you need to...' is second person, and the rubric guideline mandates reducing the specificity score by 1 for second-person voice. Not anchor 2: the actions are concrete and domain-specific, not generic.

3 / 5

Completeness

Explicitly answers both: what — 'Create and export PPTX decks using the local HTML/JS PPT framework' — and when — 'Use this when you need to generate slides from a topic/outline, edit slide content via `projects/*.js`, preview as HTML, or export a `.pptx` without relying on an existing template'. This matches the anchor-5 pattern of concrete 'what' plus explicit 'Use when...' trigger phrases; anchor 4 would require the 'when' to be weaker or less specific.

5 / 5

Trigger Term Quality

Good keyword coverage: 'PPTX decks', 'slides', 'topic/outline', 'HTML' preview, '.pptx' file extension, and 'template'. Missing common natural synonyms such as 'PowerPoint', 'presentation', and 'deck', which keeps it below anchor 5; clearly above anchor 3 because coverage is broad rather than just 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The niche is mostly distinct — code-driven deck authoring via a specific 'local HTML/JS PPT framework in `D:\SKILL\project\ppt`' with a no-template export path. Minor overlap risk remains with generic presentation/PPTX skills because terms like 'PowerPoint' or 'presentation' are absent, so a user request phrased that way could match multiple skills. Not anchor 5 for that residual overlap; not anchor 3 because the framework-specific framing is clearly distinguishing.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/ppt/SKILL.md

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.