Source profileQuality 75/100

nexu-io/open-design/skills/export-download-debugging/SKILL.md

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.

Source repository stars
82,073
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Use this when an export or download appears to run but produces an empty, missing, or unusable file. It is tuned for browser previews, iframe capture, and Electron shells.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/nexu-io/open-design --skill "skills/export-download-debugging"
    Safe inspection promptEditorial

    Inspect the Agent Skill "export-download-debugging" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/skills/export-download-debugging/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Core rule

      Separate capture from save. Prove the export payload has non-zero bytes before debugging the destination path. A 0 KB file often means the native picker or host created the target file, then the write failed or was blocked.

      Separate capture from save. Prove the export payload has non-zero bytes before debugging the destination path. A 0 KB file often means the native picker or host created the target file, then the write failed or was bloc…
    2. 02

      Evidence

      Record the payload type, MIME type, byte length, object URL or data URL path,

      Record the payload type, MIME type, byte length, object URL or data URL path,Check browser console output and app logs around showSaveFilePicker,In Electron, inspect the will-download path: filename, MIME, file extension,
    3. 03

      Fix order

      1. Prepare and validate the export payload first; disable Save until bytes are available. 2. Prefer the simplest stable save channel for the host. If showSaveFilePicker().createWritable() fails, is sandboxed, or creates empty files, route to or Electron's download manager instea…

      Prepare and validate the export payload first; disable Save until bytes arePrefer the simplest stable save channel for the host. IfAvoid opening a native picker before the payload is ready. This prevents the
    4. 04

      Validation

      Add or update tests for non-empty payload preparation, fallback save behavior,

      Add or update tests for non-empty payload preparation, fallback save behavior,Run focused export tests, then pnpm --filter @open-design/web typecheck.If Electron download handling changed, also run

    Permission review

    Static risk signals and limitations

    Network access

    medium · line 18

    The documentation includes network, browsing, or remote request actions.

    `createWritable`, `<a download>`, `URL.createObjectURL`, and URL revocation.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score75/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars82,073SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    nexu-io/open-design
    Skill path
    skills/export-download-debugging/SKILL.md
    Commit
    89d6d4ef21baf80f871595abdf6f7de6e941dd44
    License
    Apache-2.0
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    Export Download Debugging

    Use this when an export or download appears to run but produces an empty, missing, or unusable file. It is tuned for browser previews, iframe capture, and Electron shells.

    Core rule

    Separate capture from save. Prove the export payload has non-zero bytes before debugging the destination path. A 0 KB file often means the native picker or host created the target file, then the write failed or was blocked.

    Evidence

    • Record the payload type, MIME type, byte length, object URL or data URL path, and thrown error name/message.
    • Check browser console output and app logs around showSaveFilePicker, createWritable, <a download>, URL.createObjectURL, and URL revocation.
    • In Electron, inspect the will-download path: filename, MIME, file extension, save dialog filters, cancellation, and final file size.
    • Confirm the actual downloaded file size on disk and whether it opens in a normal image viewer.

    Fix order

    1. Prepare and validate the export payload first; disable Save until bytes are available.
    2. Prefer the simplest stable save channel for the host. If showSaveFilePicker().createWritable() fails, is sandboxed, or creates empty files, route to <a download> or Electron's download manager instead.
    3. Avoid opening a native picker before the payload is ready. This prevents the host from creating an empty destination file on later write failure.
    4. For PNG fallback, prefer a verified non-empty data URL when blob URLs, revocation timing, CSP, or iframe sandboxing are suspicious.
    5. In Electron, add explicit Save As filters for exported image extensions (.png, .jpg, .jpeg, .webp) so users can choose a real image target.
    6. Keep the UI restrained: format selection, filename/path hint, clear pending and error states, and one primary save action.

    Validation

    • Add or update tests for non-empty payload preparation, fallback save behavior, file extension/MIME mapping, and UI disabled/error states.
    • Run focused export tests, then pnpm --filter @open-design/web typecheck.
    • If Electron download handling changed, also run pnpm --filter @open-design/desktop typecheck.
    • Before landing, run pnpm guard, inspect the staged diff for unrelated files, generated artifacts, and accidental secrets, then use the repository's PR quality-gate workflow if the fix is being prepared for review.

    Alternatives

    Compare before choosing