JasonColapietro/suede-creator-skills / skills/suede-reverse-engineer-anyone
suede-reverse-engineer-anyone
VerifiedUse when asked "how did X grow", "reverse engineer their marketing", "what made this artist blow up", or "map their funnel". Suede reverse-engineers any company, creator, artist, founder brand, app, or launch from dated public evidence: a one-source growth curve, a log of every move, funnel and content patterns, hidden signals, the user's gap, and ranked plays routed to the Suede skill that runs each one. NOT FOR: a current-state competitor snapshot (use suede-competitor-profiling), publishing comparison pages (use suede-competitors), or why one post traveled (use suede-social).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.9 KB |
| SKILL.md | skill md | 19.7 KB |
| agents/openai.yaml | config | 619 B |
| evals/evals.json | config | 6.2 KB |
| references/collector.md | markdown | 5.5 KB |
| references/common-mistakes.md | markdown | 1.3 KB |
| references/content-teardown.md | markdown | 6.3 KB |
| references/data-sources.md | markdown | 11.1 KB |
| references/funnel-hack.md | markdown | 6.2 KB |
| references/funnel-read.md | markdown | 2.8 KB |
| references/go-inside.md | markdown | 7.3 KB |
| references/hidden-signals.md | markdown | 9.9 KB |
| references/industry-signals.md | markdown | 34.5 KB |
| references/landscape.md | markdown | 4.8 KB |
| references/play-routing.md | markdown | 11.7 KB |
| references/playbook-template.md | markdown | 6.7 KB |
| references/target-types.md | markdown | 10.6 KB |
| references/team-voices.md | markdown | 5.0 KB |
| references/timeline-analysis.md | markdown | 5.4 KB |
| references/usage-contract.md | markdown | 1.8 KB |
| references/watch-mode.md | markdown | 1.2 KB |
| references/weak-spots.md | markdown | 6.4 KB |
| scripts/collect.mjs | script | 67.7 KB |
| scripts/tests/test_collect.mjs | script | 34.4 KB |
| scripts/tests/test_timeline.mjs | script | 11.5 KB |
| scripts/timeline.mjs | script | 24.2 KB |
references/weak-spots.md
View on GitHub# Where They're Weak
Stage 8's second half. Copying what worked is half of a teardown. The other half is finding where the target is losing: what its customers or fans complain about, what it stopped doing, and which audiences it ignores. Those gaps are where the user can win without outspending it.
## Contents
- Sources of weakness
- Mining complaints
- Reading the pattern
- Turning weak spots into plays
- Rules for using weak spots
---
## Sources of Weakness
| Weakness | Where to find it | Procedure |
|---|---|---|
| **What customers hate** | 1-2 star reviews on app stores, review sites, retailer pages, game store pages | Read or export to `reviews.csv` (`date,rating,source,title,text,link`), newest first |
| | Reddit, Hacker News, forums, and comment threads | `site:reddit.com "<target>" (slow OR expensive OR switched OR alternative OR cancel)` |
| | Regulated industries | Public complaint databases and regulator actions named in `industry-signals.md` |
| **Why people leave** | "Switched from X" and "X alternative" posts, migration guides, competitors' import tools | Search `"switched from <target>"`, `"<target> alternative"`, `"migrate from <target>"` |
| **Where support breaks** | Stage 3: response time, chat bot dead ends, cancel flow length | `go-inside.md`, with approval |
| **Price pain** | Price rises in the pricing history, price complaints in reviews, removed plans | Pricing captures from `hidden-signals.md` |
| **Search they gave up** | Page families that shrank or vanished, keywords where rank fell | Sitemap growth on Wayback; the SEO tool's lost keywords |
| **Markets they left or ignore** | Locales dropped from the sitemap, countries with no pages or jobs, segments with no landing page | Sitemap and job board history |
| **Slowing output** | Changelog, release, or posting cadence that dropped; a shrinking engineering hiring share | Changelog or release dates by month; job posts by function |
| **Weak AI answers** | Prompts where they're missing, named after the user, or described wrongly | The Stage 2 AI answer check |
| **Unhappy partners** | Low-rated integration listings, partners who removed them | Marketplace listings and their captures |
| **Fan friction (creators)** | Recurring complaints about ticket fees, merch quality, shipping, release delays, a sound change, paywalled content | Public comments and threads, read by theme. No names |
## Mining Complaints
1. Pull reviews or complaints from at least two sources, newest first, and note the date range each covers.
2. Count with code: low-star share by month, and terms that appear in a larger share of 1-2 star reviews than 4-5 star ones.
3. Read recent low reviews in full. Group them into themes in your own words: price, missing feature, bugs after an update, support, billing, onboarding, performance, shipping, fees.
4. For each theme, record the count, the share of low reviews, the first month it appears, and two short quotes with links (no names or handles).
5. Check whether a rise lines up with a dated move (a price change, a redesign, a big release). Add the spike to `moves.csv` as `kind: review-spike`.
**A theme needs 5 or more low reviews across more than one month to count.** One loud thread is an anecdote.
## Reading the Pattern
- **Complaints about a recent change** (a redesign, a price rise, a removed free plan) are the most usable: the unhappy customers are still deciding whether to leave.
- **Complaints that never change** (slow support for three years) are structural. The target has decided not to fix them, which makes them a lasting angle.
- **Complaints that come with growth** (outages, support wait times, sold-out shows) can mean the target is winning. Read them next to the curve before calling it weakness.
- **Praise inside low-star reviews** ("love the product, but the price doubled") shows what not to attack.
- **Who complains** matters more than how many: complaints from the segment the user serves outweigh the rest.
## Turning Weak Spots into Plays
| Weak spot | Play | Suede skill |
|---|---|---|
| A complaint theme the user solves | "Alternative to X for [the complaining segment]" page with the specific difference | `$suede-competitors` |
| Price pain after a price rise | A switching offer or migration help for their plan tier | `$suede-offers`, `$suede-pricing` |
| Customers leaving over a missing feature | Positioning that leads with that feature | `$suede-product-marketing`, `$suede-copy` |
| Searches on "[their brand] alternative" and "[their brand] [problem]" | Search ads and comparison pages on those queries, within trademark rules | `$suede-ads`, `$suede-competitors` |
| Support or onboarding complaints | Onboarding and support promises in the funnel, then proof | `$suede-onboarding`, `$suede-site-alchemy` |
| Search families they abandoned | Build the family they dropped, if demand is still there | `$suede-programmatic-seo`, `$suede-content-strategy` |
| Markets they left | Localized pages or a market launch | `$suede-site-alchemy`, `$suede-campaign-in-a-box` |
| Weak or wrong AI answers about them | Content that answers those prompts with the user's evidence | `$suede-ai-seo` |
| Sales objections the target can't answer | A battle card for the user's sales team | `$suede-sales-enablement` |
| Voice of customer in their reviews | Interview and survey prompts in the complainers' own words | `$suede-customer-research` |
| Fan friction on fees, merch, or release delays (creators) | A clearer direct offer: fair-fee presale, merch bundle, reliable release cadence | `$suede-offers`, `$suede-campaign-in-a-box` |
## Rules for Using Weak Spots
- **Attack the gap, not the target.** Write about what the user does better, with evidence. Don't publish their customers' complaints as if they were the user's findings.
- **Every comparative claim must be true, current, and provable.** Comparative advertising is lawful in the US and the EU only when accurate and not misleading. Date each claim and keep the source. Check with counsel before naming a competitor in paid ads.
- **Trademarks:** bidding on a competitor's name is allowed in many markets, but using it in ad text often isn't. Check each platform's trademark policy.
- **No personal data:** quote reviews without the reviewer's name or handle, and never contact reviewers, fans, or customers on the strength of a complaint.
- **Recheck before publishing.** A weakness from last year may be fixed. Re-read reviews and pricing before any page or ad goes live.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |