Skip to the usage guide
theSVGby glincker

theSVG Skill.

Retrieve an existing brand mark or service icon in the form your project needs.

  • Brand Assets
  • SVG
  • Cloud Diagrams
Source Review · theSVGSKILL.md
Task Brand Assets Produces • Verified slug and variant choices for the requested brands. • Ready-to-use SVG URLs or raw markup suited to the destination. • A rights reminder and missing-brand fallback when appropriate. Before You Start Needs network access to the registry or CDN. React, CLI, Figma, and MCP integrations are optional surfaces rather than prerequisites for simple URL retrieval.
Editorial summary · source reviewed 2026-10-07 · not a generated example

01 What It Does

Find Brand SVGs Without Guessing Asset Paths

A registry-based brand-asset retrieval workflow with predictable SVG endpoints, variant selection, integration forms, and rights reminders.

Source-based workflowNot an execution benchmark

The Working Approach

theSVG is a retrieval Skill for named brands, frameworks, and cloud services. It uses a registry to resolve a brand name or alias to a slug, checks available variants, and returns a CDN URL, raw SVG, or an integration-specific form. It is not a tool for designing a new logo or choosing a generic menu icon.

The source distinguishes automated fetching from embedding a URL in a user-facing page, and prefers the jsDelivr endpoint for agent requests. It also keeps licensing boundaries visible: the repository's MIT license does not remove trademark restrictions on individual brand marks. Check the registry for each requested asset rather than relying on the source's advertised library size.

Expected Deliverables

  • Verified slug and variant choices for the requested brands.
  • Ready-to-use SVG URLs or raw markup suited to the destination.
  • A rights reminder and missing-brand fallback when appropriate.
See the Example Brief

From Brief to Review

  1. 01
    Resolve the Brand

    Look up the requested name in the registry using titles and aliases instead of inventing a file path.

  2. 02
    Choose an Available Variant

    Match the background and use case to the listed variants, falling back to default when a preferred version does not exist.

  3. 03
    Return the Right Form

    Provide Markdown or HTML embedding, SVG markup, or the documented React/CLI form when the project already uses that integration.

  4. 04
    Review Usage Rights

    Check brand guidelines for commercial use and preserve any asset-specific restrictions.

02 When to Use It

When to Use It

Needs network access to the registry or CDN. React, CLI, Figma, and MCP integrations are optional surfaces rather than prerequisites for simple URL retrieval.

A Good Fit

  • Integration PagesUseful for assembling real brand marks for supported integrations.
  • Cloud Architecture DiagramsCan group AWS, Azure, or GCP service icon URLs by their role in a diagram.
  • Documentation AssetsProvides consistent retrieval for framework and company logos in README files or technical guides.

Limits to Check

  • Not Generic UI IconsArrows, chevrons, and menu glyphs belong to a UI icon library rather than this brand registry.
  • Not Trademark ClearanceBrand marks remain owned by their respective holders. A code license is not permission to alter or combine them into a new identity.

Bring These Inputs

  • Exact Brand or ServiceName the product, framework, company, or cloud service.
  • Destination FormatSpecify HTML, Markdown, React, raw SVG, or an architecture diagram.
  • Background and VariantProvide light/dark context and whether a symbol or wordmark is needed.

03 Decisions That Matter

Decisions That Matter

  1. Registry Before Guesswork

    Checking available variants avoids a plausible-looking URL that returns no asset.

  2. Delivery Matches the Consumer

    An agent fetching markup and a page embedding an image can use different endpoints without changing the underlying mark.

  3. Asset Rights Stay Separate

    The source specifically distinguishes software licensing from trademark and cloud-icon conditions.

04 Try a Focused Brief

Try a Focused Brief

The example brief below has not been tested. Check the skill’s setup before using it.

Review the Setup

Review the repository's Skill installation instructions. The documented npx @thesvg/cli add command adds an icon asset; it is not a Skill installation command.

Upstream Source File
https://github.com/glincker/thesvg/blob/0ea4d44764ab73c8500382711736f97cba50afc8/skills/thesvg/SKILL.md

Needs network access to the registry or CDN. React, CLI, Figma, and MCP integrations are optional surfaces rather than prerequisites for simple URL retrieval.

Start With One Deliverable

Adapt the scope, source material and constraints in this brief before running the skill.

Example Brief
Use thesvg to retrieve registry assets for GitHub, Stripe, AWS Lambda, and AWS S3 for a light-background integration diagram. Confirm each slug and available variant, return grouped SVG URLs and descriptive alt text, and flag brand-usage restrictions. Do not recolor or distort the marks.

Inspect the Result

Check the actual output against these observable criteria.

  • Every requested slug and variant exists in the registry.
  • Assets remain readable on the requested background.
  • The delivery does not imply MIT grants rights to every trademark.

OpenDesign provides a local design workspace for coding agents. This listing does not mean the skill is bundled or that its external tools, credentials and software dependencies are included.

05 Source and License

Source and License

This page describes the pinned source revision linked below. Upstream behavior and requirements can change.

Source Owner
glincker
Repository
glincker/thesvg
License
MIT
Reviewed Snapshot
2026-10-07 · 0ea4d44764ab
Editorial Source Summary
A registry-based brand-asset retrieval workflow with predictable SVG endpoints, variant selection, integration forms, and rights reminders.

Original summary by OpenDesign, based on the linked source. Repository stars are a dated popularity signal, not skill usage or a quality score.

06 Questions Before You Start

Questions Before You Start

Does it create a custom logo?

No. It retrieves existing named-brand and cloud-service assets; a logo-design workflow is a different task.

Can it return a white logo for a dark background?

It can select a suitable listed variant, but should fall back honestly if that variant is absent.

Are all SVGs freely editable because the repository is MIT?

No. The source warns that trademarks retain their own usage rules and specifically describes AWS architecture icons as having separate no-derivatives terms.

OpenDesign

Make Room for the Next Design Iteration.

Keep your brief, source material and design work together in a local workspace. Check the skill’s own setup before adding it to your workflow.

Upstream Source File
https://github.com/glincker/thesvg/blob/0ea4d44764ab73c8500382711736f97cba50afc8/skills/thesvg/SKILL.md