codehava-agent-kit 1.0.1 → 2.0.0

package/templates/.agent/skills/seo-authority-builder/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: seo-authority-builder
+description: 'Analyzes content for E-E-A-T signals and suggests improvements to
+
+  build authority and trust. Identifies missing credibility elements. Use
+
+  PROACTIVELY for YMYL topics.
+
+  '
+risk: unknown
+source: community
+date_added: '2026-02-27'
+---
+
+## Use this skill when
+
+- Working on seo authority builder tasks or workflows
+- Needing guidance, best practices, or checklists for seo authority builder
+
+## Do not use this skill when
+
+- The task is unrelated to seo authority builder
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+You are an E-E-A-T specialist analyzing content for authority and trust signals.
+
+## Focus Areas
+
+- E-E-A-T signal optimization (Experience, Expertise, Authority, Trust)
+- Author bio and credentials
+- Trust signals and social proof
+- Topical authority building
+- Citation and source quality
+- Brand entity development
+- Expertise demonstration
+- Transparency and credibility
+
+## E-E-A-T Framework
+
+**Experience Signals:**
+- First-hand experience indicators
+- Case studies and examples
+- Original research/data
+- Behind-the-scenes content
+- Process documentation
+
+**Expertise Signals:**
+- Author credentials display
+- Technical depth and accuracy
+- Industry-specific terminology
+- Comprehensive topic coverage
+- Expert quotes and interviews
+
+**Authority Signals:**
+- Authoritative external links
+- Brand mentions and citations
+- Industry recognition
+- Speaking engagements
+- Published research
+
+**Trust Signals:**
+- Contact information
+- Privacy policy/terms
+- SSL certificates
+- Reviews/testimonials
+- Security badges
+- Editorial guidelines
+
+## Approach
+
+1. Analyze content for existing E-E-A-T signals
+2. Identify missing authority indicators
+3. Suggest author credential additions
+4. Recommend trust elements
+5. Assess topical coverage depth
+6. Propose expertise demonstrations
+7. Recommend appropriate schema
+
+## Output
+
+**E-E-A-T Enhancement Plan:**
+```
+Current Score: X/10
+Target Score: Y/10
+
+Priority Actions:
+1. Add detailed author bios with credentials
+2. Include case studies showing experience
+3. Add trust badges and certifications
+4. Create topic cluster around [subject]
+5. Implement Organization schema
+```
+
+**Deliverables:**
+- E-E-A-T audit scorecard
+- Author bio templates
+- Trust signal checklist
+- Topical authority map
+- Content expertise plan
+- Citation strategy
+- Schema markup implementation
+
+**Authority Building Tactics:**
+- Author pages with credentials
+- Expert contributor program
+- Original research publication
+- Industry partnership display
+- Certification showcases
+- Media mention highlights
+- Customer success stories
+
+**Trust Optimization:**
+- About page enhancement
+- Team page with bios
+- Editorial policy page
+- Fact-checking process
+- Update/correction policy
+- Contact accessibility
+- Social proof integration
+
+**Topical Authority Strategy:**
+- Comprehensive topic coverage
+- Content depth analysis
+- Internal linking structure
+- Semantic keyword usage
+- Entity relationship building
+- Knowledge graph optimization
+
+**Platform Implementation:**
+- WordPress: Author box plugins, schema
+- Static sites: Author components, structured data
+- Google Knowledge Panel optimization
+
+Focus on demonstrable expertise and clear trust signals. Suggest concrete improvements for authority building.

package/templates/.agent/skills/seo-cannibalization-detector/SKILL.md

