artifacts/bundle/skills/marketing-skill/competitor-alternatives/SKILL.md
# Competitor & Alternative Pages You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively. ## Initial Assessment **Check for product marketing context first:** If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
npx skillsauth add neekware/ehayeskills artifacts/bundle/skills/marketing-skill/competitor-alternativesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before creating competitor pages, understand:
Your Product
Competitive Landscape
Goals
Search intent: User is actively looking to switch from a specific competitor
URL pattern: /alternatives/[competitor] or /[competitor]-alternative
Target keywords: "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]"
Page structure:
Search intent: User is researching options, earlier in journey
URL pattern: /alternatives/[competitor]-alternatives
Target keywords: "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]"
Page structure:
Important: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.
Search intent: User is directly comparing you to a specific competitor
URL pattern: /vs/[competitor] or /compare/[you]-vs-[competitor]
Target keywords: "[You] vs [Competitor]", "[Competitor] vs [You]"
Page structure:
Search intent: User comparing two competitors (not you directly)
URL pattern: /compare/[competitor-a]-vs-[competitor-b]
Page structure:
Why this works: Captures search traffic for competitor terms, positions you as knowledgeable.
Start every page with a quick summary for scanners—key differences in 2-3 sentences.
Go beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.
For each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.
Include tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.
Be explicit about ideal customer for each option. Honest recommendations build trust.
Cover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.
For detailed templates: See references/templates.md
Create a single source of truth for each competitor with:
For data structure and examples: See references/content-architecture.md
For each competitor, gather:
| Format | Primary Keywords | | ------------------------ | --------------------------------------------------------- | | Alternative (singular) | [Competitor] alternative, alternative to [Competitor] | | Alternatives (plural) | [Competitor] alternatives, best [Competitor] alternatives | | You vs Competitor | [You] vs [Competitor], [Competitor] vs [You] | | Competitor vs Competitor | [A] vs [B], [B] vs [A] |
Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?"
Complete competitor profile in YAML format for use across all comparison pages.
For each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.
Recommended pages to create with priority order based on search volume.
Proactively offer competitor page creation when:
| Artifact | Format | Description |
| ---------------------------- | ---------------- | ------------------------------------------------------------------------------ |
| Competitor Intelligence File | YAML data file | Centralized competitor profile: pricing, features, weaknesses, review themes |
| Page Set Plan | Prioritized list | Ranked list of pages to build with target keywords and search volume estimates |
| Alternative Page (Singular) | Full page copy | Complete /[competitor]-alternative page with all sections |
| Vs Page | Full page copy | Complete /vs/[competitor] page with comparison table and CTA |
| Migration Guide Section | Markdown block | Reusable migration copy for inclusion across multiple pages |
All competitor page outputs should be factually accurate, legally safe (no false claims), and fair to competitors. Acknowledge genuine competitor strengths — pages that only disparage competitors lose credibility with evaluators. Reference marketing-context for ICP and positioning before writing any comparison copy. Quality bar: every claim must be verifiable from public sources or customer quotes.
Creator: Alireza Rezvani License: MIT Source Repo:
neekware/ehaye-skillsSource Bucket:marketing-skillOriginal Path:marketing-skill/competitor-alternatives
tools
# ehAye Multimedia Use this skill for **video, audio, images, media conversion, previews, transcription, thumbnails, frame extraction, Spotter visual search, or FFmpeg-backed processing**. Core rule: use ehAye native media tools first. Do not reach first for shell `ffmpeg`, `ffprobe`, Python, or `mediainfo` when a native media tool can do the job. Native tools use bundled engines, show proper tool UI, respect cancellation/timeouts, integrate with Preview/Spotter, and avoid cross-platform shell
development
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit. Handles test generation from source code, coverage report parsing (LCOV/JSON/XML), quality scoring, and framework conversion for TypeScript, JavaScript, Python, and Java projects.
tools
Help a user set up Telegram for ehAye Dojo. Default to Personal private bots (recommended). Group setup is advanced for teams/observers/demos.
development
# Writing Skills ## Overview **Writing skills IS Test-Driven Development applied to process documentation.** **Personal skills live in agent-specific directories (`~/.claude/skills` for Claude Code, `~/.agents/skills/` for Codex)** You write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes). **Core principle:** If you didn't watch an agent fail without the ski