logolink
Skill9 starsChanged 3 months agoMITView on GitHub
Use Context.dev Logo Link to dynamically pull in logos. Use when embedding company logos in UI (img tags, React components, CSS backgrounds, email HTML, spreadsheets), building logo walls, CRM avatars, or merchant icons — without calling the brand API from the frontend.
- Reads credentials
In this repository10 other files it gives its agents.
- connect-context-devSkill
- context-batchesSkill
- context-brandSkill
- context-crawlSkill
- context-devSkill
- context-extractSkill
- context-monitorSkill
- context-parseSkill
- context-scrapeSkill
- context-searchSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Do not: use the brand API or MCP from browser/client code for logos.
- Very specific: line 23
Use the brand API (see context-dev skill) when you need stored logos, multiple variants (light/dark/icon), or colors alongside the image.
- Very specific: line 29
Prefer an env var the codebase already uses, e.g.
- Very specific: line 46
Fallback: if no logo is found, Logo Link returns a generated SVG monogram — <img> tags never 404.
- Distinctive: line 50
Ask where logos should appear and which domain variable drives them.
- Very specific: line 51
Update only those locations.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Context.dev Logo Link
Logo Link delivers company logos via CDN. Pass a front-end-safe publicClientId and a domain; the URL returns raw image bytes (no JSON, no API key).
Do not use the brand API or MCP from browser/client code for logos. Use Logo Link instead.
When to use
- User wants logos in a UI, landing page, CRM, directory, or transaction list
- User asks to "dynamically fetch/display company logos by domain"
- High-volume logo rendering where
ctxt_secret_keys must stay server-side - User needs a simple
<img src="...">instead of parsingbrand.logos[]
Use the brand API (see context-dev skill) when you need stored logos, multiple variants (light/dark/icon), or colors alongside the image.
Step 1 — Get the Public Client ID
- Sign up at context.dev/signup if needed (free tier: 10,000 Logo Link requests/month).
- Copy the Public Client ID from context.dev/dashboard/logolink. Keys look like
brandLL_xxx. - Prefer an env var the codebase already uses, e.g.
NEXT_PUBLIC_LOGOLINK_KEYorVITE_LOGOLINK_PUBLIC_CLIENT_ID. Never put a private Context.dev API key in client code.
Step 2 — Restrict referring domains
In the Logo Link dashboard, Edit Restrictions and allow only domains that embed the image (e.g. *.example.com, localhost:3000). The publicClientId is safe in frontend code only when restrictions are set.
Step 3 — Build the URL
https://logos.context.dev/?publicClientId=MY_PUBLIC_CLIENT_ID&domain=TARGET_DOMAIN- Replace
MY_PUBLIC_CLIENT_IDwith the user's ID (or env var). - Replace
TARGET_DOMAINwith the company domain variable (bare domain, e.g.stripe.com). - Optionally add
theme=lightfor a dark logo on a light UI ortheme=darkfor a light logo on a dark UI. - GET and HEAD only. Response is the image file;
Content-Typeisimage/png,image/svg+xml, etc. - 24-hour
Cache-Controlon the response. Browser/CDN caching is expected. - Fallback: if no logo is found, Logo Link returns a generated SVG monogram —
<img>tags never 404.
Step 4 — Implement in the codebase
- Ask where logos should appear and which domain variable drives them.
- Update only those locations; preserve existing fallback and
onErrorpatterns. - Examples:
<img
src="https://logos.context.dev/?publicClientId=brandLL_xxx&domain=stripe.com"
alt="Stripe logo"
/>function CompanyLogo({ domain }) {
const publicClientId = process.env.NEXT_PUBLIC_LOGOLINK_KEY;
return (
<img
src={`https://logos.context.dev/?publicClientId=${publicClientId}&domain=${domain}`}
alt={`${domain} logo`}
onError={(e) => {
e.target.style.display = "none";
}}
/>
);
}Usage rules
- Allowed: embed via URL in
<img>, CSSbackground-image, email HTML,=IMAGE()in Sheets/Excel; normal browser caching. - Not allowed: download and re-host logos in your own storage or persist image files outside cache headers. For that, use brand APIs server-side.
Logo Link requests are billed separately from API credits (no rate limit; one charge per unique logo per client per 24h).
Links
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