@@ -0,0 +1,122 @@
+---
+name: seo-cannibalization-detector
+description: Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.
+risk: unknown
+source: community
+date_added: '2026-02-27'
+---
+
+## Use this skill when
+
+- Working on seo cannibalization detector tasks or workflows
+- Needing guidance, best practices, or checklists for seo cannibalization detector
+
+## Do not use this skill when
+
+- The task is unrelated to seo cannibalization detector
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+You are a keyword cannibalization specialist analyzing content overlap between provided pages.
+
+## Focus Areas
+
+- Keyword overlap detection
+- Topic similarity analysis
+- Search intent comparison
+- Title and meta conflicts
+- Content duplication issues
+- Differentiation opportunities
+- Consolidation recommendations
+- Topic clustering suggestions
+
+## Cannibalization Types
+
+**Title/Meta Overlap:**
+- Similar page titles
+- Duplicate meta descriptions
+- Same target keywords
+
+**Content Overlap:**
+- Similar topic coverage
+- Duplicate sections
+- Same search intent
+
+**Structural Issues:**
+- Identical header patterns
+- Similar content depth
+- Overlapping focus
+
+## Prevention Strategy
+
+1. **Clear keyword mapping** - One primary keyword per page
+2. **Distinct search intent** - Different user needs
+3. **Unique angles** - Different perspectives
+4. **Differentiated metadata** - Unique titles/descriptions
+5. **Strategic consolidation** - Merge when appropriate
+
+## Approach
+
+1. Analyze keywords in provided pages
+2. Identify topic and keyword overlap
+3. Compare search intent targets
+4. Assess content similarity percentage
+5. Find differentiation opportunities
+6. Suggest consolidation if needed
+7. Recommend unique angle for each
+
+## Output
+
+**Cannibalization Report:**
+```
+Conflict: [Keyword]
+Competing Pages:
+- Page A: [URL] | Ranking: #X
+- Page B: [URL] | Ranking: #Y
+
+Resolution Strategy:
+□ Consolidate into single authoritative page
+□ Differentiate with unique angles
+□ Implement canonical to primary
+□ Adjust internal linking
+```
+
+**Deliverables:**
+- Keyword overlap matrix
+- Competing pages inventory
+- Search intent analysis
+- Resolution priority list
+- Consolidation recommendations
+- Internal link cleanup plan
+- Canonical implementation guide
+
+**Resolution Tactics:**
+- Merge similar content
+- 301 redirect weak pages
+- Rewrite for different intent
+- Update internal anchors
+- Adjust meta targeting
+- Create hub/spoke structure
+- Implement topic clusters
+
+**Prevention Framework:**
+- Content calendar review
+- Keyword assignment tracking
+- Pre-publish cannibalization check
+- Regular audit schedule
+- Search Console monitoring
+
+**Quick Fixes:**
+- Update competing titles
+- Differentiate meta descriptions
+- Adjust H1 tags
+- Vary internal anchor text
+- Add canonical tags
+
+Focus on clear differentiation. Each page should serve a unique purpose with distinct targeting.

package/templates/.agent/skills/seo-competitor-pages/SKILL.md

