Product Comparison Writer

v1.0.0

Generates fair, structured, balanced product comparisons, pros/cons lists, buying guides, and personalized recommendations for informed purchase decisions.

0· 26·0 current·0 all-time
byhaidong@harrylabsj

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for harrylabsj/product-comparison-writer.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Product Comparison Writer" (harrylabsj/product-comparison-writer) from ClawHub.
Skill page: https://clawhub.ai/harrylabsj/product-comparison-writer
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install product-comparison-writer

ClawHub CLI

Package manager switcher

npx clawhub@latest install product-comparison-writer
Security Scan
Capability signals
CryptoCan make purchases
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name, description, and prompt templates all match a copywriter/comparison use case. The skill requests no binaries, credentials, or config paths — appropriate for a text-generation prompt-flow that relies on user-provided product data.
Instruction Scope
SKILL.md stays within the stated purpose (build tables, pros/cons, 'best for' recommendations, fairness gate). One minor mismatch: the instructions repeatedly require citing third‑party sources when used, but the skill is instruction-only and skill.json claims 'no_network' — implying the agent cannot fetch sources on its own. Citations will therefore depend on user-supplied data or an external tool/permission; clarify how source data is expected to be provided.
Install Mechanism
No install spec and no code files — lowest-risk pattern. Nothing is downloaded or written to disk by the skill itself.
Credentials
No environment variables, credentials, or config paths are required, which is proportionate for this task.
Persistence & Privilege
always:false and normal autonomous invocation is allowed; the skill does not request elevated persistence or modify other skills/configuration.
Assessment
This skill appears internally consistent and low-risk, but check these practical points before installing: (1) Decide how source citations will be provided — the SKILL.md demands citations but the skill claims no network access, so you must supply source URLs/text in inputs or permit a separate browsing/data skill. (2) Provide accurate product specs and disclosures (sponsored/editorial) as inputs; the fairness gate depends on input quality. (3) Confirm whether your agent environment enforces the 'no_network' and 'no_code_execution' constraints; if not, verify any network-capable tools the agent could call. (4) Review outputs for factual accuracy and potential legal/defamatory phrasing despite the safety rules — the assistant can still make mistakes. (5) Note minor metadata mismatches (README install path vs registry owner id) — likely benign but worth confirming the correct package source.

Like a lobster shell, security has layers — review code before you run it.

latestvk97cq4t5dp0khpr34s4asvk4qx85ms2r
26downloads
0stars
1versions
Updated 11h ago
v1.0.0
MIT-0

Product Comparison & Review Copywriter

Purpose

This skill generates fair, structured product comparison content — head-to-head comparison tables, category buying guides, balanced pros/cons analyses, specification battles, and personalized "best for" recommendations. It is built with fairness as a first principle: the output must be useful to readers making purchase decisions, not a disguised sales pitch. Designed for e-commerce product pages, editorial content, affiliate marketing, and merchant category pages.

Triggers

  • "product comparison"
  • "product VS"
  • "对比评测"
  • "buying guide"
  • "pros and cons"
  • "选购指南"
  • "compare products"
  • "spec comparison"
  • "best for recommendation"
  • "优缺点分析"

Workflow

  1. Receive products to compare from user: Product A and Product B (or a category with multiple entries), with key specs, price points, target users, and any sponsored/editorial disclosure.
  2. Build a feature comparison matrix: list all comparable features across both products, note where data is missing.
  3. Generate balanced pros and cons for each product — a MINIMUM of 2 pros and 2 cons per product, even for the recommended one.
  4. Create "best for" recommendations based on user personas, not product superiority: "Product A is best for [persona/use case], Product B is best for [different persona/use case]."
  5. Apply the fairness gate: verify no invented weaknesses, no suppressed advantages, no defamatory language.
  6. Output the complete comparison package: feature table + pros/cons + buying recommendation + fairness disclosure.

Prompt Templates

1. Head-to-Head Comparison (head_to_head_comparison)

Purpose: Generate a structured A vs B comparison. Input:

  • ${product_a_name} — Product A name + key specs
  • ${product_b_name} — Product B name + key specs
  • ${comparison_focus} — What matters most (price/performance/quality/features/ecosystem)
  • ${disclosure} — Editorial or sponsored relationship

Output: Feature matrix table + balanced pros/cons per product + "best for" verdict + fairness disclosure.

2. Buying Guide (buying_guide)

Purpose: Create a tiered buying guide for a product category. Input:

  • ${category} — Product category (e.g., "noise-canceling headphones")
  • ${budget_tiers} — Price brackets with 1–2 products per tier
  • ${user_personas} — 2–3 buyer types and what they value

Output: Tiered guide: Budget Tier | Product(s) | Key Feature | Best For | Pros | Cons | Price.

3. Pros/Cons Generator (pros_cons_generator)

Purpose: Generate an objectively balanced pros/cons list for one product. Input:

  • ${product_name} — Product
  • ${product_details} — Full specs, price, user reviews context
  • ${use_case} — Intended usage context

Output: Pros list (minimum 3) and Cons list (minimum 2), each with a one-sentence explanation.

4. Spec Battle (spec_battle)

Purpose: Format raw specifications into a readable comparison. Input:

  • ${product_a_specs} — Structured spec list for Product A
  • ${product_b_specs} — Structured spec list for Product B
  • ${highlight_categories} — Which spec categories to emphasize

Output: Spec comparison table: Feature | Product A | Product B | Winner (if clear) | Note.

5. Best For Matcher (best_for_matcher)

Purpose: Match products to user personas with personalized recommendations. Input:

  • ${product_options} — 2–5 products in a category
  • ${user_persona} — One persona description (type, budget, priorities, constraints)

Output: Ranked recommendation: #1 pick with reasoning, runner-up, and "avoid if" note for each product.

Output Format

Every comparison is delivered in a reader-friendly structure:

Feature Comparison Table:

FeatureProduct AProduct BEdge
Price¥299¥399A
............

Pros & Cons:

  • Product A
    • ✅ Pro 1: ...
    • ❌ Con 1: ...
  • Product B (same structure)

Verdict: Best for [persona/use case] → [which product and why]

Fairness Disclosure: [Editorial/Sponsored/Data sources]

Safety Rules

  • NEVER invent or exaggerate a competitor's weakness — if data is missing, say "data not available"
  • NEVER suppress or omit a competitor's genuine advantage
  • NEVER use defamatory, dismissive, or insulting language about any product
  • NEVER present sponsored content as editorial — always label sponsorship
  • ALWAYS generate AT LEAST 2 cons for every product, even the recommended one
  • ALWAYS cite sources when using third-party data or reviews
  • ALWAYS provide a fairness disclosure section

Examples

Example 1: Head-to-Head (Smartphones)

Input: A="Phone X ¥2999 6.7in 5000mAh 64MP", B="Phone Y ¥3299 6.5in 4500mAh 108MP", Focus="camera+battery" Output: Feature table with 8 rows, A wins on battery/price, B wins on camera/resolution. Pros/cons for each (Phone X con: "lower camera resolution"; Phone Y con: "higher price, smaller battery"). Verdict: "Phone X best for budget-conscious battery users; Phone Y best for photography enthusiasts."

Example 2: Buying Guide

Input: Category="蓝牙耳机 (Bluetooth Earbuds)", Tiers=["入门<200", "中端200-500", "高端>500"], Personas=["通勤党", "运动党", "学生党"] Output: Three-tier guide with 5 products, each linked to a persona, with balanced pros/cons.

Related Skills

Comments

Loading comments...