Competitor Researcher
hanzili/hanzi-browse
Research SaaS and AI-tool competitors in a real browser. An agent skill from hanzili/hanzi-browse.
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.
Install Competitor Monitoring
$ npx skills add amplitude/builder-skills --skill competitor-monitoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install amplitude/builder-skills competitor-monitoring --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/amplitude/builder-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/product-skills/skills/competitor-monitoring .claude/skills/competitor-monitoring && 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 "competitor-monitoring" agent skill from https://github.com/amplitude/builder-skills/tree/main/product-skills/skills/competitor-monitoring into .claude/skills/competitor-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-monitoring", 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/amplitude/builder-skills/tree/main/product-skills/skills/competitor-monitoringType 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 amplitude/builder-skills --skill competitor-monitoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install amplitude/builder-skills competitor-monitoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amplitude/builder-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/product-skills/skills/competitor-monitoring .agents/skills/competitor-monitoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "competitor-monitoring" agent skill from https://github.com/amplitude/builder-skills/tree/main/product-skills/skills/competitor-monitoring into .agents/skills/competitor-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-monitoring", 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 amplitude/builder-skills --skill competitor-monitoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install amplitude/builder-skills competitor-monitoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amplitude/builder-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/product-skills/skills/competitor-monitoring .cursor/skills/competitor-monitoring && 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 "competitor-monitoring" agent skill from https://github.com/amplitude/builder-skills/tree/main/product-skills/skills/competitor-monitoring into .cursor/skills/competitor-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-monitoring", 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/amplitude/builder-skills.git --path product-skills/skills/competitor-monitoring--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 amplitude/builder-skills --skill competitor-monitoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install amplitude/builder-skills competitor-monitoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amplitude/builder-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/product-skills/skills/competitor-monitoring .gemini/skills/competitor-monitoring && 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 "competitor-monitoring" agent skill from https://github.com/amplitude/builder-skills/tree/main/product-skills/skills/competitor-monitoring into .gemini/skills/competitor-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-monitoring", 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 amplitude/builder-skills competitor-monitoringInstalls 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 amplitude/builder-skills --skill competitor-monitoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/amplitude/builder-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/product-skills/skills/competitor-monitoring .github/skills/competitor-monitoring && 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 "competitor-monitoring" agent skill from https://github.com/amplitude/builder-skills/tree/main/product-skills/skills/competitor-monitoring into .github/skills/competitor-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-monitoring", 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 amplitude/builder-skills --skill competitor-monitoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install amplitude/builder-skills competitor-monitoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amplitude/builder-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/product-skills/skills/competitor-monitoring .opencode/skills/competitor-monitoring && 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 "competitor-monitoring" agent skill from https://github.com/amplitude/builder-skills/tree/main/product-skills/skills/competitor-monitoring into .opencode/skills/competitor-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-monitoring", 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
competitor-monitoring- GitHub stars
- 159
- Token cost
- ~1k tokens
- SKILL.md length
- 209 words
- Files
- 1
- Skills in repo
- 61
- Repo updated
- First seen
- Licence
- None found
At a glance
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.
- A standing weekly competitive pulse
- SKILL.md covers Prompt Template, Setup, Placeholders to fill in and Tips
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- An on-demand deep-dive
What it does
Competitor Monitoring is an agent skill from 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. Use for a standing weekly competitive pulse or an on-demand deep-dive.
Its SKILL.md is about 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 Landing pages and Competitor analysis. It works with Google Drive and Model Context Protocol. The repository describes itself as: Open-source AI skills for product managers — battle-tested by PMs at Amplitude.
When your agent uses it
- A standing weekly competitive pulse
- An on-demand deep-dive
Example prompts
- “/competitor-monitoring”
What it can do on your machine
Read from SKILL.md and the folder at commit 51838c2. 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
Competitor Monitoring loads about 1k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 209 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 209 words (~1,016 tokens).
“A weekly competitive intelligence analyst — reads your competitor list, visits their sites, and writes you a report.”
- name
- competitor-monitoring
- suggest_when
- User says "competitor monitoring", "competitive intelligence", "what are competitors shipping", "competitive report", "track competitors", or wants to stay on…
Files
Just SKILL.md in product-skills/skills/competitor-monitoring of amplitude/builder-skills.
Open the folder on GitHubat commit 51838c2
Compare with similar skills
Competitor Monitoring 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 |
|---|---|---|---|---|---|---|
| Competitor Monitoring this skillamplitude/builder-skills | 159 | — | ~1k | Automated safety check: Pass | None | |
| Competitor Researcherhanzili/hanzi-browse | 177 | — | ~4.7k | Automated safety check: Pass | Custom licence | |
| Brand Kitcognyai/claude-code-marketing-skills | 104 | — | ~3.4k | Automated safety check: Notes | None | |
| Google Ads Landing ReviewTheMattBerman/google-ads-copilot | 238 | — | ~4.1k | Automated safety check: Pass | MIT | |
| 03 Performance Eval Globalminhnv0807/ai-business-skills | 609 | — | ~3.5k | Automated safety check: Pass | MIT | |
| SEO Competitor Pagesseranking/seo-skills | 161 | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
Brand Kit
cognyai/claude-code-marketing-skills
Build a portable brand-kit.json for the user's product — colors, typography, voice — that other skills (video, ad creative, landing page) can consume.
Google Ads Landing Review
TheMattBerman/google-ads-copilot
Diagnose landing page → conversion path problems for Google Ads traffic.
03 Performance Eval Global
minhnv0807/ai-business-skills
A skill your agent uses when marketing numbers look bad and the user needs to know WHY — layered root-cause diagnosis across tracking, delivery, creative, landing page, offer, and audience quality…
SEO Competitor Pages
seranking/seo-skills
Generate SEO-optimized "X vs Y" comparison and "alternatives to X" landing pages targeting comparative-intent keywords.
Screenshot Teardown
mohitagw15856/pm-claude-skills
Tear down a competitor's product from screenshots of its actual UI — onboarding, pricing page, core flows.
More from amplitude/builder-skills
All 61 skills in this repo7 Powers Analysis
amplitude/builder-skills
Analyzes a business, product or feature with Hamilton Helmer's 7 Powers framework to judge competitive advantage and how long it will last.
Amplitude Custom Agent Builder
amplitude/builder-skills
Helps an Amplitude user design a custom agent by proposing use cases that fit their role and data, shaping a spec, and returning a Global Agent link that builds it.
Good Strategy Bad Strategy Kernel
amplitude/builder-skills
Evaluates or drafts a strategy using Rumelt's kernel of diagnosis, guiding policy and coherent actions, to expose goal lists posing as strategy.
High Output Management Framework
amplitude/builder-skills
Applies Andy Grove's High Output Management ideas to diagnose where a team loses output and to design meetings, processes and management decisions.
Playing to Win Strategy
amplitude/builder-skills
Walks a team through Lafley and Martin's five-choice cascade to pin down where to compete and how to win there.
Amazon Working Backwards
amplitude/builder-skills
Write a PR/FAQ for a product idea using Amazon's Working Backwards process.
Related
Works with
Categories
Questions about Competitor Monitoring
What does Competitor Monitoring do?
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. Competitor Monitoring is an agent skill from 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.
When should I use Competitor Monitoring?
Competitor Monitoring fits situations like: A standing weekly competitive pulse; an on-demand deep-dive.
How do I install Competitor Monitoring in Claude Code?
Run `npx skills add amplitude/builder-skills --skill competitor-monitoring -a claude-code`. Or copy the skill folder (product-skills/skills/competitor-monitoring in amplitude/builder-skills) into .claude/skills/competitor-monitoring in your project. Claude Code loads it when a task matches its description.
How do I install Competitor Monitoring in Codex?
Run `npx skills add amplitude/builder-skills --skill competitor-monitoring -a codex`. Or copy the skill folder (product-skills/skills/competitor-monitoring in amplitude/builder-skills) into .agents/skills/competitor-monitoring in your project. Codex loads it when a task matches its description.
Can I use Competitor Monitoring 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 amplitude/builder-skills --skill competitor-monitoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/competitor-monitoring, .gemini/skills/competitor-monitoring, .github/skills/competitor-monitoring and .opencode/skills/competitor-monitoring in your project.
What does Competitor Monitoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Competitor Monitoring is instructions for the agent only.
Does Competitor Monitoring 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 Competitor Monitoring 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 Competitor Monitoring use?
No licence was found for Competitor Monitoring or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Competitor Monitoring use?
About 1k tokens (SKILL.md is roughly 4.1k 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 Competitor Monitoring?
Skills that share tags, products or a category with Competitor Monitoring: Competitor Researcher (hanzili/hanzi-browse, 177 stars), Brand Kit (cognyai/claude-code-marketing-skills, 104 stars), Google Ads Landing Review (TheMattBerman/google-ads-copilot, 238 stars) and 03 Performance Eval Global (minhnv0807/ai-business-skills, 609 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Competitor Monitoring?
amplitude (a GitHub organization) maintains it in amplitude/builder-skills, which has 159 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on July 24, 2026.
Source: amplitude/builder-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.