CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pdf-to-ppt-pack

Convert research paper PDFs into literature-report PPTX decks using a fully offline workflow (extract text/figures, map captions, summarize findings, and generate slides). Use when you need to turn a PDF into a presentation deck, especially for scientific articles with figures and tables.

Quality

69%

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/pdf-to-ppt-pack/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 body contains a genuinely useful, concrete two-command pipeline with an iterative refinement loop, but it is buried under a duplicated generic template, contradictory validation guidance, and references to scripts and directories that are absent from the bundle. Roughly two-thirds of the file is padding that competes with context for no value.

Suggestions

Delete the duplicated template half (the first 'When to Use', 'Key Features', 'Dependencies', 'Example Usage', 'Implementation Details', plus generic sections like 'Required Inputs', 'Deterministic Output Rules', and 'Completion Checklist') and keep only the specific 'PDF To PPT Pack' sections 1-5.

Fix the validation contradiction: either ship 'scripts/validate_skill.py' and remove the 'No local script validation step is required' note, or drop the 'Validation Shortcut' section entirely and keep the concrete Step 3 verify/rerun loop.

Ship the referenced bundle files ('tools/extract_pdf_figures.py', 'tools/build_cell_reports_ppt_offline.py', 'ppt/requirements.txt') or rewrite the paths to match what is actually packaged, and replace the dated '20260316/scientific-skills/Others/pdf-to-ppt-pack' example path and the irrelevant '.md' output contract with the real '.pptx' deliverable.

DimensionReasoningScore

Conciseness

The body duplicates entire sections ('When to Use', 'Key Features', 'Dependencies', 'Example Usage', 'Implementation Details' each appear twice) and pads ~60% of the file with generic template boilerplate like 'Use this skill when the request matches its documented task boundary' and 'Produce the expected output using the documented file format, schema, or narrative structure', while the actual useful core is roughly sections 1-5 of the 'PDF To PPT Pack' block. This is noticeably-to-heavily padded, fitting between anchors 1 and 2; anchor 2 fits best because a lean, concrete core does exist.

2 / 5

Actionability

The pipeline sections give concrete commands ('python "tools/extract_pdf_figures.py" --pdf ... --outdir ...', 'python "tools/build_cell_reports_ppt_offline.py" --base-dir ... --output ...') with expected output files and slide structure, but every referenced execution surface ('scripts/validate_skill.py', 'tools/*.py', 'ppt/requirements.txt') is absent from the bundle, so the guidance is concrete in shape yet not actually executable as packaged — missing key details, matching anchor 3.

3 / 5

Workflow Clarity

A three-step sequence exists with a refine-and-rerun loop (Step 3: verify titles, edit 'figure_titles_zh.txt', rerun Step 2), but the validation checkpoints are contradictory ('Validation Shortcut' says run 'python scripts/validate_skill.py --help' while 'Quick Validation' says 'No local script validation step is required for this skill') and the referenced validator script does not exist — checkpoints are present in form but broken and inconsistent, matching anchor 3.

3 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, assets/, or tools/ directories), yet the body points to 'scripts/validate_skill.py', 'tools/extract_pdf_figures.py', 'tools/build_cell_reports_ppt_offline.py', 'ppt/', 'PPTX/', and 'pdf-extract/' — navigation is dead ends. All content is inlined monolithically in one ~200-line file with the duplicated template halves, fitting anchor 2 (content that clearly belongs in separate files is inlined and references are broken).

2 / 5

Total

10

/

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 strong description: it clearly and explicitly states both the concrete multi-step capability set and the triggering scenarios, with good natural keywords and a distinct niche. The only flaws are second-person phrasing in the trigger clause and a few missing common synonyms (PowerPoint, .pptx).

DimensionReasoningScore

Specificity

The description lists multiple concrete pipeline actions ('extract text/figures, map captions, summarize findings, and generate slides'), matching the level-5 anchor, but the trigger clause 'Use when you need to turn a PDF into a presentation deck' is second person, which the judging guidelines penalize by reducing specificity by 1.

4 / 5

Completeness

Both what ('Convert research paper PDFs into literature-report PPTX decks... extract text/figures, map captions, summarize findings, and generate slides') and when ('Use when you need to turn a PDF into a presentation deck, especially for scientific articles with figures and tables') are explicitly stated with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural-keyword coverage ('PDFs', 'presentation deck', 'slides', 'figures and tables', 'research paper', 'scientific articles') but common variations like 'PowerPoint', '.pptx', and 'journal club' are missing, fitting the 'good coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The PDF-to-PPTX literature-report niche with figure/caption mapping and offline constraints is a clear niche with distinct triggers; overlap risk with generic PDF-extraction or pptx-editing skills is minimal because the scope is pinned to research papers and report decks.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/pdf-to-ppt-pack/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.