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.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted skill description that clearly defines its scope around media pipeline planning and optimization. It excels in all dimensions by listing concrete actions, providing extensive natural trigger terms including problem-based triggers, explicitly answering both what and when, and carving out a distinct niche. The inclusion of user pain points ('images are slow, broken, or scattered across systems') is a particularly effective touch for matching real user queries.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: designing image storage and delivery, choosing formats (WebP, AVIF), setting up responsive images, picking a video host, organizing a brand asset library, and auditing a slow image pipeline. | 3 / 3 |
Completeness | Clearly answers both 'what' (plan and run a media pipeline for images, video, and downloadable assets with specific sub-tasks) and 'when' (explicit 'Use this skill when...' clause plus a 'Triggers on' list and problem-based triggers). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say, including format names (WebP, AVIF), domain terms (image pipeline, asset library, DAM, image CDN, responsive images, video hosting), and problem-based triggers (images are slow, broken, or scattered across systems). | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around media/image pipeline management with highly specific triggers like DAM, AVIF, image CDN, and asset workflow that are unlikely to conflict with general web development or content management skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, well-structured skill that provides genuinely actionable guidance for media pipeline planning. Its strengths are the clear 4-stage framework, concrete HTML patterns, and well-sequenced 8-step workflow with monitoring checkpoints. Its main weakness is verbosity — at ~300 lines, it includes explanatory content and exhaustive lists that could be trimmed or moved to reference files, consuming more context window than necessary for a skill Claude could partially reason about independently.
Suggestions
Trim the 'Failure patterns' section to the 4-5 most non-obvious patterns; Claude can infer common mistakes like missing alt text or random naming.
Move the format reference table and detailed Stage descriptions into a separate reference file to reduce the main skill's token footprint.
Provide the referenced `references/responsive-image-patterns.md` bundle file so the progressive disclosure actually functions as designed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is well-organized but verbose in places. The 'When to use' and 'When NOT to use' lists, the extensive 'Required inputs' section, and the detailed 'Failure patterns' section contain information Claude could largely infer. The format reference table and HTML examples earn their place, but sections like Stage 1's source list and management decisions could be tightened significantly. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready HTML patterns for responsive images and format negotiation, a clear format reference table, specific pipeline patterns (A/B/C) with tool names, enforceable standards (CI checks, CMS requirements), and specific targets (under 500KB per page). The workflow steps are concrete with named tools (Lighthouse, WebPageTest) and specific deliverables. | 3 / 3 |
Workflow Clarity | The 8-step workflow is clearly sequenced from inventory through documentation, with explicit audit/monitoring steps (Steps 2 and 7) serving as validation checkpoints. The 4-stage framework (Source → Process → Deliver → Manage) provides a clear mental model. Step 7 includes ongoing monitoring for broken images and performance regression, creating a feedback loop. | 3 / 3 |
Progressive Disclosure | The skill references one external file (`references/responsive-image-patterns.md`) which is well-signaled, but no bundle files were provided to support it. The main document is quite long (~300 lines) and some sections like the failure patterns list and the detailed Stage descriptions could be split into reference files. The format reference table and output format section add length that could be externalized. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- rampstackco/claude-skills
- Commit
8e70d03
- 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.