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

52

Quality

59%

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

60%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 skill is highly actionable with executable pandoc/ReportLab commands and a clear backend-selection workflow, but it is markedly verbose — the same code patterns and examples are restated multiple times, inflating the token budget without adding guidance.

Suggestions

Dedupe the pandoc/ReportLab code blocks: keep one canonical example in Common Patterns and reference it from Quick Start, Full Workflow, and the Examples instead of restating each block.

Trim the three full worked Examples down to one pandoc-first and one ReportLab-first, removing Example 3's near-duplicate fallback code.

Consolidate the two Troubleshooting sections (one at the end duplicates 'Missing reportlab: Install via pip install reportlab') into a single block.

DimensionReasoningScore

Conciseness

The ~650-line body is noticeably verbose: it repeats the same pandoc/ReportLab code blocks across Quick Start, Full Workflow, three Examples, Common Patterns, and Troubleshooting, padding the context with redundant variants of identical steps.

2 / 5

Actionability

It provides concrete, copy-paste-ready pandoc commands and complete ReportLab Python snippets covering the common cases, with only minor gaps (e.g., the sanitization script's sed quoting is not validated end-to-end).

4 / 5

Workflow Clarity

Steps are clearly sequenced with a numbered Quick-Start and Full Workflow, plus a verification step (ls -lh outputs) and a decision flowchart; the cap-triggering destructive/batch validation is present, though the fallback retry loop is only loosely described ('If Step 2 returns error...').

4 / 5

Progressive Disclosure

Structure is well-organized with clear section headers and a decision flowchart, and no bundle files are referenced (all content inline); the inlining of the large repeated example/code material is the minor gap keeping it below 5.

4 / 5

Total

14

/

20

Passed

Description

58%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.

The description concretely names its backends and fallback mechanism, but lacks an explicit "Use when..." trigger clause and the natural user-facing terms (formats, file extensions) that would drive activation.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers such as 'Use when generating .docx, .pdf, or .html from Markdown'.

Include user-facing terms and file extensions (e.g., 'Markdown to Word/PDF', '.docx', '.pdf') rather than only backend names.

State the concrete output action ('generates documents') upfront before describing the backend mechanism.

DimensionReasoningScore

Specificity

"direct pandoc/ReportLab execution" and "optional shell_agent fallback" name concrete backends and a specific fallback mechanism, but the description omits the concrete output actions (generate .docx/.pdf/.html) — closer to anchor 4 than 5.

4 / 5

Completeness

There is a clear "what" (document generation with two backends) but no explicit "Use when..." trigger clause; the "when" is only weakly implied by "for complex scenarios", which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

It surfaces technical keywords (pandoc, ReportLab, shell_agent) but lacks the natural phrases a user would actually say ("generate a document", "convert markdown to PDF", "create a .docx"); missing common synonyms and file extensions.

3 / 5

Distinctiveness Conflict Risk

The dual-backend framing (pandoc/ReportLab + shell_agent fallback) carves a fairly distinct niche from generic document skills, with only minor overlap risk against other document-gen variants it references.

4 / 5

Total

14

/

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.

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.