CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

export-download-debugging

Diagnose and fix browser, preview, or Electron export/download failures, especially image export issues involving Save As, Blob/Data URLs, the File System Access API, createWritable failures, and 0 KB files.

64

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, well-structured debugging skill: lean prose, a clear diagnose-then-fix-then-validate sequence, and concrete commands. The main gap is the absence of an executable code snippet for the primary save-channel fallback and an explicit error-recovery loop in the fix order.

Suggestions

Add a short copy-paste code example for the primary fallback path (e.g. an <a download> with a verified non-empty blob/data URL) to lift actionability to fully executable.

Make the feedback loop explicit in the Fix order, e.g. 'if the payload is still 0 bytes, log the byte length and error name and re-check the capture step before routing to a fallback channel'.

Include the exact byte-length assertion to 'Prove the export payload has non-zero bytes' (e.g. check blob.size > 0 or the data URL length) so the core rule is directly checkable.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — no padding, no explanation of concepts Claude already knows (blob URLs, Electron, CSP are referenced without tutorials), and every section carries actionable weight ('Separate capture from save. Prove the export payload has non-zero bytes...').

5 / 5

Actionability

Concrete API names, specific checks, and real commands ('pnpm --filter @open-design/web typecheck', 'pnpm guard') make the guidance mostly executable, but the fix steps are prose directives without a copy-paste code example for the key fallback path.

4 / 5

Workflow Clarity

Clear ordered sequence (Evidence → Fix order → Validation) with explicit validation checkpoints and commands, but no explicit validate→fix→retry feedback loop within the fix steps — anchor 4 fits better than 5.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external bundle files needed, and content is cleanly organized into well-labeled sections (Core rule, Evidence, Fix order, Validation) — meets the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

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

A specific, well-scoped description with a clear niche and strong concrete failure-mode keywords. Its main weakness is the missing explicit 'Use when...' trigger clause, which caps completeness, plus some reliance on technical jargon over natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when an image export or download produces a 0 KB, empty, or missing file, or when the user mentions export/download failures.'

Include more natural user phrasings and file extensions among the trigger terms (e.g. '.png', 'download failed', 'empty file') to complement the API-level jargon.

Add one or two more action verbs beyond 'Diagnose and fix' (e.g. 'validate payload bytes, route fallback save channels') to strengthen capability coverage.

DimensionReasoningScore

Specificity

Names the domain ('browser, preview, or Electron export/download failures') and concrete failure modes ('Save As, Blob/Data URLs, the File System Access API, createWritable failures, and 0 KB files'), but only two action verbs ('Diagnose and fix') — minor gaps versus comprehensive action coverage.

4 / 5

Completeness

Has a clear 'what' (diagnose and fix export/download failures) but no 'Use when...' clause or equivalent explicit trigger guidance in the description text, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes natural user phrases like 'export/download failures', 'image export issues', and '0 KB files', but mixes in technical jargon ('File System Access API', 'createWritable') and misses common variations like '.png', 'download failed', or 'empty file'.

4 / 5

Distinctiveness Conflict Risk

The Electron/createWritable/blob-URL/0-KB-file niche is highly specific with distinct technical triggers; minimal overlap risk with other skills.

5 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

nexu-io/open-design

Path

skills/export-download-debugging/SKILL.md

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.