Publisher: Corey Haines · Editorial profile by AI Tools Ratings · Review method
What task is this skill designed for?
Draft a comparison outline for two explicitly named products using only current official feature and pricing evidence.
What input and output should you expect?
Input: Named products, dated sources, target buyer task, comparable billing terms and an existing comparison if refreshing one.
Output: A claim ledger and decision-oriented outline covering fit, costs, limitations and migration questions, with unknowns left visible.
What does it need to run?
Agent Skills client plus browsing access or supplied current sources. Inspect the comparison-template and content-architecture references when building a reusable page family.
The pinned publisher README declares support for Agent Skills clients including Claude Code, Codex and Cursor. Compatibility follows the publisher’s stated support.
How should you approach installation?
- Inspect the pinned SKILL.md, license and referenced files needed for your specific task before installation.
- Follow the publisher README for your actual Agent Skills client.
- Try the illustrative prompt with synthetic material in a separate workspace. Review the checklist and approve any publishing, account or external-message action separately.
Installation guide: discovery, dependencies and runtime checks
What files, accounts or data can it access?
Reads public competitor documents and local marketing materials. It may draft public claims but does not authorize publication. Keep private sales intelligence separate from evidence that a reader can verify.
What does the skill cost?
MIT-licensed source. Agent subscriptions, model usage and optional research or analytics services have separate costs.
What are its limits and alternatives?
A feature absent from a pricing page is not proven unavailable. Plans and product names change, so conclusions need dates and matching scopes. A self-ranked list is not an independent benchmark.
Use Customer Research to understand evaluation criteria and SEO Audit for technical problems. This workflow is strongest when the named comparison and evidence already exist.
What could you ask in a small trial?
Try this with a small sample:
Compare fictional Alpha and Beta using these supplied source excerpts. Normalize annual versus monthly billing, mark undocumented features unknown and describe one buyer scenario favoring each. No unsupported winner or score.
How would you verify the result?
- Require a source and date for material product claims.
- Use equivalent units and billing commitments in price comparisons.
- Include honest reasons a buyer might choose either product.
Use a baseline and record acceptance evidence before treating a successful task as a reliable workflow.
Which source and license were checked?
Read the reviewed SKILL.md at its pinned commit · Complete reviewed folder
Repository and current publisher guidance
Checked:
MIT — identified in the repository LICENSE at the pinned commit. External services and dependencies have their own terms. License evidence
Version details and review scope
Source: coreyhaines31/marketingskills/skills/competitors
Reviewed commit: e85f3cbc2e4a79bf33b2a12e9bdd9087d414735b
SKILL.md SHA-256: ff77b76dfe43158b2fc248bb8c41fe94745d1264abb0a0c665b2c55318287a35
Source-document review. This profile covers the source workflow, stated dependencies and license evidence. See our editorial methodology for how we distinguish source reviews and hands-on evaluations.