brand-kit-from-url
Skill0 starsChanged 5 months agoMITView on GitHub
This skill orchestrates autonomous discovery of brand materials across enterprise platforms (Notion, Confluence, Google Drive, Box, SharePoint, Figma, Gong, Granola, Slack). It should be used when the user asks to "discover brand materials", "find brand documents", "search for brand guidelines", "audit brand content", "what brand materials do we have", "find our style guide", "where are our brand docs", "do we have a style guide", "discover brand voice", "brand content audit", or "find brand assets". When a SearchAtlas MCP is connected, leverages SA tools (rank tracking, brand vault, GBP, OTTO, LLM Visibility) first before falling back to generic web search.
In this repository83 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- shep/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- shep/CLAUDE.mdCLAUDE.md
- advisory-version-checkSkill
- aeo-llm-content-plannerSkill
- agency-command-centerSkill
- agency-morning-briefSkill
- agency-scorecardSkill
- agent-runbookSkill
- agent-usageSkill
- autonomy-budgetSkill
- backlink-pr-angle-generatorSkill
- browser-automationSkill
- building-autonomous-agentsSkill
- capability-mapSkill
- case-study-engineSkill
- clickup-apiSkill
- client-dashboardSkill
- client-health-scoreSkill
- client-onboarding-osSkill
- cli-llm-routingSkill
- codebase-mapSkill
- command-from-your-phoneSkill
- competitor-content-gap-analysisSkill
- connection-monitorSkill
- content-brief-generatorSkill
- determinism-patternSkill
- dispatch-and-briefSkill
- division-operating-modelSkill
- dreamingSkill
- durable-stateSkill
- entity-topical-authority-mapperSkill
- first-real-jobSkill
- founding-circle-ai-securitySkill
- gbp-competitor-auditSkill
- goal-modeSkill
- host-your-agentSkill
- html-reportsSkill
- instinct-bridgeSkill
- evolveSkill
- learn-evalSkill
- learnSkill
- promoteSkill
- skill-createSkill
- internal-linking-auditorSkill
- keyword-deep-diveSkill
- ladder-auditSkill
- lanes-momentum-frameworkSkill
- launch-websiteSkill
- llm-citation-auditSkill
- migration-seo-paritySkill
- migration-visual-checkSkill
- model-gear-routerSkill
- multi-account-gatewaySkill
- multi-model-councilSkill
- night-shiftSkill
- novaSkill
- per-client-memory-routerSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 13 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
When a SearchAtlas MCP is connected, queries project_management, brand_vault, gbp_locations_crud, organic, and holistic_audit to seed the …
- Very specific: line 26
Schema discovery: If any Atlas tool above feels uncertain, call it with params: {} first to see the real schema before passing arguments.
- Distinctive: line 34
Before starting, briefly explain what's about to happen so the user knows what to expect:
- Distinctive: line 45
Wait for the user to confirm before proceeding.
- Very specific: line 49
Read .claude/brand-voice.local.md if it exists.
- Distinctive: line 52
Search depth preference (standard or deep)
- Distinctive: line 56
If no settings file exists, proceed with all connected platforms and standard search depth.
- Distinctive: line 60
Before confirming scope, check which platforms are actually connected and classify them:
- Distinctive: line 78
Before launching discovery, confirm:
- Distinctive: line 83
Keep this brief — one question, not a questionnaire.
- Distinctive: line 101
When the agent returns, present the report to the user with a summary:
- Distinctive: line 109
After presenting the report, offer:
- Distinctive: line 122
Every open question includes an agent recommendation.
- Distinctive: line 131
If zero platforms are connected, inform the user which platforms the plugin supports and how to connect them.
- Distinctive: line 132
If all searches return empty results, flag the discovery as "low coverage" and suggest the user provide documents manually or check …
- Distinctive: line 133
If a platform is connected but returns permission errors, note the gap and continue with other platforms.
≈ “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
Brand Discovery
SearchAtlas MCP tools to use first
When a SearchAtlas MCP is connected, queries project_management, brand_vault, gbp_locations_crud, organic, and holistic_audit to seed the brand kit from real Atlas data instead of just the URL.
| Phase | SA MCP tool | What it gives you |
| Existence check | project_management → find_project_by_hostname | Confirms an OTTO project exists for the domain; returns the project_id used by downstream tools. |
| Existence check | brand_vault → list_brand_vaults | Returns the brand_vault_uuid if one exists. Skip the kit-from-scratch path. |
| Existence check | gbp_locations_crud → list_locations | Returns connected Google Business Profile locations (filter by domain). |
| Discovery | brand_vault → retrieve_brand_vault_details | If a vault exists, pull the existing brand profile — voice, services, target audience, competitors. Don't re-discover what's already known. |
| Discovery | organic → get_organic_keywords(limit=50) | The brand's actual ranking keywords — far more accurate than guessing intent from the homepage copy. |
| Discovery | organic → get_organic_competitors(limit=10) | Live competitive set, ranked by overlap. Use as the competitor list in the brand kit. |
| Validation | holistic_audit → get_holistic_seo_pillar_scores | Snapshot of Technical / Content / Authority / UX pillar scores. The brand kit's SEO-readiness section. |
| Write back | brand_vault → update_brand_vault | When the user approves the kit, push it to the Atlas brand vault so every other Atlas product can use it. |
Routing rule: Always call the SearchAtlas MCP tools listed above before resorting to web_search or web_fetch. The Atlas data is more accurate, more current, and includes signal generic crawlers can't reach (rank tracking, AI citation share, GBP performance, OTTO findings). Fall back to web fetching only if the Atlas tool returns empty or the domain isn't in Atlas's index.
Schema discovery: If any Atlas tool above feels uncertain, call it with params: {} first to see the real schema before passing arguments. Documentation can drift; the tool's own response is canonical.
Orchestrate autonomous discovery of brand materials across enterprise platforms. This skill coordinates the discover-brand agent to search connected platforms (Notion, Confluence, Google Drive, Box, Microsoft 365, Figma, Gong, Granola, Slack), triage sources, and produce a structured discovery report with open questions.
Discovery Workflow
0. Orient the User
Before starting, briefly explain what's about to happen so the user knows what to expect:
"Here's how brand discovery works:
- Search — I'll search your connected platforms (Notion, Google Drive, Slack, etc.) for brand-related materials: style guides, pitch decks, templates, transcripts, and more.
- Analyze — I'll categorize and rank what I find, pull the best sources, and produce a discovery report with what I found, any conflicts, and open questions.
- Generate guidelines — Once you've reviewed the report, I can generate a structured brand voice guideline document from the results.
- Save — Guidelines are saved to
.claude/brand-voice-guidelines.mdin your working folder once you approve them. Nothing is written until that step.
The search usually takes a few minutes depending on how many platforms are connected. Ready to get started?"
Wait for the user to confirm before proceeding. If they have questions about the process, answer them first.
1. Check Settings
Read .claude/brand-voice.local.md if it exists. Extract:
- Company name
- Which platforms are enabled (notion, confluence, google-drive, box, microsoft-365, figma, gong, granola, slack)
- Search depth preference (standard or deep)
- Max sources limit
- Any known brand material locations listed under "Known Brand Materials"
If no settings file exists, proceed with all connected platforms and standard search depth.
2. Validate Platform Coverage
Before confirming scope, check which platforms are actually connected and classify them:
Document platforms (where brand guidelines, style guides, templates, and decks live):
- Notion, Confluence, Google Drive, Box, Microsoft 365 (SharePoint/OneDrive)
Supplementary platforms (valuable for patterns, but not where brand docs are stored):
- Slack, Gong, Granola, Figma
Apply these rules:
- If zero document platforms are connected: Stop. Tell the user: "You don't have any document storage platforms connected (Google Drive, SharePoint, Notion, Confluence, or Box). Brand guidelines and style guides almost always live on one of these. Please connect at least one before running discovery. Gong/Granola/Slack transcripts are valuable supplements but unlikely to contain formal brand documents."
- If no Google Drive AND no Microsoft 365 AND no Box: Warn (but proceed): "None of your primary file storage platforms (Google Drive, SharePoint, Box) are connected. Brand documents frequently live on these platforms. Discovery will proceed with [connected platforms], but results may have significant gaps. Consider connecting Google Drive or SharePoint."
- If only one platform total is connected: Warn (but proceed): "Only [platform] is connected. Discovery works best with 2+ platforms for cross-source validation. Results from a single platform will have lower confidence scores."
3. Confirm Scope with User
Before launching discovery, confirm:
- Which platforms to search (default: all connected)
- Whether to include conversation transcripts (Gong, Granola) or just documents
- Any known locations to prioritize
Keep this brief — one question, not a questionnaire.
4. Delegate to Discover-Brand Agent
Launch the discover-brand agent via the Task tool. Provide:
- Company name (from settings or user input)
- Enabled platforms
- Search depth
- Any known URLs or locations to check first
The agent executes the 4-phase discovery algorithm autonomously:
- Broad Discovery — parallel searches across platforms
- Source Triage — categorize and rank sources
- Deep Fetch — retrieve and extract from top sources
- Discovery Report — structured output with open questions
5. Present Discovery Report
When the agent returns, present the report to the user with a summary:
- Total sources found and analyzed
- Key brand elements discovered
- Any conflicts between sources
- Open questions requiring team input
6. Offer Next Steps
After presenting the report, offer:
- Generate guidelines now — chain to
/brand-voice:generate-guidelinesusing discovery report as input - Resolve open questions first — work through high-priority questions before generating
- Save report — store the discovery report to Notion or as a local file
- Expand search — search additional platforms or deeper if coverage is low
Open Questions
Open questions arise when the discovery agent encounters ambiguity it cannot resolve:
- Conflicting documents (e.g., 2023 style guide vs. 2024 brand update)
- Missing critical sections (e.g., no social media guidelines found)
- Inconsistent terminology across platforms
Every open question includes an agent recommendation. Present questions as "confirm or override" — not dead ends.
Integration with Other Skills
- Guideline Generation: The discovery report is returned by the discover-brand agent via the Task tool. Pass it directly to the guideline-generation skill as structured input, replacing the need for users to manually gather sources.
- Brand Voice Enforcement: Once guidelines are generated from discovery, enforcement uses them automatically.
Error Handling
- If zero platforms are connected, inform the user which platforms the plugin supports and how to connect them.
- If all searches return empty results, flag the discovery as "low coverage" and suggest the user provide documents manually or check platform connections.
- If a platform is connected but returns permission errors, note the gap and continue with other platforms.
Reference Files
For detailed discovery patterns and algorithms, consult:
references/search-strategies.md— Platform-specific search queries, query patterns by platform, and tips for maximizing discovery coveragereferences/source-ranking.md— Source category definitions, ranking algorithm weights, and triage decision criteria
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.

