Media and asset pipeline

Skill wfprieto/wcbs-build-kit/skills/media-and-asset-pipeline

Use when deciding whether to generate, retrieve, reference, transform, optimize, cache, license, or deliver images, video, audio, documents, icons, logos, fonts, generated media, CDN assets, or user-uploaded files.From its SKILL.md

Install

npx -y skills add wfprieto/wcbs-build-kit --skill media-and-asset-pipeline

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.7 KB, as published. Nobody here has run it

Media And Asset Pipeline

Use this skill to route asset decisions safely and efficiently.

Required Inputs

Asset purpose, audience, brand/quality requirement, and usage context.
Existing asset sources, licensing/rights status, format, size, and delivery constraints.
Whether the asset is generated, retrieved, referenced, transformed, user-uploaded, or externally hosted.

Routing Workflow

Read 40_knowledge/MEDIA_AND_ASSET_PIPELINE_GUIDANCE.md.
Choose the asset route:
- retrieve existing approved asset;
- reference external asset;
- generate new asset;
- transform/compress/resize;
- cache/CDN;
- user upload and moderation;
- fallback/placeholder.
Define rights, attribution, storage, optimization, responsive delivery, accessibility, and failure behavior.
Decide whether external API, deployment/hosting, or reporting guidance also applies.
Verify rendered output and delivery behavior when user-facing.

Decision Graph

flowchart TD
  A["Asset needed"] --> B{"Approved asset already exists?"}
  B -- "Yes" --> C["Retrieve and optimize"]
  B -- "No" --> D{"Can external asset be licensed/referenced?"}
  D -- "Yes" --> E["Reference with rights and attribution"]
  D -- "No" --> F{"Should asset be generated?"}
  F -- "Yes" --> G["Generate, review, store provenance"]
  F -- "No" --> H["Use placeholder or request source asset"]
  C --> I["Optimize, cache, add alt/fallback"]
  E --> I
  G --> I
  H --> I
  I --> J["Rendered verification before PASS"]

Guardrails

Do not use assets without rights, provenance, or user authorization.
Do not rely on a single cinematic/decorative asset for essential content.
Do not ship large media without responsive delivery or cost/performance awareness.
Do not claim visual quality without rendered review.

Good / Bad

<Bad> Grab a random image URL, place it in production, and assume it will stay available. </Bad> <Good> Use an approved asset or generated asset with provenance, store it in the project/CDN, optimize responsive variants, add alt text, and verify rendering in the target layout. </Good>

Worked Example

Scenario: Add product imagery to a landing page.

Route: retrieve approved brand images when available; generate only missing concept art.
Connected skills: deployment guidance for CDN/storage and external API guidance if generation uses a provider.
Evidence: asset source, rights/provenance, file size, responsive variants, alt text, screenshot/rendered review.
APIVR verdict: PASS only when rights, performance, accessibility, and rendered quality are Verified.

Closeout

Report asset route, provenance/rights state, optimization, fallback behavior, rendered verification, and APIVR verdict.

Workflow

Establish asset rights, transformations, formats, and output checks before publishing; retain the source and verification record for later replacement.