Skip to content

JasonColapietro/suede-creator-skills / skills/suede-reverse-engineer-anyone

suede-reverse-engineer-anyone

Verified

Use 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).

references/watch-mode.md

View on GitHub
# Watch Mode

Once a teardown exists, rerun it monthly and report only what is new.

1. Re-run the stage 1 history checks, the stage 5 signals, the hiring boards, reviews, ad libraries, and paid promotion sweep, plus the industry section's checks, and pull the last month's posts and interviews. Append new dated moves to a fresh `moves.csv`.
2. Diff the new log against the last one:
   ```bash
   node <skill-dir>/scripts/timeline.mjs diff --old teardowns/<target>/moves-2026-10.csv --new teardowns/<target>/moves.csv --out teardowns/<target>/new-moves.csv
   ```
3. Report only meaningful new moves: a new ad network, page family, loop, pricing change, content format, hiring burst in one channel, or complaint theme. **Launch radar:** when two or more of these land within a few weeks (a new subdomain, a trademark filing, new job titles in one area, a sitemap jump, a new domain verification), flag a likely launch and say what it points to. Write "no new moves" when there are none, which is the usual result.
4. For each new move, say whether it changes a play and which skill takes it.

To schedule it, run it as the monthly watch loop in `suede-marketing-loops`, keeping the dated move logs as its state.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall