Skill Detail

Inspect and retrieve brand and cloud service SVG assets with theSVG

Resolve named brands and cloud services through theSVG’s manifest, choose available light or dark variants, and return exact SVG assets for docs and diagrams.

Image & Creative AutomationMulti-Framework
Image & Creative Automation Multi-Framework Published
⭐ 3k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill retrieve-brand-cloud-service-svg-assets-thesvg Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
HTTP-capable agent; theSVG manifest and SVG CDN; requested brands/services, background and output form
Install & setup
No package installation is needed for this HTTP route. Read the pinned upstream skills/thesvg/SKILL.md, fetch the manifest, match slugs and variants, then retrieve SVGs. Use revision 8d1934ccc6329da24d2db703eaaf57487ed4c31d in place of main in the CDN paths for reproducible retrieval, keeping manifest and assets on that revision. Retain applicable brand guidelines. Optional npm, CLI and MCP integrations are outside this route.
Author
glincker
Publisher
Individual
Last updated
Nov 13, 2026
Quick brief

Use this skill when an operator asks an agent to assemble named brand marks for an integrations page, README or cloud architecture diagram. Input is a list of brands or cloud services, the intended background and the desired output form. Return verified slugs, available variants and actual SVG markup or URLs, grouped by service tier when appropriate.

How it works

What this skill actually does

The upstream skill tells agents to fetch the registry once per session at https://cdn.jsdelivr.net/gh/glincker/thesvg@main/src/data/icons.json. Match requests against titles and aliases, then resolve assets under public/icons/{slug}/{variant}.svg on the same CDN. Inspect manifest variants and successful SVG responses before embedding. If a requested appearance is unavailable, use default; report missing brands rather than substituting unrelated marks. For reproducibility, use one reviewed repository revision for both the manifest and assets.

Preserve supplied usage-guideline references. Brand marks remain their owners’ trademarks; the code license does not grant unrestricted brand usage. Upstream identifies AWS architecture icons as requiring unmodified distribution. The workflow boundary is retrieval and assembly of existing named-brand and cloud-service assets. Exclude generic navigation glyph selection, logo redesign and image generation. Multi-Framework is defensible because the actual upstream skill uses public HTTP resources that multiple agent runtimes can invoke; MCP, CLI and package integrations are optional.