competitors

A set of methods for creating pages that compare a product with a competitor or present it as an alternative. These pages can support sales conversations and searches such as “Product A vs Product B.”

In plain words
What is it for?
Use it to plan competitor comparison pages, alternative pages, SEO content, honest positioning, and sales enablement material.
Why use it?
It helps prospective customers evaluate choices while keeping comparisons accurate and useful.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/patrickserrano/lacquer/competitors
Any agent
npx skills add patrickserrano/lacquer --skill competitors
Clone the repo
git clone --depth 1 https://github.com/patrickserrano/lacquer

Made for: Claude Code, Codex.

Per session 121 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,956 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00121 $0.01956
Opus 5 $0.00060 $0.00978
Sonnet 5 $0.00024 $0.00391
Haiku 4.5 $0.00012 $0.00196

Measured 2d ago against content hash 99e9ea715b1a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

competitors scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to competitors — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

core/skills/competitors/SKILL.md · 259 lines

How it starts

The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), 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:

  1. Your Product

    • Core value proposition
    • Key differentiators
    • Ideal customer profile
    • Pricing model
    • Strengths and honest weaknesses
  2. Competitive Landscape

    • Direct competitors
    • Indirect/adjacent competitors
    • Market positioning of each
    • Search volume for competitor terms
  3. Goals

    • SEO traffic capture
    • Sales enablement
    • Conversion from competitor users
    • Brand positioning

Core Principles

1. Honesty Builds Trust

  • Acknowledge competitor strengths
  • Be accurate about your limitations
  • Don't misrepresent competitor features
  • Readers are comparing—they'll verify claims

2. Depth Over Surface

  • Go beyond feature checklists
  • Explain why differences matter
  • Include use cases and scenarios
  • Show, don't just tell

3. Help Them Decide

  • Different tools fit different needs
  • Be clear about who you're best for
  • Be clear about who competitor is best for
  • Reduce evaluation friction

4. Modular Content Architecture

  • Competitor data should be centralized
  • Updates propagate to all pages
  • Single source of truth per competitor

Page Formats

Format 1: [Competitor] Alternative (Singular)

Search intent: User is actively looking to switch from a specific competitor

URL pattern: /alternatives/[competitor] or /[competitor]-alternative

Read the full file on GitHub · 259 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 259 lines · 121 tokens per session scan A 99e9ea715b1a

Subscribe to this mod's changes

competitors is a skill published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed 2d ago), licensed MIT. It adds 121 tokens to every session and 1,956 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to competitors, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

update-store

ストア情報の更新自動化 — スクリーンショット撮影(シミュレーター × モック画面 × Marionette MCP)とメタデータテキスト更新。ストア更新、スクショ更新、App Store / Google Play のメタデータ更新、リリースノート作成の際に使用すること。.

K9i-0/ccpocket · 80 tokens

aso-playbook

Beginner-friendly App Store Optimization guide covering keyword research, screenshot design, rating management, and A/B testing for iOS and Android. By @WeiYipei — practical ASO for indie developers and small teams.

Gingiris-1031/gingiris-skills · 48 tokens

appstore-ads-operator

Apple Ads campaigns: inspect and manage separate auth, orgs, ad groups, creatives, keywords, reports, and API calls; approve live mutations first.

Xopoko/build-swift-apps · 38 tokens

appstore-aso-auditor

App Store ASO audit: analyze canonical ./metadata offline after asc metadata pull; add Astro MCP keyword gaps and Apple app-tag context when available.

Xopoko/build-swift-apps · 40 tokens

appstore-metadata-localizer

App Store listing text: translate and market-adapt descriptions, keywords, What's New, names, subtitles, and privacy text across locales. Excludes non-translation edits, standalone release notes, and IAP/subscription names.

Xopoko/build-swift-apps · 52 tokens

gingiris-aso-growth

🇺🇸 ASO & Mobile App Growth Playbook 2026 — Complete App Store Optimization guide. ASO keyword ranking, App Store & Google Play listing optimization, app cold start, UGC creator operations, TikTok/Instagram/YouTube Shorts marketing, AI-matrix content scaling, mobile user acquisition. 🇨🇳 ASO 增长与 App 冷启动权威指南 …

Gingiris-1031/gingiris-skills · 320 tokens