CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pptx-posters

Generate PowerPoint presentations and academic posters from paper abstracts or full paper content, with automatic layout optimization and citation formatting.

Quality

72%

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/pptx-posters/SKILL.md
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.

A well-structured, actionable skill body with a clear sequenced workflow, explicit validation and error-handling steps, and executable commands anchored by a real script. Its weaknesses are redundancy (scope-guard rules repeated across four sections plus overlapping Stress-Case/Response-Template blocks) and an undocumented, misused --style flag in one usage example.

Suggestions

Consolidate the scope-guard messaging repeated across When to Use, Scope Boundaries, Input Validation, and Error Handling into a single section, and merge Stress-Case Rules into the Response Template section.

Document the --style flag (academic/conference/lightning) in the Parameters table and fix the invalid "--style minimal" in the third usage example to a valid value such as "--style conference" or use "--template minimal".

Add an explicit validate-and-retry loop for the PDF validation step (e.g., after the parse error, accept a text/abstract fallback and re-run extraction) to strengthen the workflow's feedback structure.

DimensionReasoningScore

Conciseness

The body is mostly efficient — a compact parameter table, short usage block, no explanation of concepts Claude already knows — but scope-guard messaging is repeated across four sections: "Validate that the request is for presentation generation from existing content, not original research writing" (Workflow), "Input Validation", "Scope Boundaries" ("it does not write original research"), and "Error Handling". "Stress-Case Rules" and "Response Template" also overlap heavily (both mandate Assumptions/Risks blocks). This redundancy could be consolidated into one section, matching 'mostly efficient but could be tightened'.

3 / 5

Actionability

Guidance is largely executable: a Quick Check ("python -m py_compile scripts/main.py", "python scripts/main.py --help"), three concrete usage commands, and a complete-looking parameter table. The gaps: the third example uses "--style minimal" yet `--style` is absent from the Parameters table entirely, and the script's actual choices (academic/conference/lightning) exclude "minimal", so that example fails as written. That internal inconsistency keeps it below the fully copy-paste-ready 5.

4 / 5

Workflow Clarity

The 6-step Workflow is clearly sequenced with explicit validation checkpoints — "PDF Validation: ... If the PDF is encrypted, image-only, or corrupt, emit a specific error" and step 3's request-scope validation — plus an Error Handling section with recovery guidance ("report the failure point, summarize what still can be completed safely, and provide a manual fallback"). It is not a 5 because there is no validate-then-retry feedback loop after a failure (e.g., re-running after fixing a bad PDF) and the input-validation step is duplicated rather than chained as an explicit checkpoint.

4 / 5

Progressive Disclosure

Structure is good: clearly titled sections (Quick Check, When to Use, Workflow, Usage, Parameters, Output, Scope Boundaries, Error Handling) and a real, working reference to scripts/main.py one level deep — the referenced bundle file exists and its flags match the documented interface (except the undocumented --style). The body is ~100 lines, over the under-50-lines threshold where organization alone earns a 5, and the Stress-Case/Response-Template sections could live in a reference file, so it sits at 'good structure; most content appropriately placed'.

4 / 5

Total

15

/

20

Passed

Description

66%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, specific description with a clear 'what' and a well-defined academic niche, but it lacks any explicit 'when to use' trigger guidance and misses common natural terms like 'slides', 'deck', 'conference poster', and '.pptx'. Adding a 'Use when...' clause with those trigger phrases would move it into the top tier.

Suggestions

Append an explicit trigger clause, e.g. "Use when converting a paper, abstract, or PDF into a conference poster, slide deck, or .pptx presentation."

Add natural synonyms and extensions users would say — "slides", "slide deck", "conference poster", ".pptx" — to improve trigger term coverage.

Optionally enumerate the supported templates (academic, minimal, colorful) and output formats (poster, slides) to close the specificity gap.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Generate PowerPoint presentations and academic posters", "automatic layout optimization and citation formatting" — grounded in a specific domain ("from paper abstracts or full paper content"). It falls short of a 5 because capabilities like template selection (academic/minimal/colorful) and output formats are not enumerated, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is clear (generate presentations/posters with layout optimization and citation formatting), but there is no 'Use when...' clause or equivalent trigger guidance; the 'when' is only weakly implied by "from paper abstracts or full paper content". Per the judging guidelines, a missing 'Use when' clause caps completeness at 3, and it does not merit a 4 since no explicit trigger context exists.

3 / 5

Trigger Term Quality

Natural user phrasings like "PowerPoint presentations", "academic posters", "paper abstracts", and "citation formatting" are present. Common variations users would actually say — "slides", "slide deck", "conference poster", ".pptx" — are missing, so it matches 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym/extension coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The academic-poster-from-paper niche ("academic posters from paper abstracts or full paper content") is distinct with domain-specific triggers. There is minor overlap risk with general presentation skills for generic 'make me a PowerPoint' requests triggered by "Generate PowerPoint presentations", which keeps it below a 5 but above the broader overlap risk of a 3.

4 / 5

Total

15

/

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/pptx-posters/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.