asset-pipeline-verifier

Identifies broken asset references and missing files in web projects' src/public directories.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/DaFum/neurotoxic-game --skill asset-pipeline-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asset-pipeline-verifier
Source: https://github.com/DaFum/neurotoxic-game/tree/main/.agents/skills/asset-pipeline-verifier
Command: npx skills add https://github.com/DaFum/neurotoxic-game --skill asset-pipeline-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Verify asset paths, glob patterns, and references across a project to detect broken links or missing files in the asset pipeline. Use when assets fail to load, paths are undefined, or MIME mismatches are suspected.

Core Features & Use Cases

  • Asset-path validation: scans for import.meta.glob and new URL(import.meta.url) references to locate dynamic asset loads.
  • Cross-reference checks: compares asset usage against files in src/assets and static assets in public/ to surface missing or mismatched references.
  • Reporting & workflow integration: outputs a suspect list that can feed CI checks or manual audits to prevent broken assets in production.

Quick Start

Run the asset-scan.sh script to identify broken asset references and missing files.

Frequently Asked Questions about asset-pipeline-verifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify asset paths and find missing files in my Vite web project?

To verify asset paths, scan your web project for broken references by analyzing import.meta.glob usage, new URL(import.meta.url) patterns, and public path references against files in src/assets and public directories.

How do I detect broken static asset references before deploying to production?

Detect broken static asset references by running a scan during development or CI workflows to compare asset usage against public and src directories, generating a structured report of suspects to prevent broken assets in production.

Why do my dynamically imported assets fail to load or return undefined paths?

Dynamically imported assets fail to load when import.meta.glob or new URL(import.meta.url) patterns reference missing files; cross-reference checks compare asset usage against src/assets and public directories to surface mismatched references.

Can I integrate asset-path validation into my CI workflow to catch broken links?

Yes, you can integrate asset-path validation into CI workflows by running the scan to output a suspect list, feeding CI checks to prevent broken assets from reaching production.

What is the best way to audit import.meta.glob usage for missing assets at scale?

The best way to audit import.meta.glob usage at scale is to run a cross-reference check that analyzes dynamic asset loads and compares them against static assets in public and src directories to surface missing references.