Install
$ agentstack add skill-fjilvi-afk-growthlens-competitor-teardown ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Competitor Teardown
> Turn a competitor's website into a structured intelligence report: how they > position, what they sell, how they get customers, and where they're weak.
What it does
Produces a complete competitor profile from public information only. It reads the competitor's site the way a strategist would — homepage, product/pricing/about pages, blog, and footer — and reconstructs their positioning, offer, funnel, and go-to-market, then judges where they are strong and where they are exposed.
When to use this skill
- "Here's a competitor: — break them down."
- "Research for me."
- "How does position themselves / make money / get traffic?"
- Building a battlecard, a market map, or prepping a strategy session.
Inputs needed
- Required: the competitor's primary URL (homepage). If the user names a
company without a URL, find the official site first and confirm it.
- Helpful: the user's own product/positioning (to make the comparison
relevant), the market/niche, and any specific question ("focus on pricing").
- If you only have a brand name and can't confirm the official domain, ask.
Method
Work through the [teardown framework](references/teardown-framework.md) — the nine lenses below. For each, capture what's observable and flag what you're inferring.
- Snapshot — company, category, one-line "what they do", apparent stage/size
(team page, funding mentions, customer logos).
- Positioning — the promise in the hero section, the category they claim,
who they say it's for, and the primary differentiator they lean on.
- Target audience / ICP — who the copy speaks to; segments and roles named.
- Offer & value ladder — products/plans, lead magnets, free tier/trial,
core offer, upsells. Map the ladder from free → flagship.
- Pricing signals — published prices, packaging, billing terms, anchoring,
discounts. If pricing is hidden, note that and what it implies.
- Funnel & conversion path — the steps from landing to purchase; primary
CTA, friction, lead capture, demo/checkout flow.
- Acquisition channels — evidence of SEO (blog depth, topics), paid ads
(landing-page patterns, UTM hints), social, partnerships, affiliates.
- Social proof & trust — testimonials, case studies, logos, reviews,
guarantees, named results.
- Strengths & vulnerabilities — synthesize: what they do well, where the
gaps are, and where a challenger could attack.
Visit the most informative pages (home, product, pricing, about, a few blog posts). Don't speculate beyond what the site supports.
Output format
# Competitor Teardown —
## TL;DR
- 3–5 sharp takeaways (positioning, who they target, how they monetize, biggest weakness)
## 1. Snapshot
| Field | Finding |
|-------|---------|
| Category | |
| What they do | |
| Apparent stage/size | |
## 2. Positioning
- Hero promise:
- Category claimed:
- Primary differentiator:
## 3. Target audience / ICP
## 4. Offer & value ladder
## 5. Pricing signals
## 6. Funnel & conversion path
## 7. Acquisition channels
## 8. Social proof & trust
## 9. Strengths & vulnerabilities
| Strengths | Vulnerabilities (where to attack) |
|-----------|-----------------------------------|
## Strategic read
2–3 sentences: their apparent strategy and the single best opening against them.
Quality bar
- Mark every claim as observed (on the site) or inferred (your read).
- No invented metrics, funding, or headcount. "Not disclosed" is a valid answer.
- The "vulnerabilities" must be specific and actionable, not "could improve UX".
- Analyze the company, not its employees as individuals.
Common mistakes to avoid
- Summarizing the homepage instead of reconstructing the strategy.
- Treating marketing copy as fact (a claimed differentiator ≠ a real one).
- Ending with a list of features instead of a strategic read.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: fjilvvi
- Source: fjilvvi/growthlens
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.