CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ppt-master

AI-driven multi-format SVG content generation system. Converts source documents (PDF/DOCX/URL/Markdown) into high-quality SVG pages and exports to PPTX through multi-role collaboration. Use when user asks to "create PPT", "make presentation", "generate PPT", "make slides", or ...

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/ppt-master/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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.

Exemplary workflow sequencing — gates, checkpoints, a validation feedback loop, and failure handling — with largely executable command guidance. The main weaknesses are redundancy between the global execution rules and their Step 6 restatements, and extensive references (workflows/, templates/, docs/) that point to files missing from the bundle, including one cited as a mandatory gate.

Suggestions

Deduplicate the execution discipline: state rules 6-9 once (in the global block or Step 6) and cross-reference them from the other location instead of repeating them nearly verbatim.

Resolve the missing bundle paths: workflows/*.md, templates/* (layouts/brands/charts indexes, design_spec_reference.md, spec_lock_reference.md, icons/), and docs/ are referenced — several as mandatory reads — but absent; either ship them or remove/collapse the links.

Tighten Step 3: the mechanical no-fuzzy-matching trigger rule is explained twice in overlapping callouts; a single dispatch table plus one example callout would convey it in half the space.

DimensionReasoningScore

Conciseness

The body is mostly dense, skill-specific operational detail, but there is real duplication: Global Execution Discipline rules 6-9 are restated nearly verbatim in Step 6 ("Main-agent only", "Generation rhythm", "Per-page spec_lock re-read (Mandatory)"), and Step 3's mechanical trigger rule is stated twice in overlapping callouts. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-instances 4 anchor.

3 / 5

Actionability

Concrete, copy-paste-ready commands abound (project_manager.py init/import-sources, finalize_svg.py, svg_to_pptx.py with documented flags) plus input-to-command mapping tables, matching 'mostly executable guidance; concrete code or commands with minor gaps'. It is not a 5 because roughly a dozen instructions point to workflows/*.md files and mandatory template files (e.g. templates/design_spec_reference.md) that are absent from the actual bundle, so those steps cannot be executed as written.

4 / 5

Workflow Clarity

The 7-step serial pipeline has explicit prerequisites (🚧 GATE) before each step, checkpoints after each step, a mandatory quality-check gate with an error→fix→re-run feedback loop (svg_quality_checker.py: "Any error MUST be fixed before proceeding... re-run check"), and explicit failure paths (image rows marked Needs-Manual trigger a Step 7 pause listing missing files). This matches the top anchor: clear sequence, explicit validation, feedback loops, and checklists.

5 / 5

Progressive Disclosure

Good structure with clearly signaled, conditionally loaded references — lazy-loading image-generator.md/image-searcher.md only when needed, reading exactly one locked mode and visual-style file, and delegating script docs to scripts/README.md. It falls short of 5 because the body leans heavily on bundle paths that do not exist in the actual bundle (workflows/, templates/, docs/ — including the mandatory Step 4 gate read templates/design_spec_reference.md), which breaks navigation for those targets; this is more than a minor organization gap, keeping it below the top anchor but above the 3 anchor whose references are poorly signaled.

4 / 5

Total

16

/

20

Passed

Description

73%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 with a concrete what and explicit, natural trigger phrases, narrowly scoped to presentation generation. Its main defects are a trigger clause that is truncated mid-sentence, a few missing common synonyms (PowerPoint, .pptx, deck), and mild buzzword padding.

Suggestions

Complete the truncated trigger clause (it currently ends with "or ...") and add missing natural synonyms such as 'PowerPoint', '.pptx', 'deck', and 'build slides'.

Replace vague filler ('AI-driven', 'multi-role collaboration', 'high-quality') with concrete capabilities, e.g. the specific conversions and export types the pipeline actually performs.

Make the 'when' guidance fully self-contained so it covers the main input scenarios (file, URL, or topic-only) without relying on an open-ended list.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — "Converts source documents (PDF/DOCX/URL/Markdown) into high-quality SVG pages and exports to PPTX" — which matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because "AI-driven", "multi-role collaboration", and "high-quality" are buzzwordy padding rather than additional specific capabilities.

3 / 5

Completeness

Both what (convert source documents to SVG pages, export to PPTX) and when ("Use when user asks to...") are explicitly present with concrete trigger phrases. It is not a 5 because the when clause is truncated mid-list ("...make slides", or ..."), leaving the trigger guidance incomplete; it is above a 3 because both halves are explicitly stated.

4 / 5

Trigger Term Quality

Natural user phrases are present — "create PPT", "make presentation", "generate PPT", "make slides" — giving good keyword coverage. It falls short of the 5 anchor because common synonyms and extensions ("PowerPoint", ".pptx", "deck") are missing and the trigger list is literally cut off with a dangling "or ...".

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — presentation generation from source documents — with creation-specific triggers ("create PPT", "make slides") that would not fire for presentation-editing or general document skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

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

skill_md_line_count

SKILL.md is long (577 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 16 missing, 1 suspicious

Warning

Total

13

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/ppt-master/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.