CtrlK
BlogDocsLog inGet started
Tessl Logo

report-to-pdf

Narrow conversion skill. Invoke only when the user explicitly asks to convert an existing Data Analytics report, dashboard, or inline chart export into a PDF artifact.

67

Quality

80%

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 ./packages/opencode/src/skill/builtin/.bundle/data-analytics/workflows/build-report/report-to-pdf/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A thorough, executable single-purpose skill with a strong sequenced workflow, validation checkpoints, and a repair loop. The main weakness is redundancy between the workflow steps and the later Standards/Verification Guidance sections.

Suggestions

Collapse the 'Standards' and 'Verification Guidance' sections into the workflow steps they duplicate, or explicitly frame them as a quick-reference recap, to remove the repetition that holds conciseness at 2.

Add one short example invocation for pdfinfo/pdftotext/pdftoppm (e.g. `pdfinfo report.pdf`, `pdftoppm -png -r 80 report.pdf page`) to make the verification step fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is operational rather than explanatory of known concepts, but the 'Standards' and 'Verification Guidance' sections largely restate rules already embedded in the workflow steps (omit app-only controls, omit internal metadata, verify with pdfinfo/pdftotext/pdftoppm), creating noticeable redundancy.

2 / 3

Actionability

It provides a copy-paste-ready Chrome headless print-to-PDF command with concrete flags and names specific verification tools (pdfinfo, pdftotext, pdftoppm); the tool-agnostic fallback is an explicitly justified flexibility rather than vague direction.

3 / 3

Workflow Clarity

A clearly sequenced 6-step workflow with explicit validation in step 4 and a repair feedback loop in step 5 (verify -> if blank/clipped -> fix source -> regenerate), plus blocker-stop criteria for unfixable cases.

3 / 3

Progressive Disclosure

No bundle files are present or needed; the single SKILL.md is well-organized into Workflow, Standards, and Verification Guidance sections with no nested references, matching the simple-skill allowance for a 3 at well-organized sections.

3 / 3

Total

11

/

12

Passed

Description

75%

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 well-scoped, third-person description with an explicit 'when' trigger and low conflict risk. It is held back from the top by listing only one action and by slightly technical trigger phrasing.

Suggestions

Add one or two more concrete actions (e.g., 'export a dashboard to PDF, print a chart to PDF') to lift specificity to the multi-action anchor.

Soften jargon such as 'inline chart export' and 'PDF artifact' toward phrasings a user would naturally say, e.g. 'export to PDF' or just 'PDF'.

DimensionReasoningScore

Specificity

It names the domain ('Data Analytics report, dashboard, or inline chart export') and a single concrete action ('convert ... into a PDF artifact'), but does not list multiple distinct actions, so it stops at the 'some actions, not comprehensive' anchor.

2 / 3

Completeness

It states what (convert an existing report/dashboard/chart export to PDF) and gives an explicit when ('Invoke only when the user explicitly asks to convert ...'), satisfying both halves with a clear trigger clause.

3 / 3

Trigger Term Quality

Natural terms like 'convert ... report, dashboard ... into a PDF' are present, but 'inline chart export' and 'PDF artifact' lean technical and common variations such as plain 'PDF' or 'export to PDF' are under-covered.

2 / 3

Distinctiveness Conflict Risk

The 'Narrow conversion skill' framing plus the Data-Analytics-report-only trigger carves a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

10

/

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
XiaomiMiMo/MiMo-Code
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.