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

59

Quality

68%

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%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 content is highly actionable with a well-sequenced, validated multi-phase workflow and copy-paste code for all three deliverables, but it is verbose with redundant summary sections and inlines material that would benefit from separate reference files.

Suggestions

Move the long per-deliverable code examples into scripts/ or references/ files and link to them from SKILL.md to cut inline token load.

Consolidate Best Practices, Anti-Patterns, and Success Criteria into one section to remove restated budget/path/verification guidance.

Drop or shorten the Quick Start template since it duplicates the Phase 1–3 examples already shown in full.

DimensionReasoningScore

Conciseness

The body is mostly useful domain-specific guidance, but the Quick Start template duplicates the per-phase code, and Best Practices, Anti-Patterns, and Success Criteria restate earlier checkpoints and budgets.

3 / 5

Actionability

Fully executable, copy-paste-ready openpyxl, matplotlib, and fpdf2 examples with ARTIFACT_PATH outputs, plus concrete verification commands and a per-error recovery matrix cover the common cases.

5 / 5

Workflow Clarity

A clearly sequenced Phase 0–4 workflow with per-phase iteration checkpoints, explicit verification steps, fallback feedback loops, and a final bundle checklist — including validation for this batch operation.

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers and tables, but the skill is a ~440-line monolithic file with long inline code examples and no references/ or scripts/ files that could hold the bulk.

3 / 5

Total

16

/

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 the three deliverable types and a distinctive iteration-budgeting mechanism, but omits any explicit "Use when..." trigger guidance and lacks synonyms/file extensions that users naturally invoke.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user needs a coordinated spreadsheet, diagram, and PDF report bundle in one task."

Add natural synonyms and file extensions (e.g. .xlsx, .png, .pdf, charts, visual layout) to broaden trigger coverage.

Keep the third-person voice but lead with the triggering scenario so "when" is as concrete as "what".

DimensionReasoningScore

Specificity

Lists several concrete actions — "Generate spreadsheet, diagram, and PDF report" plus "iteration budgeting per component" — covering the three deliverable types and a budgeting mechanism, with only minor gaps.

4 / 5

Completeness

The "what" is clear (generate a cohesive deliverable set with iteration budgeting), but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural terms "spreadsheet", "diagram", and "PDF report" are present, but common synonyms and file extensions (.xlsx, .png, .pdf) are missing and there is no trigger context to anchor them.

3 / 5

Distinctiveness Conflict Risk

The "cohesive deliverable set with iteration budgeting per component" framing carves a mostly distinct niche with only minor overlap risk against single-deliverable generation skills.

4 / 5

Total

14

/

20

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.