CtrlK
BlogDocsLog inGet started
Tessl Logo

reports-pdfs-and-slide-automation

Lay out and export data-rich reports and documents. Use when the user needs report structure, figure packaging, PDFs, PowerPoint or Google Slides automation, or programmatic insertion of visualizations, UML-like diagrams, or architecture diagrams into documents.

66

Quality

78%

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 ./plugins/build-web-data-visualization/skills/reports-pdfs-and-slide-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized instruction skill that assumes competence and uses real, one-level-deep bundle references effectively. It loses points on actionability (no executable code) and workflow clarity (validation checkpoints implicit for the build/render steps), and some prose could be tighter.

Suggestions

Tighten the dense run-on sentences in the Overview and Figure Packaging Rule 3 into shorter bullets to improve conciseness.

Add at least one minimal executable snippet (e.g. a Playwright/Puppeteer HTML-to-PDF render call or a pptxgenjs slide-asset placement) to lift actionability.

Insert an explicit validate-then-proceed checkpoint in the PDF/slide build steps (e.g. 'render, verify the output opens and figures placed, then export') to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence (no explanation of what a PDF is or how libraries work), but the Overview prose paragraphs and Figure Packaging Rule 3 are dense run-on sentences that could be tightened. Not score 3 because those passages pad rather than earn every token; not score 1 because there is no conceptual over-explanation.

2 / 3

Actionability

Concrete tools are named (pptxgenjs, pdf-lib, PDFKit, jsPDF, Playwright, Puppeteer, Google Slides API) and export formats are specified (SVG/PNG/PDF), but there is no executable code and guidance stays at the direction level. Not score 3 because nothing is copy-paste ready; not score 1 because specific libraries and formats make it more than abstract description.

2 / 3

Workflow Clarity

Figure Packaging Rules form a numbered sequence and Rule 3 includes an explicit approval feedback loop ('repeat the concise bullet review until the user agrees') with editorial QA, but there is no strict validate→fix→retry checkpoint for the document/PDF generation steps. Not score 3 because validation checkpoints are implicit rather than enforced for the build/render operations; not score 1 because sequencing and one feedback loop are present.

2 / 3

Progressive Disclosure

SKILL.md is a clear overview that points to one-level-deep references, and all four referenced bundle files (./references/report-structure-and-figure-packaging.md, pdf-generation-paths.md, powerpoint-and-google-slides.md, document-embedding-and-regeneration.md) exist on disk and are signaled in the References section. Not score 2 because the split is clean and navigation is explicit.

3 / 3

Total

9

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that names concrete actions, includes an explicit 'Use when' trigger with natural keywords, and carves out a distinct niche around document/deck composition. It hits all four dimensions at the top of the scale.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Lay out and export data-rich reports and documents' plus 'programmatic insertion of visualizations, UML-like diagrams, or architecture diagrams into documents' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what ('Lay out and export data-rich reports and documents') and when ('Use when the user needs report structure, figure packaging, PDFs...'). Not score 2 because the 'Use when...' trigger clause is present and explicit.

3 / 3

Trigger Term Quality

Natural user terms are well covered: 'report structure, figure packaging, PDFs, PowerPoint or Google Slides automation'. Not score 2 because it includes the common variations (PDFs, PowerPoint, Google Slides) users would actually say.

3 / 3

Distinctiveness Conflict Risk

Clear niche — composing figures/charts/diagrams into reports, PDFs, and decks — with distinct triggers unlikely to fire for unrelated skills. Uses third-person imperative voice, so no voice penalty applies.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.