CtrlK
BlogDocsLog inGet started
Tessl Logo

integrated-report-bundle

Generate spreadsheet, diagram, and PDF report as a cohesive deliverable set with iteration budgeting per component

57

Quality

65%

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/pdf-checklist-workflow-enhanced-a53b26/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 a clear, well-validated multi-phase workflow, but it is verbose and monolithic — redundant template/practice sections and large inline code blocks that could be offloaded to reference files hold back conciseness and progressive disclosure.

Suggestions

Remove the redundant "Quick Start All Three Deliverables" template and consolidate overlapping "Best Practices", "Anti-Patterns", and "Success Criteria" sections to tighten the body.

Move the full per-deliverable code examples into reference files (e.g., references/spreadsheet.py, references/diagram.py, references/pdf.py) and link to them from a concise overview to improve progressive disclosure.

Trim the stray "*** End Files" marker and any repeated ARTIFACT_PATH boilerplate to recover token budget.

DimensionReasoningScore

Conciseness

The body is mostly efficient actionable guidance, but it is padded with redundant sections (e.g., the "Quick Start All Three" template duplicates the per-phase examples, and "Best Practices", "Anti-Patterns", and "Success Criteria" overlap), so it could be tightened rather than rating a lean 3.

2 / 3

Actionability

It provides complete, executable code for openpyxl, matplotlib, and fpdf2 plus specific verification commands and a concrete error-handling matrix, matching the copy-paste-ready anchor.

3 / 3

Workflow Clarity

Phases 0-4 are clearly sequenced with explicit verification checkpoints, iteration checkpoints ("After 8 iterations... move to... regardless"), fallback feedback loops, and a final bundle checklist, satisfying the explicit-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets are absent) and the ~430-line file is monolithic with large inline code blocks and templates that could be split into reference files; section organization is decent but content that should be separate stays inline.

2 / 3

Total

10

/

12

Passed

Description

52%

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 is specific about the deliverable bundle and budgeting concept but omits any "Use when..." trigger guidance, which caps both completeness and trigger-term quality at 2. Adding an explicit usage-trigger clause would lift the weakest dimensions.

Suggestions

Add an explicit "Use when..." clause naming natural trigger phrases (e.g., "Use when the user asks for a combined spreadsheet, diagram, and PDF report package").

Vary the action verbs beyond "Generate" (e.g., "Build spreadsheets, render diagrams, assemble PDF reports") to strengthen specificity.

Include common user synonyms such as "xlsx", "chart", or "report bundle" to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Quotes "Generate spreadsheet, diagram, and PDF report" and "iteration budgeting per component" name a concrete domain and outputs, but the action vocabulary is essentially a single verb ("Generate") applied to three objects, which is less comprehensive than the score-3 anchor's multiple distinct verbs.

2 / 3

Completeness

It clearly states what the skill does (generate the three-deliverable bundle with budgeting) but provides no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Terms like "spreadsheet", "diagram", and "PDF report" are natural, but "cohesive deliverable set" and "iteration budgeting per component" lean technical, and common user variations (e.g. "xlsx", "chart", "report bundle") are missing.

2 / 3

Distinctiveness Conflict Risk

The three-deliverable bundle with iteration budgeting is a recognizable niche, but it could still overlap with general report-generation or spreadsheet/diagram skills since no trigger disambiguates it.

2 / 3

Total

8

/

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