CtrlK
BlogDocsLog inGet started
Tessl Logo

structured-document-creation

Create coordinated internal/external documents from reference materials with consistent formatting and cross-references

53

Quality

58%

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/structured-document-creation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is a well-structured, actionable workflow with executable code and checklists, but it carries noticeable prose filler and lacks an explicit feedback loop for the validation step.

Suggestions

Trim hand-holding prose (e.g., 'First, thoroughly read...', 'Before creating documents, plan the structure...') and remove the extraction checklist that duplicates the structured_requirements dict comments to improve conciseness.

Add an explicit feedback loop to Step 6, e.g., 'If a consistency or cross-reference check fails, return to Step 4 to fix and re-run the checklist before finalizing.'

Extend create_document_template to show filling in extracted requirements and saving both documents, so the actionability examples cover the end-to-end flow.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code, but includes filler prose ('First, thoroughly read the reference document to understand the source content', 'Before creating documents, plan the structure for each audience') and an extraction checklist that duplicates the structured_requirements dict comments.

3 / 5

Actionability

Provides concrete, executable Python (read_reference_doc, create_document_template) and a structured dict, but the examples don't fully wire extracted content into the final documents end-to-end, leaving minor gaps.

4 / 5

Workflow Clarity

A clear six-step sequence with checklists at Steps 2 and 6 and a dedicated Quality Check step; a verification step is present so the batch-operation cap does not apply, but there is no explicit validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

Well-organized into clear sections (When to Use, Steps, Example Structure, Tips, Pitfalls) with no external bundle files needed; slightly above the well-organized baseline but over 50 lines with minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

50%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 clearly states what the skill does but omits any explicit trigger guidance for when to use it, which caps its completeness. Trigger-term coverage is adequate but lacks natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when creating matching internal and external documents from a single reference source, or when the user mentions internal/external document pairs or cross-references').

Drop the filler word 'coordinated' in favor of another concrete action (e.g., 'maintain consistent terminology') to raise specificity.

Include natural synonyms or file extensions users would say (e.g., 'reference document', '.docx', 'internal vs external version') to improve trigger-term quality.

DimensionReasoningScore

Specificity

Names the domain and three concrete actions ('Create coordinated internal/external documents', 'consistent formatting', 'cross-references'), but 'coordinated' is mild filler and coverage is not comprehensive.

3 / 5

Completeness

A clear 'what' is stated but no 'when' / 'Use when...' clause exists, so per the guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Relevant domain keywords ('internal/external documents', 'reference materials', 'formatting', 'cross-references') are present but no natural user-facing trigger phrases or synonyms are included.

3 / 5

Distinctiveness Conflict Risk

The coordinated internal/external document-pair niche is somewhat specific, but it could still overlap with general document-creation skills.

3 / 5

Total

12

/

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.