Competitor Monitoring
amplitude/builder-skills
Visit each competitor's homepage, features page, pricing page, and blog using Chrome MCP, then write a structured competitive intelligence report saved to Google Drive.
Tear down a competitor's product from screenshots of its actual UI — onboarding, pricing page, core flows.
Install Screenshot Teardown
$ npx skills add mohitagw15856/pm-claude-skills --skill screenshot-teardown -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills screenshot-teardown --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/screenshot-teardown .claude/skills/screenshot-teardown && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "screenshot-teardown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/screenshot-teardown into .claude/skills/screenshot-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "screenshot-teardown", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/screenshot-teardownType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill screenshot-teardown -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills screenshot-teardown --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/screenshot-teardown .agents/skills/screenshot-teardown && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "screenshot-teardown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/screenshot-teardown into .agents/skills/screenshot-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "screenshot-teardown", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill screenshot-teardown -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills screenshot-teardown --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/screenshot-teardown .cursor/skills/screenshot-teardown && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "screenshot-teardown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/screenshot-teardown into .cursor/skills/screenshot-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "screenshot-teardown", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/screenshot-teardown--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill screenshot-teardown -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills screenshot-teardown --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/screenshot-teardown .gemini/skills/screenshot-teardown && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "screenshot-teardown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/screenshot-teardown into .gemini/skills/screenshot-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "screenshot-teardown", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills screenshot-teardownInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill screenshot-teardown -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/screenshot-teardown .github/skills/screenshot-teardown && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "screenshot-teardown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/screenshot-teardown into .github/skills/screenshot-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "screenshot-teardown", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill screenshot-teardown -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills screenshot-teardown --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/screenshot-teardown .opencode/skills/screenshot-teardown && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "screenshot-teardown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/screenshot-teardown into .opencode/skills/screenshot-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "screenshot-teardown", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
screenshot-teardown- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 544 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Tear down a competitor's product from screenshots of its actual UI — onboarding, pricing page, core flows.
- Works in 6 steps: Anchor every claim to pixels. "Their… → Read the hierarchy, not just the… → Count the friction. Fields, steps,… → …
- Given screenshots of a rivals app
- SKILL.md covers What This Skill Produces, Required Inputs, Reading Method and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Screenshot Teardown is an agent skill from mohitagw15856/pm-claude-skills. Tear down a competitor's product from screenshots of its actual UI — onboarding, pricing page, core flows. Use when given screenshots of a rival's app or website and asked what they're doing, how their flow works, or what to learn/steal/avoid. Produces a UX-and-strategy teardown grounded in what is visibly on screen, with an inferences-vs-observations split. Requires image input. For a market-level teardown without screenshots use competitor-teardown.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Competitor analysis and Landing pages. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Given screenshots of a rivals app
- Website and asked what theyre doing
- How their flow works
- What to learn/steal/avoid
Example prompts
- “s app or website and asked what they”
- “/screenshot-teardown”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Anchor every claim to pixels. "Their onboarding asks for a credit card at step 1" — only if the screenshot shows it. Cite which screenshot…
- Read the hierarchy, not just the content. What's biggest, first, pre-selected, and colourful is what they want used; what's behind a…
- Count the friction. Fields, steps, decisions, permission asks — visible effort before value is a measurable choice.
- Read the copy as positioning. Button labels, empty states, and upgrade nags reveal the audience and the monetisation pressure better than…
- Separate the two registers strictly
- Mind the screenshot's limits. One user's session, one plan tier, one moment. Note what state the shots can't show (A/B variants, other…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Screenshot Teardown loads about 1.1k tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 544 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 544 words, ~1,117 tokens.
Download SKILL.mdSave it as
.claude/skills/screenshot-teardown/SKILL.md (or your agent's skills folder).- name
- screenshot-teardown
- description
- Tear down a competitor's product from screenshots of its actual UI — onboarding, pricing page, core flows. Use when given screenshots of a rival's app or website and asked what they're doing, how their flow works, or what to learn/steal/avoid. Produces a UX-and-strategy teardown grounded in what is visibly on screen, with an inferences-vs-observations split. Requires image input. For a market-level teardown without screenshots use competitor-teardown.
Screenshot Teardown Skill
Marketing pages say what a competitor claims; screenshots show what they shipped. This skill reads real UI evidence — layout, copy, defaults, friction, what's promoted and what's buried — and turns it into competitive insight you can defend, because every claim points at pixels.
What This Skill Produces
- A screen-by-screen read: what each screenshot shows, what the design is optimising for, where the friction is
- Strategic inferences — pricing/packaging signals, target-user signals, maturity signals — each labelled as inference and tied to its visual evidence
- Learn / steal / avoid recommendations for your own product
Required Inputs
- The screenshots (up to ~5 per pass; more → ask which flow matters most). If none attached, ask — never tear down from memory of the product.
- Your product and angle (ask if missing): who's analysing, and for what decision (pricing? onboarding redesign? battlecard?)
Reading Method
- Anchor every claim to pixels. "Their onboarding asks for a credit card at step 1" — only if the screenshot shows it. Cite which screenshot each observation comes from.
- Read the hierarchy, not just the content. What's biggest, first, pre-selected, and colourful is what they want used; what's behind a "More" menu is what they don't. Defaults are strategy.
- Count the friction. Fields, steps, decisions, permission asks — visible effort before value is a measurable choice.
- Read the copy as positioning. Button labels, empty states, and upgrade nags reveal the audience and the monetisation pressure better than their homepage does.
- Separate the two registers strictly:
- Observed — on screen, citable
- Inferred — a reading of intent ("the pre-selected annual plan suggests LTV pressure"), always labelled
[inference]
- Mind the screenshot's limits. One user's session, one plan tier, one moment. Note what state the shots can't show (A/B variants, other tiers, mobile vs desktop).
Output Format
Show full SKILL.md (250 more words)Show less
Screenshot teardown: [competitor] — [flow examined]
Evidence base: [n] screenshots of [what], captured [date if known]. What this evidence can't show: [limits].
Screen-by-screen: [#1 — screen name] — Shows: [observed]. Optimised for: [read]. Friction: [count/notes]. Notable copy: "[verbatim]".
What they're optimising for overall: [2-3 lines synthesising the design intent]
Strategic signals:
| Signal | Evidence (screenshot #) | Observed / Inference |
|---|
For us — learn / steal / avoid:
- Learn: [pattern worth understanding]
- Steal: [specific, adaptable pattern — with what to change]
- Avoid: [their visible mistake and why we think it's one]
Quality Checks
- Every observation cites its screenshot; every inference is labelled
[inference] - Copy is quoted verbatim where it carries the point, not paraphrased
- The friction count is actual (fields/steps visible), not vibes
- The teardown states what the screenshots cannot show
- Recommendations name what to change when stealing a pattern — context transplants fail
Anti-Patterns
- Do not analyse a product from training-data memory when screenshots are provided — the pixels are the source of truth, and the product has probably changed
- Do not proceed without images — that's
competitor-teardown's job - Do not present inferences as facts — "they're struggling with churn" is a reading, not a screenshot
- Do not sneer — "cluttered" is not analysis; name what the clutter costs and whom it serves
- Do not extrapolate a whole strategy from one screen — say when the evidence is thin
Example Trigger Phrases
- "Tear down this competitor's onboarding from these screenshots."
- "How does their flow work?"
- "What should we learn, steal or avoid from their pricing page?"
- "Here are screenshots of their app: what are they doing?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/screenshot-teardown of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Screenshot Teardown next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Screenshot Teardown this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Competitor Monitoringamplitude/builder-skills | 159 | — | ~1k | Automated safety check: Pass | None | |
| SEO Competitor Pagesseranking/seo-skills | 161 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Competitor Teardownirinabuht12-oss/marketing-skills | 4.1k | — | ~1.6k | Automated safety check: Pass | None | |
| Competitor Alternativesfreekmurze/dotfiles | 1k | 24 repos | ~2k | Automated safety check: Pass | None | |
| Competitor Researcherhanzili/hanzi-browse | 177 | — | ~4.7k | Automated safety check: Pass | Custom licence |
Similar skills
SEO Competitor Pages
seranking/seo-skills
Generate SEO-optimized "X vs Y" comparison and "alternatives to X" landing pages targeting comparative-intent keywords.
Competitor Teardown
irinabuht12-oss/marketing-skills
Systematic competitive analysis covering positioning, messaging hierarchy, objection handling, and CTA strategy from landing page URLs or screenshots.
Competitor Alternatives
freekmurze/dotfiles
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.
Competitor Researcher
hanzili/hanzi-browse
Research SaaS and AI-tool competitors in a real browser. An agent skill from hanzili/hanzi-browse.
Landing Page GTM Copy
ooiyeefei/ccc
Builds or rewrites SaaS landing pages by researching the real product, positioning it against alternatives and writing buyer-focused copy, then implementing it in the codebase.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Screenshot Teardown
What does Screenshot Teardown do?
Tear down a competitor's product from screenshots of its actual UI — onboarding, pricing page, core flows. Screenshot Teardown is an agent skill from mohitagw15856/pm-claude-skills. Tear down a competitor's product from screenshots of its actual UI — onboarding, pricing page, core flows.
When should I use Screenshot Teardown?
Screenshot Teardown fits situations like: given screenshots of a rivals app; website and asked what theyre doing; how their flow works; what to learn/steal/avoid.
How do I install Screenshot Teardown in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill screenshot-teardown -a claude-code`. Or copy the skill folder (skills/screenshot-teardown in mohitagw15856/pm-claude-skills) into .claude/skills/screenshot-teardown in your project. Claude Code loads it when a task matches its description.
How do I install Screenshot Teardown in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill screenshot-teardown -a codex`. Or copy the skill folder (skills/screenshot-teardown in mohitagw15856/pm-claude-skills) into .agents/skills/screenshot-teardown in your project. Codex loads it when a task matches its description.
Can I use Screenshot Teardown in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill screenshot-teardown -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/screenshot-teardown, .gemini/skills/screenshot-teardown, .github/skills/screenshot-teardown and .opencode/skills/screenshot-teardown in your project.
What does Screenshot Teardown need to run?
SKILL.md names no scripts, command-line tools or credentials: Screenshot Teardown is instructions for the agent only.
Does Screenshot Teardown access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Screenshot Teardown safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Screenshot Teardown use?
Screenshot Teardown is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Screenshot Teardown use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Screenshot Teardown?
Skills that share tags, products or a category with Screenshot Teardown: Competitor Monitoring (amplitude/builder-skills, 159 stars), SEO Competitor Pages (seranking/seo-skills, 161 stars), Competitor Teardown (irinabuht12-oss/marketing-skills, 4.1k stars) and Competitor Alternatives (freekmurze/dotfiles, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Screenshot Teardown?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.