comparison-table
starsforks
How to install comparison-table?
kostja94/marketing-skills/comparison-table
$npx -y skills add kostja94/marketing-skills --skill comparison-tableWhen the user wants to create, optimize, or audit a comparison table section—an in-page block (HTML table or responsive equivalent) comparing products, methods, or approaches, with optional supporting copy. Also use when the user mentions "comparison table," "compare table," "fea
SKILL.md
| 1 | # Components: Comparison Table Section |
| 2 | |
| 3 | Guides **comparison tables as an in-page section**: a **scannable matrix** (rows × columns) embedded **inside** landing pages, blog posts, pricing pages, homepages, or docs. **Not** a standalone page type—parent page structure, URLs, and "alternatives vs blog" decisions come from **alternatives-page-generator**, **landing-page-generator**, **article-page-generator**, **pricing-page-generator**, etc. Distinct from **FAQ** (Q&A → FAQPage) and from **HowTo** (procedure → HowTo). **schema-markup** remains the source for exhaustive Schema.org rules; this skill owns **section-level** criteria, copy, HTML/accessibility, fairness, and ad alignment. |
| 4 | |
| 5 | **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. |
| 6 | |
| 7 | ## Comparison Table Section vs Alternatives Page |
| 8 | |
| 9 | | Dimension | Comparison table **section** (this skill) | Alternatives / compare **page** | |
| 10 | |-----------|-------------------------------------------|----------------------------------| |
| 11 | | **Scope** | One block: headings, table, footnotes, optional CTA line | Full page or article: headline, intro, verdict, listicles, FAQ, metadata | |
| 12 | | **URL / intent** | Chosen by parent; section supports **commercial** or **informational** parent | Owns **"X alternatives"**, **"X vs Y"**, PPC landing strategy | |
| 13 | | **PPC** | Align **copy and criteria** with ad and parent LP | Owns **where** paid traffic lands (dedicated LP vs blog) | |
| 14 | | **Skill** | **comparison-table-generator** (this) | **alternatives-page-generator** | |
| 15 | |
| 16 | Use **both** when building an alternatives LP: **alternatives-page-generator** for page structure; **comparison-table-generator** for the **table** itself (criteria, rows, cells, fairness). |
| 17 | |
| 18 | ## Comparison Types (Same Component, Different Framing) |
| 19 | |
| 20 | | Type | Rows / columns | Typical use | |
| 21 | |------|------------------|-------------| |
| 22 | | **Product vs product** | You vs 1–N competitors or tools | Alternatives LP, category pages, blog "best X" | |
| 23 | | **Traditional vs modern** | Old workflow vs your approach | Category creation, thought leadership, LP objection handling | |
| 24 | | **Manual vs automated** | Spreadsheets, agencies, DIY vs product | Mid-funnel LP, demo request pages | |
| 25 | | **Before / after** | State A vs State B (metrics allowed if true) | Outcome-focused LP, case studies | |
| 26 | | **Feature / capability matrix** | Features as rows; plans or products as columns | Pricing-adjacent, **features-page-generator** context | |
| 27 | |
| 28 | **Column count**: Prefer **4–7 columns** including names; more columns hurt mobile—use **priority columns** above the fold and **expand** or **link** to full spec. |
| 29 | |
| 30 | ## Placement Within the Parent Page |
| 31 | |
| 32 | | Location | When | |
| 33 | |----------|------| |
| 34 | | **After hero + short value prop** | LP: remove doubt early; **before** long prose | |
| 35 | | **After "problem" / "why switch"** | Alternatives or comparison article: user is ready for criteria | |
| 36 | | **Before FAQ** | Table answers "which is better for X?"; FAQ handles objections | |
| 37 | | **Mid-article** | Blog: after context; supports **featured-snippet** table patterns | |
| 38 | |
| 39 | **Narrative**: Table should **answer** the promise of the H1/H2—do not bury the matrix below unrelated storytelling. |
| 40 | |
| 41 | ## Content Structure |
| 42 | |
| 43 | ### Section title (H2) |
| 44 | |
| 45 | - **Default**: Outcome or task-oriented—"How [Product] compares to [Competitor]," "[Category] comparison at a glance," "Traditional vs [Your approach]." |
| 46 | - **Avoid**: Vague **"Comparison"** alone; match query language where relevant (**"vs"**, **alternatives**, **best for**). |
| 47 | |
| 48 | ### Intro (1–3 sentences) |
| 49 | |
| 50 | - State **who** the table is for and **criteria** (e.g. "pricing as of [date]," "SMB-focused"). |
| 51 | - **Transparency**: "We sell [Product]; we include [Competitor] because users search for both." |
| 52 | |
| 53 | ### The table |
| 54 | |
| 55 | - **HTML `<table>`** with `<thead>`, `<th>` scope, **`<caption>`** (summary for screen readers). |
| 56 | - **Cells**: Short phrases, icons, or **Yes/No/Limited**—avoid marketing fluff in cells; **footnote** |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
