CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pdf-ppt

Create literature-report PPTX decks from PDF papers. Use when you must extract a paper’s metadata, summarize the study, interpret Results/Figures/Tables, and generate slides with 1:1 figure-to-text alignment and layout rules (triggered by requests like “PDF to PPT”, “literature report slides”, or “turn this paper into a presentation”).

Quality

81%

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

67%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 is well-structured and unusually concrete — exact coordinates, colors, naming conventions, and a deck-plan schema make the output reproducible — with clearly signaled, one-level-deep references. Its main weaknesses are redundancy across the When to Use / Key Features / Example Usage / Implementation Details sections, duplication of rules already in the reference files, and reliance on an external local PPTX skill path with no validation of the final deck.

Suggestions

Merge 'Key Features' into 'When to Use' and 'Implementation Details' to eliminate the repeated capability/output lists and cut token overhead.

Replace duplicated interpretation rules in the body with a pointer to references/figure-interpretation.md, keeping only the slide-level specifics (Summary line, label styling) inline.

Make the PPTX generation step self-contained or verify the external path exists (D:\\SKILL\\project\\PPTX\\SKILL.md is machine-specific), and add a final validation step confirming every figure/table has exactly one slide before finishing.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but capability statements are repeated across sections — "When to Use", "Key Features", "Example Usage", and "Implementation Details" each restate the extraction outputs ("Figure_1.jpg, Figure_2.jpg", legend grouping, explication.json), the 1:1 mapping rule, and the supplementary-figure exclusion. Not 4: the duplication is more than minor trimming — merging 'Key Features' into 'Implementation Details' would remove several duplicated sections. Not 2: it never pads with tutorials or library comparisons.

3 / 5

Actionability

Concrete, near-executable guidance throughout: exact box coordinates and font sizes ("Title box: (2.0825, 1.796, 9.1683, 1.2), 32pt bold"), specific hex colors, a copy-adaptable deck-plan JSON, naming conventions ("Figure_1.jpg"), and the mapping file format ("Figure_1<TAB>Chinese Title"). Not 5: the actual PPTX generation defers to an external local Windows path ("D:\\SKILL\\project\\PPTX\\SKILL.md") that may not exist, and no runnable commands are given for the parsing tools — the reader must assemble the execution themselves.

4 / 5

Workflow Clarity

The workflow is clearly sequenced ("1. Offline parse the PDF... 2. Write Chinese content... 3. Generate PPTX") with a concrete intermediate artifact (explication.json / deck plan), and the referenced offline-parsing.md includes a validation checkpoint ("Step 5: Manual sanity checks — verify each Figure_X.jpg matches the correct legend"). Not 5: the body itself never surfaces a validation or error-recovery step for the generated deck, and there is no check that every figure/table got a slide before finishing.

4 / 5

Progressive Disclosure

References are clearly signaled and one level deep: "Follow references/offline-parsing.md" and "Use references/figure-interpretation.md" both point to real bundle files, and sections are well organized (When to Use / Example Usage / Implementation Details). Not 5: the body inlines content that duplicates the reference files (the 1:1 mapping, panel-label bolding, Summary line, and supplementary-figure rules all restate figure-interpretation.md) and the ~40 lines of layout coordinates could live in their own reference.

4 / 5

Total

15

/

20

Passed

Description

88%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 states concrete capabilities across the full pipeline, explicitly signals when to use it with natural trigger phrases, and stays within a distinctive niche. The only weaknesses are missing common trigger synonyms/file extensions and slight overlap risk with generic PPT/PDF skills.

Suggestions

Add file-extension and synonym triggers such as '.pptx', '.pdf', or 'make slides from this paper' to broaden natural keyword coverage.

Tighten distinctiveness by emphasizing the literature-report/academic-paper scope in the trigger clause so generic 'PDF to PPT' conversion requests don't fire this skill instead of a general one.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Create literature-report PPTX decks from PDF papers", "extract a paper's metadata, summarize the study, interpret Results/Figures/Tables", and "generate slides with 1:1 figure-to-text alignment and layout rules" — comprehensively covering the skill's pipeline. Not 4: unlike 'minor gaps in coverage', every stage (extraction, summarization, interpretation, generation with alignment/layout constraints) is explicitly named.

5 / 5

Completeness

Both 'what' ("Create literature-report PPTX decks from PDF papers... interpret Results/Figures/Tables... generate slides with 1:1 figure-to-text alignment") and 'when' ("Use when you must... triggered by requests like 'PDF to PPT', 'literature report slides', or 'turn this paper into a presentation'") are explicit with concrete trigger phrases, matching the top anchor exactly. Not 4: the 'when' clause is not merely adequate — it enumerates concrete trigger requests.

5 / 5

Trigger Term Quality

Natural trigger phrases are included: "PDF to PPT", "literature report slides", and "turn this paper into a presentation" — good coverage with natural variations. Not 5: it misses common synonyms and file extensions users would say (e.g., '.pptx', '.pdf', 'make slides from this paper', 'paper presentation').

4 / 5

Distinctiveness Conflict Risk

The literature-report/PDF-to-PPT framing ("literature-report PPTX decks from PDF papers") carves a clear niche with distinct triggers. Not 5: a generic request like "PDF to PPT" or "convert this paper to slides" could also plausibly match a general PDF or PPTX-editing skill (the skill itself references a sibling PPTX skill), creating minor overlap risk with closely related skills.

4 / 5

Total

18

/

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/pdf-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.