amazon-competitor-radar
Skill0 starsChanged 3 months agoMITView on GitHub
Radar de concorrentes Amazon BR — get_market_pulse com alertas RED/YELLOW/GREEN. Monitora preco, BSR e reviews vs snapshot anterior. Use para monitorar preço, BSR e reviews vs o snapshot anterior.
In this repository24 other files it gives its agents.
- amazon-ads-keyword-target-builderSkill
- amazon-ads-launch-playbookSkill
- amazon-ads-optimizationSkill
- amazon-ads-reports-troubleshootingSkill
- amazon-adsSkill
- amazon-ads-write-recoverySkill
- amazon-dspSkill
- amazon-keyword-intelligenceSkill
- amazon-listing-auditSkill
- amazon-market-entrySkill
- amazon-mining-researchSkill
- amazon-pricing-signalsSkill
- amazon-reorder-planningSkill
- amazon-seller-centralSkill
- amazon-sp-campaign-launcherSkill
- bling-erpSkill
- fba-inventory-risk-dashboardSkill
- listing-create-publishSkill
- olist-tiny-erpSkill
- search-term-harvest-dashboardSkill
- super-listing-powerSkill
- titanos-ads-quickstartSkill
- titanos-mcp-setupSkill
- wasted-ad-spend-dashboardSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use esta skill quando o usuário / Use this skill when the user:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Amazon Competitor Radar — MCP Titanos
Quando usar / When to Use This Skill
Use esta skill quando o usuário / Use this skill when the user:
- Pergunta o que mudou no nicho (preço, BSR, reviews)
- Quer alertas de concorrentes RED/YELLOW/GREEN
- Precisa de market pulse vs um snapshot anterior
Skill para monitoramento operacional: "o que mudou no meu nicho?", "concorrente baixou preço?".
Scope: mining:search · Requer organização na API Key.
Tool principal
| Tool | Créditos | Função |
get_market_pulse | 100 | Diff vs último snapshot + alertas |
Setup (primeira execução)
{
"pais": "BR",
"asins": ["B0MEUASIN1", "B0CONCORR1", "B0CONCORR2"],
"label": "watchlist-garrafa-termica",
"salvar_snapshot": true
}Primeira run = baseline (alertas INFO). Segunda run em diante = diff real.
Alertas
| Nível | Exemplos |
| 🔴 RED | Preço -10%; BSR piora >50% |
| 🟡 YELLOW | Preço ±5–10%; BSR ±20–50%; novo player |
| 🟢 GREEN | BSR melhora; aceleração de reviews |
Automação (agente local)
Agendar daily:
get_market_pulse (mesmos ASINs, salvar_snapshot=true)
→ resumir alertas RED primeiro
→ sugerir get_pricing_signals nos ASINs própriosComplementos
get_market_overview— contexto de mercado semanalamazon-listing-audit— gap vs concorrentes na conta sellerAmazon-Ads— reação a movimentos de SERP/keywords
Pitfalls
- Máximo 20 ASINs por watchlist.
- Snapshots são por organização — keys da mesma org compartilham histórico.
- Não substitui alertas nativos Seller Central ou Ads.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

