brand-style-extractor
Skill1 starsChanged 7 months agoNo licenceView on GitHub
Extract a comprehensive brand style guide from any company website URL and generate a structured .md file covering brand voice, typography, colors, logo usage, imagery, and design patterns. Use this skill whenever the user provides a company URL and asks to extract, document, or reverse-engineer their brand guidelines, style guide, visual identity, brand voice, or design system. Also trigger when the user says things like "pull brand info from this site", "what's their brand style?", "generate a brand guide for [company]", "extract the design language from [URL]", "document their visual identity", or "create a style guide from their website". Trigger even for partial requests like "what fonts do they use?" or "what's their brand color?" since the full extraction produces a complete, reusable document.
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- account-brief-generatorSkill
- ai-fluency-assessmentSkill
- anyreach-deck-pptxSkill
- anyreach-financial-reportSkill
- anyreach-funnel-analysisSkill
- anyreach-web-designSkill
- bpo-partner-pitch-deckSkill
- bpo-roi-briefSkill
- bpo-roi-internal-briefingSkill
- bpo-roi-modelSkill
- callsSkill
- company-deep-researchSkill
- competitor-deep-diveSkill
- consumer-intelligence-xlsxSkill
- consumer-intel-reportSkill
- cx-intel-report-pdfSkill
- cx-intel-report-xlsxSkill
- demo-bot-usage-reportSkill
- deploy-intelSkill
- discovery-dashboardSkill
- discovery-to-proposalSkill
- gtm-audit-appSkill
- gtm-audit-pdfSkill
- gtm-stack-auditSkill
- legal-reviewSkill
- leverage-analysisSkill
- maturity-assessmentSkill
- meeting-recap-emailSkill
- narrative-deckSkill
- portfolio-cx-briefSkill
- product-site-frameworkSkill
- proposal-sow-generatorSkill
- remotion-best-practicesSkill
- reviews-vs-live-callsSkill
- richard-thought-leadershipSkill
- shadcn-deckSkill
- stakeholder-intelSkill
- status-deckSkill
- visual-briefSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.

