structured-document-creation

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

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

62%

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

A well-structured, clearly sequenced workflow with executable code and thorough checklists, weakened by incomplete extraction logic and a monolithic layout that mixes inline material which could be split into references.

Suggestions

Replace the empty structured_requirements dict skeleton in Step 2 with executable extraction logic or concrete examples showing how timelines, roles, and steps are actually pulled from the reference.

Collapse the overlapping Step 3 audience table and document-planning template into a single concise planning section to reduce redundancy.

Move the example structure diagram, tips, and pitfalls into a referenced file (e.g., EXAMPLES.md) so the main SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	It avoids explaining concepts Claude already knows, but at ~190 lines it carries redundancy (the Step 3 audience table overlaps the planning template, and the intro echoes the 'When to Use' list) that could be tightened.	2 / 3
Actionability	It provides real executable python-docx snippets (read_reference_doc, create_document_template) and checklists, but the core extraction step is only an empty dict skeleton plus a manual checklist, leaving the actual work underspecified.	2 / 3
Workflow Clarity	The six numbered steps form a clear sequence, and Step 6 supplies explicit validation/quality-check checkpoints with checklists for consistency, audience appropriateness, and cross-references.	3 / 3
Progressive Disclosure	The body is well-organized into sections but is a single ~190-line monolithic file with no bundle files or one-level-deep references, and the >50-line simple-skill exemption does not apply.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 states a clear purpose in third person and a reasonably distinct niche, but it lacks an explicit 'Use when' trigger and relies on one main action with modifiers rather than enumerating multiple concrete capabilities.

Suggestions

Add a 'Use when...' clause listing natural trigger situations, e.g., 'Use when creating paired internal and external documents from one source, or when maintaining consistency across audience-specific versions.'

Surface more concrete actions users would name (e.g., 'extract timelines, roles, and policies' and 'generate matched internal and external versions') to lift specificity and trigger coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('internal/external documents', 'reference materials') and qualities ('consistent formatting', 'cross-references'), but these are modifiers on a single create action rather than the multiple distinct concrete actions the top anchor requires.	2 / 3
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Terms like 'internal/external documents' and 'reference materials' are plausible user phrasing, but 'cross-references' and 'consistent formatting' lean technical and common variations are missing.	2 / 3
Distinctiveness Conflict Risk	The coordinated internal/external-from-one-source niche is somewhat distinctive, but the generic word 'documents' and absence of explicit triggers leave room for overlap with other document skills.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/structured-document-creation/SKILL.md
Commit: c5a9c4b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.