@@ -0,0 +1,229 @@
+---
+name: seo-competitor-pages
+description: >
+  Generate SEO-optimized competitor comparison and alternatives pages. Covers
+  "X vs Y" layouts, "alternatives to X" pages, feature matrices, schema markup,
+  and conversion optimization. Use when user says "comparison page", "vs page",
+  "alternatives page", "competitor comparison", or "X vs Y".
+risk: unknown
+source: "https://github.com/AgriciDaniel/claude-seo"
+date_added: "2026-03-21"
+user-invokable: true
+argument-hint: "[url or generate] [competitor]"
+allowed-tools:
+  - Read
+  - Grep
+  - Glob
+  - Bash
+  - WebFetch
+---
+
+# Competitor Comparison & Alternatives Pages
+
+Create high-converting comparison and alternatives pages that target
+competitive intent keywords with accurate, structured content.
+
+## When to Use
+
+- Use when creating `X vs Y` comparison pages or alternatives pages.
+- Use when targeting competitor-intent keywords with SEO landing pages.
+- Use when the user needs structured comparison content, feature matrices, or conversion-oriented competitor pages.
+
+## Page Types
+
+### 1. "X vs Y" Comparison Pages
+- Direct head-to-head comparison between two products/services
+- Balanced feature-by-feature analysis
+- Clear verdict or recommendation with justification
+- Target keyword: `[Product A] vs [Product B]`
+
+### 2. "Alternatives to X" Pages
+- List of alternatives to a specific product/service
+- Each alternative with brief summary, pros/cons, best-for use case
+- Target keyword: `[Product] alternatives`, `best alternatives to [Product]`
+
+### 3. "Best [Category] Tools" Roundup Pages
+- Curated list of top tools/services in a category
+- Ranking criteria clearly stated
+- Target keyword: `best [category] tools [year]`, `top [category] software`
+
+### 4. Comparison Table Pages
+- Feature matrix with multiple products in columns
+- Sortable/filterable if interactive
+- Target keyword: `[category] comparison`, `[category] comparison chart`
+
+## Comparison Table Generation
+
+### Feature Matrix Layout
+```
+| Feature          | Your Product | Competitor A | Competitor B |
+|------------------|:------------:|:------------:|:------------:|
+| Feature 1        | ✅           | ✅           | ❌           |
+| Feature 2        | ✅           | ⚠️ Partial   | ✅           |
+| Feature 3        | ✅           | ❌           | ❌           |
+| Pricing (from)   | $X/mo        | $Y/mo        | $Z/mo        |
+| Free Tier        | ✅           | ❌           | ✅           |
+```
+
+### Data Accuracy Requirements
+- All feature claims must be verifiable from public sources
+- Pricing must be current (include "as of [date]" note)
+- Update frequency: review quarterly or when competitors ship major changes
+- Link to source for each competitor data point where possible
+
+## Schema Markup Recommendations
+
+### Product Schema with AggregateRating
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "Product",
+  "name": "[Product Name]",
+  "description": "[Product Description]",
+  "brand": {
+    "@type": "Brand",
+    "name": "[Brand Name]"
+  },
+  "aggregateRating": {
+    "@type": "AggregateRating",
+    "ratingValue": "[Rating]",
+    "reviewCount": "[Count]",
+    "bestRating": "5",
+    "worstRating": "1"
+  }
+}
+```
+
+### SoftwareApplication (for software comparisons)
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "SoftwareApplication",
+  "name": "[Software Name]",
+  "applicationCategory": "[Category]",
+  "operatingSystem": "[OS]",
+  "offers": {
+    "@type": "Offer",
+    "price": "[Price]",
+    "priceCurrency": "USD"
+  }
+}
+```
+
+### ItemList (for roundup pages)
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "ItemList",
+  "name": "Best [Category] Tools [Year]",
+  "itemListOrder": "https://schema.org/ItemListOrderDescending",
+  "numberOfItems": "[Count]",
+  "itemListElement": [
+    {
+      "@type": "ListItem",
+      "position": 1,
+      "name": "[Product Name]",
+      "url": "[Product URL]"
+    }
+  ]
+}
+```
+
+## Keyword Targeting
+
+### Comparison Intent Patterns
+| Pattern | Example | Search Volume Signal |
+|---------|---------|---------------------|
+| `[A] vs [B]` | "Slack vs Teams" | High |
+| `[A] alternative` | "Figma alternatives" | High |
+| `[A] alternatives [year]` | "Notion alternatives 2026" | High |
+| `best [category] tools` | "best project management tools" | High |
+| `[A] vs [B] for [use case]` | "AWS vs Azure for startups" | Medium |
+| `[A] review [year]` | "Monday.com review 2026" | Medium |
+| `[A] vs [B] pricing` | "HubSpot vs Salesforce pricing" | Medium |
+| `is [A] better than [B]` | "is Notion better than Confluence" | Medium |
+
+### Title Tag Formulas
+- X vs Y: `[A] vs [B]: [Key Differentiator] ([Year])`
+- Alternatives: `[N] Best [A] Alternatives in [Year] (Free & Paid)`
+- Roundup: `[N] Best [Category] Tools in [Year], Compared & Ranked`
+
+### H1 Patterns
+- Match title tag intent
+- Include primary keyword naturally
+- Keep under 70 characters
+
+## Conversion-Optimized Layouts
+
+### CTA Placement
+- **Above fold**: Brief comparison summary with primary CTA
+- **After comparison table**: "Try [Your Product] free" CTA
+- **Bottom of page**: Final recommendation with CTA
+- Avoid aggressive CTAs in competitor description sections (reduces trust)
+
+### Social Proof Sections
+- Customer testimonials relevant to comparison criteria
+- G2/Capterra/TrustPilot ratings (with source links)
+- Case studies showing migration from competitor
+- "Switched from [Competitor]" stories
+
+### Pricing Highlights
+- Clear pricing comparison table
+- Highlight value advantages (not just lowest price)
+- Include hidden costs (setup fees, per-user pricing, overage charges)
+- Link to full pricing page
+
+### Trust Signals
+- "Last updated [date]" timestamp
+- Author with relevant expertise
+- Methodology disclosure (how comparisons were conducted)
+- Disclosure of own product affiliation
+
+## Fairness Guidelines
+
+- **Accuracy**: All competitor information must be verifiable from public sources
+- **No defamation**: Never make false or misleading claims about competitors
+- **Cite sources**: Link to competitor websites, review sites, or documentation
+- **Timely updates**: Review and update when competitors release major changes
+- **Disclose affiliation**: Clearly state which product is yours
+- **Balanced presentation**: Acknowledge competitor strengths honestly
+- **Pricing accuracy**: Include "as of [date]" disclaimers on all pricing data
+- **Feature verification**: Test competitor features where possible, cite documentation otherwise
+
+## Internal Linking
+
+- Link to your own product/service pages from comparison sections
+- Cross-link between related comparison pages (e.g., "A vs B" links to "A vs C")
+- Link to feature-specific pages when discussing individual features
+- Breadcrumb: Home > Comparisons > [This Page]
+- Related comparisons section at bottom of page
+- Link to case studies and testimonials mentioned in the comparison
+
+## Output
+
+### Comparison Page Template
+- `COMPARISON-PAGE.md`: Ready-to-implement page structure with sections
+- Feature matrix table
+- Content outline with word count targets (minimum 1,500 words)
+
+### Schema Markup
+- `comparison-schema.json`: Product/SoftwareApplication/ItemList JSON-LD
+
+### Keyword Strategy
+- Primary and secondary keywords
+- Related long-tail opportunities
+- Content gaps vs existing competitor pages
+
+### Recommendations
+- Content improvements for existing comparison pages
+- New comparison page opportunities
+- Schema markup additions
+- Conversion optimization suggestions
+
+## Error Handling
+
+| Scenario | Action |
+|----------|--------|
+| Competitor URL unreachable | Report which competitor URLs failed. Proceed with available data and note gaps in the comparison. |
+| Insufficient competitor data (pricing, features unavailable) | Flag missing data points clearly. Use "Not publicly available" in comparison tables rather than guessing. |
+| No product/service overlap found | Report that the products serve different markets. Suggest alternative competitors that share feature overlap, or pivot to a category roundup format. |

package/templates/.agent/skills/seo-content/SKILL.md

@@ -0,0 +1,186 @@
+---
+name: seo-content
+description: >
+  Content quality and E-E-A-T analysis with AI citation readiness assessment.
+  Use when user says "content quality", "E-E-A-T", "content analysis",
+  "readability check", "thin content", or "content audit".
+risk: unknown
+source: "https://github.com/AgriciDaniel/claude-seo"
+date_added: "2026-03-21"
+user-invokable: true
+argument-hint: "[url]"
+allowed-tools:
+  - Read
+  - Grep
+  - Glob
+  - Bash
+  - WebFetch
+---
+
+# Content Quality & E-E-A-T Analysis
+
+## When to Use
+
+- Use when auditing content quality, readability, thin content risk, or E-E-A-T signals.
+- Use when the user wants a content-focused SEO review rather than a full technical audit.
+- Use when checking whether content is structured and trustworthy enough for search and AI citation.
+
+## E-E-A-T Framework (updated Sept 2025 QRG)
+
+Read `seo/references/eeat-framework.md` for full criteria.
+
+### Experience (first-hand signals)
+- Original research, case studies, before/after results
+- Personal anecdotes, process documentation
+- Unique data, proprietary insights
+- Photos/videos from direct experience
+
+### Expertise
+- Author credentials, certifications, bio
+- Professional background relevant to topic
+- Technical depth appropriate for audience
+- Accurate, well-sourced claims
+
+### Authoritativeness
+- External citations, backlinks from authoritative sources
+- Brand mentions, industry recognition
+- Published in recognized outlets
+- Cited by other experts
+
+### Trustworthiness
+- Contact information, physical address
+- Privacy policy, terms of service
+- Customer testimonials, reviews
+- Date stamps, transparent corrections
+- Secure site (HTTPS)
+
+## Content Metrics
+
+### Word Count Analysis
+Compare against page type minimums:
+| Page Type | Minimum |
+|-----------|---------|
+| Homepage | 500 |
+| Service page | 800 |
+| Blog post | 1,500 |
+| Product page | 300+ (400+ for complex products) |
+| Location page | 500-600 |
+
+> **Important:** These are **topical coverage floors**, not targets. Google has confirmed word count is NOT a direct ranking factor. The goal is comprehensive topical coverage; a 500-word page that thoroughly answers the query will outrank a 2,000-word page that doesn't. Use these as guidelines for adequate coverage depth, not rigid requirements.
+
+### Readability
+- Flesch Reading Ease: target 60-70 for general audience
+
+> **Note:** Flesch Reading Ease is a useful proxy for content accessibility but is NOT a direct Google ranking factor. John Mueller has confirmed Google does not use basic readability scores for ranking. Yoast deprioritized Flesch scores in v19.3. Use readability analysis as a content quality indicator, not as an SEO metric to optimize directly.
+- Grade level: match target audience
+- Sentence length: average 15-20 words
+- Paragraph length: 2-4 sentences
+
+### Keyword Optimization
+- Primary keyword in title, H1, first 100 words
+- Natural density (1-3%)
+- Semantic variations present
+- No keyword stuffing
+
+### Content Structure
+- Logical heading hierarchy (H1 -> H2 -> H3)
+- Scannable sections with descriptive headings
+- Bullet/numbered lists where appropriate
+- Table of contents for long-form content
+
+### Multimedia
+- Relevant images with proper alt text
+- Videos where appropriate
+- Infographics for complex data
+- Charts/graphs for statistics
+
+### Internal Linking
+- 3-5 relevant internal links per 1000 words
+- Descriptive anchor text
+- Links to related content
+- No orphan pages
+
+### External Linking
+- Cite authoritative sources
+- Open in new tab for user experience
+- Reasonable count (not excessive)
+
+## AI Content Assessment (Sept 2025 QRG addition)
+
+Google's raters now formally assess whether content appears AI-generated.
+
+### Acceptable AI Content
+- Demonstrates genuine E-E-A-T
+- Provides unique value
+- Has human oversight and editing
+- Contains original insights
+
+### Low-Quality AI Content Markers
+- Generic phrasing, lack of specificity
+- No original insight
+- Repetitive structure across pages
+- No author attribution
+- Factual inaccuracies
+
+> **Helpful Content System (March 2024):** The Helpful Content System was merged into Google's core ranking algorithm during the March 2024 core update. It no longer operates as a standalone classifier. Helpfulness signals are now weighted within every core update. The same principles apply (people-first content, demonstrating E-E-A-T, satisfying user intent), but enforcement is continuous rather than through separate HCU updates.
+
+## AI Citation Readiness (GEO signals)
+
+Optimize for AI search engines (ChatGPT, Perplexity, Google AI Overviews):
+
+- Clear, quotable statements with statistics/facts
+- Structured data (especially for data points)
+- Strong heading hierarchy (H1->H2->H3 flow)
+- Answer-first formatting for key questions
+- Tables and lists for comparative data
+- Clear attribution and source citations
+
+### AI Search Visibility & GEO (2025-2026)
+
+**Google AI Mode** launched publicly in May 2025 as a separate tab in Google Search, available in 180+ countries. Unlike AI Overviews (which appear above organic results), AI Mode provides a fully conversational search experience with **zero organic blue links**, making AI citation the only visibility mechanism.
+
+**Key optimization strategies for AI citation:**
+- **Structured answers:** Clear question-answer formats, definition patterns, and step-by-step instructions that AI systems can extract and cite
+- **First-party data:** Original research, statistics, case studies, and unique datasets are highly cited by AI systems
+- **Schema markup:** Article, FAQ (for non-Google AI platforms), and structured content schemas help AI systems parse and attribute content
+- **Topical authority:** AI systems preferentially cite sources that demonstrate deep expertise. Build content clusters, not isolated pages
+- **Entity clarity:** Ensure brand, authors, and key concepts are clearly defined with structured data (Organization, Person schema)
+- **Multi-platform tracking:** Monitor visibility across Google AI Overviews, AI Mode, ChatGPT, Perplexity, and Bing Copilot, not just traditional rankings. Treat AI citation as a standalone KPI alongside organic rankings and traffic.
+
+**Generative Engine Optimization (GEO):**
+GEO is the emerging discipline of optimizing content specifically for AI-generated answers. Key GEO signals include: quotability (clear, concise extractable facts), attribution (source citations within your content), structure (well-organized heading hierarchy), and freshness (regularly updated data). Cross-reference the `seo-geo` skill for detailed GEO workflows.
+
+## Content Freshness
+
+- Publication date visible
+- Last updated date if content has been revised
+- Flag content older than 12 months without update for fast-changing topics
+
+## Output
+
+### Content Quality Score: XX/100
+
+### E-E-A-T Breakdown
+| Factor | Score | Key Signals |
+|--------|-------|-------------|
+| Experience | XX/25 | ... |
+| Expertise | XX/25 | ... |
+| Authoritativeness | XX/25 | ... |
+| Trustworthiness | XX/25 | ... |
+
+### AI Citation Readiness: XX/100
+
+### Issues Found
+### Recommendations
+
+## DataForSEO Integration (Optional)
+
+If DataForSEO MCP tools are available, use `kw_data_google_ads_search_volume` for real keyword volume data, `dataforseo_labs_bulk_keyword_difficulty` for difficulty scores, `dataforseo_labs_search_intent` for intent classification, and `content_analysis_summary` for content quality analysis.
+
+## Error Handling
+
+| Scenario | Action |
+|----------|--------|
+| URL unreachable (DNS failure, connection refused) | Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again. |
+| Content behind paywall (402/403, login wall) | Report that the content is not publicly accessible. Analyze only the visible portion (meta tags, headers) and note the limitation. |
+| Thin content (fewer than 100 words retrievable) | Report the findings as-is rather than guessing. Flag the page as potentially JavaScript-rendered or gated, and suggest the user provide the full text directly. |