theSVG Brand Icon Library
6,500+ brand SVG icons and cloud architecture icons fetched via predictable CDN URLs — no web scraping or path guessing required.
The skill is read-only URL/manifest lookup: no credentials, no arbitrary code execution, no file writes, transparent data flow; SECURITY.md describes SVG payload scanning, LICENSE is MIT, and trademark/CC BY-ND risks are proactively flagged. Deductions: icon content depends on external CDNs (jsDelivr/thesvg.org) with no integrity check or fallback defined in the skill itself; execution evidence for the claimed security-scan script is not present in the provided files; publisher identity is unverified, leaving attribution incomplete.
URL patterns, manifest endpoints, and slug/variant rules are internally consistent with explicit fallback guidance (default variant); the repo includes fairly complete CLI error-handling tests (network errors, HTTP 500/404, bad JSON, unexpected shape). Deductions: those tests cover the CLI package, not the skill's own key paths (jsDelivr URLs, icons. manifest); CDN paths are pinned to the mutable @main branch, introducing drift risk; static review cannot confirm reachability, and variant coverage is 'up to 7', not guaranteed.
Trigger conditions are precise (brand/logo/cloud-service icons) with a clear non-fit boundary excluding generic UI icons and pointing to Lucide/Heroicons; delivery formats are tabulated by user context. Deductions: no Chinese-language support and no discussion of mainland-China reachability — jsDelivr has historically been unreliable there and the alternate thesvg.org endpoint is also overseas, so core function depends entirely on services of uncertain mainland accessibility; self-hosting is mentioned in README but not integrated into the skill.
MIT license is explicit, with SECURITY.md, legal/TRADEMARK/LEGAL references, changesets-based versioning, dual-endpoint architecture, caching advice, and documented icon submission/removal processes. Deductions: the skill claims 6,500+ icons while README says 7,400+, an inconsistency; SKILL.md has no version or update date; CDN references pin @main rather than a release tag; maintenance responsibility (glincker/thesvg.org) is stated but unverified.
The goal is clear (return directly usable CDN URLs or SVG markup), with example URLs, registry-matching strategy, and light/dark variant selection rules that lower usage cost, providing real marginal value over manually hunting brand assets. Deductions: static review cannot verify that the URLs actually return correct SVGs; key promises (6,500+ scale, 'default always present') lack committed reproduction evidence; the icon-count discrepancy between README and skill weakens scale claims.
Evidence types include: in-skill checkable URL patterns, repo CLI tests for network error handling, CI workflows (actionlint, gated auto-merge), and SECURITY.md scanning claims. Deductions: tests and CI do not cover the skill's own key paths (reachability/correctness of icon URLs and icons.); the referenced security-audit script is not in evidence; claims like icon totals and 'no rate limits' lack independent cross-source corroboration; no execution or reproduction was performed.
- All example URLs pin the mutable @main branch; content can change at any time — prefer a fixed release tag or self-hosting for production use.
- Reachability of both jsDelivr and thesvg.org from mainland China is unstable; the skill's core function may be unusable without a mirror or self-hosted fallback.
- Trademark risk rests with the user: the skill flags CC BY-ND (no derivatives) and brand usage guidelines — verify each brand's policy before commercial use and do not recolor/distort marks despite the skill's recoloring-adjacent advice.
- Icon count in the skill (6,500+) contradicts the README (7,400+); totals and 'no rate limits' claims are independently unverified, and the referenced security-audit script was not included in the evidence.
- This is a static, non-executed review; actual availability and output correctness require independent reproduction.
What does this skill do, and when should you use it?
theSVG is an open-source SVG icon library with 4,629 brand logos, 739 AWS architecture icons, 626 Azure service icons, and 214 Google Cloud icons — over 12,300 variants including color, mono, light, dark, and wordmark. The skill teaches an agent to fetch icons through one consistent URL pattern on jsDelivr or thesvg.org, using a JSON registry to resolve brand names and aliases into slugs. The codebase is MIT-licensed, but individual brand marks remain trademarks of their owners, and AWS icons are distributed under CC BY-ND 2.0 with no modifications allowed. It fits developers and designers who need real brand logos in docs, READMEs, architecture diagrams, or frontend projects.
Looks up a JSON icon registry (slug, title, aliases, categories, hex, variants) and matches user queries against titles and aliases; assembles standard URLs for variants like default, mono, light, dark, and wordmark; delivers icons as Markdown, HTML, React/Vue/Svelte components, or raw SVG markup depending on context; groups AWS/Azure/GCP icon URLs by service tier (compute/storage/network) for architecture diagrams; and points users to thesvg.org/submit for missing brands.
- A developer writing a README or docs who needs the correct logo for GitHub, Tailwind, or another named brand
- A cloud architect drawing AWS/Azure/GCP diagrams in Excalidraw, Mermaid, or Figma who needs official service icons
- A frontend developer adding brand icons to an integrations page (Slack, Notion, Stripe) with typed packages like @thesvg/react
- An agent or automation batch-generating documents with brand icons, preferring jsDelivr to absorb bursty automated traffic
- Someone styling icons on a dark background who needs the light or mono variant
What are this skill's strengths and limitations?
- 6,500+ icons and 12,300+ variants, including official AWS/Azure/GCP cloud sets
- Fully predictable URL pattern with no auth and no rate limits — agents can construct URLs directly
- A complete JSON registry supports caching once and searching client-side
- MIT-licensed codebase with typed, tree-shakeable npm packages across React/Vue/Svelte/CLI/MCP
- The skill file bakes in practical guidance on variant selection, light/dark backgrounds, and trademark compliance
- Individual brand marks remain trademarked; commercial use requires reviewing each brand's guidelines, and AWS icons must be distributed unmodified
- Not every icon ships all 7 variants; light/dark variants may be missing
- The source provides no evidence of a test suite, contributor count, or performance benchmarks
- Covers named brands and services only — generic UI icons require Lucide, Heroicons, or similar
How do you install this skill?
Install the skill with: npx skills add glincker/thesvg. The skill file lives at skills/thesvg/SKILL.md in the repository. No local dependencies are required beyond HTTP access to jsDelivr CDN or thesvg.org.
How do you use this skill?
Trigger the agent with requests like "Give me the GitHub logo as SVG", "I need AWS Lambda and S3 architecture icons", or "What's the URL for the dark variant of the OpenAI mark". The agent fetches the registry (https://cdn.jsdelivr.net/gh/glincker/thesvg@main/src/data/icons.), matches the query against titles/aliases, and returns the CDN URL or raw SVG for the right variant. Ecosystem tools also work: npx @thesvg/cli add github, the @thesvg/mcp-server MCP server, the Figma plugin, or the VS Code extension.
How does this skill compare with similar options?
The source notes that most icon libraries focus on UI icons (the skill itself recommends Lucide and Heroicons for those), while brand logos are scattered across press kits and random GitHub repos — theSVG positions itself as the single source for brand and cloud service icons.