CtrlK
BlogDocsLog inGet started
Tessl Logo

document-gen-dual-backend

Document generation with direct pandoc/ReportLab execution (lightweight default) and optional shell_agent fallback for complex scenarios

55

Quality

62%

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 ./benchmarks/gdpval/skills/document-gen-fallback-enhanced-enhanced-9f3b1f/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable with complete, executable pandoc and ReportLab examples and good backend-selection guidance, but it suffers from notable duplication and verbosity and keeps everything in one monolithic file. Workflow verification is present but shallow and the fallback logic is hand-waved with a placeholder.

Suggestions

De-duplicate the body — the Pandoc-First example, the sanitized-source block, and the 'Missing reportlab' entry each appear twice, and trailing stub sections repeat earlier headings; remove the redundant copies.

Replace the placeholder '[If Step 2 returns error...]' in the fallback example with a concrete error-detection check (e.g. inspecting run_shell exit status) and strengthen verification to validate output validity rather than only file existence.

Move stable reference material (the Unicode replacement table, common pandoc commands, the sanitization script) into files under references/ and link to them, keeping SKILL.md as a lean overview with a quick-start path.

DimensionReasoningScore

Conciseness

The body is mostly task-relevant but noticeably padded and duplicated — the Pandoc-First example, sanitized-source block, and 'Missing reportlab' entry each recur, and trailing stub sections ('Example 1', 'Example 2', a second Troubleshooting) repeat earlier content, so it could be tightened substantially.

2 / 3

Actionability

Provides concrete, copy-paste-ready code: complete ReportLab scripts, specific pandoc commands, a reusable sanitization shell script, and an installation block — fully executable rather than pseudocode.

3 / 3

Workflow Clarity

Steps are clearly numbered with a decision flowchart and a verify step, but verification is shallow ('ls -lh' confirms existence, not validity) and the fallback path relies on a placeholder '[If Step 2 returns error...]' rather than a concrete error-detection feedback loop.

2 / 3

Progressive Disclosure

Well-organized into labeled sections, but it is a single monolithic ~300+ line file with no bundle files in references/scripts/assets; reference material (Unicode table, common commands, sanitization script) that could live in separate files is kept inline.

2 / 3

Total

9

/

12

Passed

Description

60%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description concretely names the dual-backend capability and fallback behavior but is missing an explicit 'Use when...' trigger clause and common trigger terms like PDF/DOCX. It also risks overlapping with related document-generation skills. Adding a usage trigger and user-facing keywords would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause listing user-facing triggers, e.g. 'Use when generating PDFs, DOCX, or HTML from Markdown, or when converting documents with Unicode/special characters.'

Include natural trigger terms users would say — 'PDF', 'DOCX', 'HTML', 'Markdown to PDF', 'convert documents' — alongside 'document generation'.

Sharpen distinctiveness from sibling skills by foregrounding the dual-backend/fallback decision as the unique niche rather than generic 'document generation'.

DimensionReasoningScore

Specificity

Names concrete actions across two backends — 'direct pandoc/ReportLab execution' and 'optional shell_agent fallback' — listing multiple specific capabilities rather than vague language.

3 / 3

Completeness

Clearly states what the skill does (pandoc/ReportLab execution with fallback) but lacks any explicit 'Use when...' trigger, so the when is only implied.

2 / 3

Trigger Term Quality

Includes the natural term 'document generation' but omits common user-facing variations like 'PDF', 'DOCX', 'convert Markdown', or 'generate documents', so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The dual-backend framing is fairly specific, but it overlaps with sibling skills like 'document-gen-unicode-safe' and 'document-gen-fallback' and could trigger for generic document-generation requests.

2 / 3

Total

9

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (649 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
HKUDS/OpenSpace
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.