Agent skill · Content & Marketing

media-asset-management

Plan and run a media pipeline for images, video, and downloadable assets. Use this skill when designing image storage and delivery, choosing formats (WebP, AVIF), setting up responsive images, picking a video host, organizing a brand asset library, or auditing a slow image pipeline. Triggers on image pipeline, asset library, DAM, image optimization, WebP, AVIF, responsive images, video hosting, image CDN, asset workflow, media management. Also triggers when images are slow, broken, or scattered across systems.

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill media-asset-management --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 11 KB
Bundled scripts: none
Path: skills/media-asset-management/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Media Asset Management Design how images, video, and downloadable files get stored, processed, organized, and served. Stack-agnostic. The principles apply whether you're running a custom pipeline or using a hosted service. --- ## When to use - Designing or redesigning the image and media pipeline - Choosing a media CDN or image service - Setting up responsive image delivery - Planning a digital asset management (DAM) system - Auditing media performance issues - Picking video hosting and embedding strategy - Setting up workflows for designers and writers to upload assets - Migrating media from one platform to another ## When NOT to use - Performance optimization beyond media (use `performance-optimization`) - Brand identity or photography direction (use `brand-identity`, `art-direction`) - Content production strategy (use `content-strategy`) - Single-image optimization (covered in `performance-optimization`) --- ## Required inputs - Current media inventory: where assets live, in what formats - Volume: how many assets, how much storage, how much traffic - Sources: who creates and uploads media (designers, writers, automated tools) - Platforms: where media is consumed (web, email, a

What's inside
Steps it walks through
  1. When to use
  2. When NOT to use
  3. Required inputs
  4. The framework: 4 stages
  5. Stage 1: Source
  6. Stage 2: Process
  7. Stage 3: Deliver
  8. Stage 4: Manage
  9. Format reference
  10. Workflow
  11. Step 1: Inventory
  12. Step 2: Audit performance
  13. Step 3: Pick the pipeline
  14. Step 4: Define standards
Ships with 1 file
  • references/responsive-image-patterns.md
More from claude-skills
All skills →
About this skill
What does the media-asset-management skill do?

Plan and run a media pipeline for images, video, and downloadable assets. Use this skill when designing image storage and delivery, choosing formats (WebP, AVIF), setting up responsive images, picking a video host, organizing a brand asset library, or auditing a slow image pipeline. Triggers on image pipeline, asset library, DAM, image optimization, WebP, AVIF, responsive images, video hosting, image CDN, asset workflow, media management. Also triggers when images are slow, broken, or scattered across systems.

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill media-asset-management --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going