discover-brand▌
anthropics/knowledge-work-plugins · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
Brand Discovery
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
How to use discover-brand on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add discover-brand
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches discover-brand from GitHub repository anthropics/knowledge-work-plugins and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate discover-brand. Access the skill through slash commands (e.g., /discover-brand) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★65 reviews- ★★★★★Diego Dixit· Dec 28, 2024
discover-brand fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ganesh Mohane· Dec 24, 2024
discover-brand fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Min Garcia· Dec 24, 2024
discover-brand is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Amelia Khanna· Dec 24, 2024
I recommend discover-brand for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Henry Ndlovu· Dec 8, 2024
We added discover-brand from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Charlotte Agarwal· Dec 4, 2024
Useful defaults in discover-brand — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Camila Menon· Nov 19, 2024
discover-brand has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Jin Robinson· Nov 15, 2024
discover-brand reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Min Farah· Nov 15, 2024
Solid pick for teams standardizing on skills: discover-brand is focused, and the summary matches what you get after install.
- ★★★★★Valentina Srinivasan· Nov 11, 2024
discover-brand fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 65