brand-research-agent
Use this skill to analyze a brand from their website before creating content. Triggers: "analyze brand", "research brand", "brand guidelines", "brand profile", "understand brand", "brand colors", "brand voice", "before creating content for" Extracts: colors, typography, voice/tone, products, audience, competitive positioning. Outputs a reusable brand_profile.json that producer skills can use.
What this skill does
# Brand Research Skill
Analyze a brand's website to extract brand elements for content creation.
**This skill uses 5 specialized agents** that analyze different brand dimensions in parallel, then synthesizes into a unified brand profile.
## What It Extracts
| Dimension | Elements | Used For |
|-----------|----------|----------|
| **Visual** | Colors, typography, logo, imagery style | Image prompts, video style |
| **Voice** | Tone, messaging, taglines, copy style | Voiceover, scripts |
| **Product** | Offerings, features, USPs, pricing | Content focus |
| **Audience** | Demographics, psychographics, pain points | Tone targeting |
| **Positioning** | Market position, competitors, differentiation | Messaging strategy |
## Prerequisites
- Browser access (uses web scraping)
- No API keys required
## Workflow
### Step 1: Get the Website URL (REQUIRED)
**FIRST, always ask for the website URL.** Do not proceed without it.
**Say this to the user:**
> "I'll analyze that brand for you!
>
> **What's the website URL?** (e.g., https://nike.com)
>
> Optional: Any specific pages to focus on? Any known competitors?"
**Wait for the user to provide the URL before proceeding.**
If the user just says "analyze Nike's brand", ask:
> "I'll analyze Nike for you. Just to confirm - should I use https://nike.com?"
---
### Step 2: Navigate and Capture Website Data
Use browser tools to navigate the website and capture:
```
1. Homepage - Overall impression, hero messaging, colors
2. About page - Company story, values, team
3. Products/Services page - Offerings, features, pricing
4. Blog/Resources - Voice, content style
5. Footer - Social links, taglines
```
**Capture for each page:**
- Screenshot for visual analysis
- HTML/CSS for colors and fonts
- Text content for voice analysis
- Images for style analysis
---
### Step 3: Run Specialized Agents in Parallel
Deploy 5 agents, each analyzing a different dimension:
#### Agent 1: Visual Analyst
Focus: Colors, typography, logo, imagery style
```
Analyze:
- Primary, secondary, accent colors from CSS/design
- Font families for headings and body
- Logo usage and placement
- Photography/illustration style
- Overall visual mood (minimal, bold, playful, etc.)
```
#### Agent 2: Voice Analyst
Focus: Tone, messaging, taglines, copy style
```
Analyze:
- Headlines and how they're written
- Body copy style (formal vs casual)
- CTAs and their tone
- Taglines and slogans
- Emotional appeals used
```
#### Agent 3: Product Analyst
Focus: Offerings, features, USPs, pricing
```
Analyze:
- What products/services they offer
- Key features highlighted
- Unique selling propositions
- Pricing model and tiers
- Value propositions
```
#### Agent 4: Audience Analyst
Focus: Demographics, psychographics, pain points
```
Analyze:
- Who the messaging targets
- Pain points addressed
- Aspirations appealed to
- Language level and jargon
- Testimonials and case studies
```
#### Agent 5: Competitive Analyst
Focus: Market position, competitors, differentiation
```
Analyze:
- Market/industry category
- Implied competitors
- How they differentiate
- Unique market position
- Competitive advantages claimed
```
---
### Step 4: Synthesize into Brand Profile
Combine all agent outputs into a unified `brand_profile.json`:
```json
{
"brand": {
"name": "Company Name",
"website": "https://example.com",
"tagline": "Their main tagline",
"analyzed_date": "2026-01-04"
},
"visual": {
"colors": {
"primary": "#1E40AF",
"secondary": "#F59E0B",
"accent": "#10B981",
"background": "#FFFFFF",
"text": "#1F2937"
},
"typography": {
"headings": "Montserrat Bold",
"body": "Open Sans",
"style": "Modern, clean"
},
"logo": {
"description": "Abstract geometric mark + wordmark",
"usage": "Typically on white/dark backgrounds"
},
"imagery_style": {
"type": "Photography",
"mood": "Professional, aspirational",
"subjects": "People using product, office settings",
"treatment": "Bright, high contrast, natural lighting"
}
},
"voice": {
"tone": ["Confident", "Approachable", "Expert"],
"personality": "Like a smart friend who knows their stuff",
"formality": "Professional casual",
"style_notes": [
"Short, punchy sentences",
"Active voice preferred",
"Benefit-focused over feature-focused",
"Uses 'you' and 'your' frequently"
],
"example_headlines": [
"Built for builders",
"Simple. Powerful. Yours."
],
"words_to_use": ["Simple", "Powerful", "Fast", "Seamless"],
"words_to_avoid": ["Cheap", "Basic", "Just"]
},
"products": {
"category": "SaaS / Developer Tools",
"offerings": [
{
"name": "Core Platform",
"description": "Main product offering",
"key_features": ["Feature 1", "Feature 2", "Feature 3"]
}
],
"usps": [
"10x faster than alternatives",
"No-code setup in 5 minutes",
"Enterprise-grade security"
],
"pricing_model": "Freemium with usage-based scaling",
"value_proposition": "Get to market faster without sacrificing quality"
},
"audience": {
"primary": {
"who": "Technical founders and developers",
"demographics": "25-45, tech-savvy, startup/scale-up",
"psychographics": "Move fast, value efficiency, quality-conscious"
},
"secondary": {
"who": "Enterprise DevOps teams",
"demographics": "Large companies, IT departments"
},
"pain_points": [
"Complex setup processes",
"Slow iteration cycles",
"Scaling costs out of control"
],
"aspirations": [
"Ship faster",
"Look professional",
"Scale effortlessly"
]
},
"positioning": {
"market": "Developer tools / Infrastructure",
"competitors": ["Competitor A", "Competitor B", "Competitor C"],
"differentiation": "Simplicity + Enterprise power in one package",
"market_position": "Premium but accessible",
"competitive_advantages": [
"Easiest setup in category",
"Best-in-class performance",
"Loved by developers"
]
},
"content_guidelines": {
"for_video_producer": {
"music_style": "Modern, upbeat, confident but not aggressive",
"voiceover_tone": "Confident, clear, approachable expert",
"visual_style": "Clean, minimal, bold accents, professional"
},
"for_podcast_producer": {
"host_personality": "Smart, curious, enthusiastic about tech",
"conversation_style": "Educational but engaging, not dry"
},
"for_audio_producer": {
"voiceover_direction": "Professional but warm, not corporate robot",
"music_mood": "Inspiring, forward-moving, modern"
},
"for_social_producer": {
"image_style": "Clean product shots, lifestyle use cases",
"video_style": "Quick, punchy, value-first",
"copy_style": "Short, benefit-focused, emoji-light"
}
}
}
```
---
### Step 5: Save and Deliver
Save the brand profile:
```bash
# Save to current directory
brand_profile.json
# Or to a specific location
/path/to/project/brand_profile.json
```
**Delivery message:**
"✅ Brand analysis complete!
**Brand Profile saved to:** `brand_profile.json`
**Summary:**
- **Brand:** Acme Corp
- **Colors:** Blue (#1E40AF) + Orange (#F59E0B)
- **Voice:** Confident, approachable, expert
- **Audience:** Technical founders, 25-45
- **Position:** Simplicity + Power
**Use this profile with:**
- `video-producer --brand brand_profile.json`
- `podcast-producer --brand brand_profile.json`
- `social-producer --brand brand_profile.json`
**Want me to:**
- Analyze additional pages?
- Deep dive on any dimension?
- Create content using this profile?"
---
## Using the Brand Profile with Producers
Once you have a `brand_profile.json`, reference it when creating content:
**Example workflow:**
```
USER: "Create a product video using our brand profile"
PRODUCER:
1. Reads brand_profile.Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".