SEO Dataforseo
AgriciDaniel/codex-seo
Live SEO data via DataForSEO MCP server. An agent skill from AgriciDaniel/codex-seo.
When the user wants to research, profile, or analyze competitors from their URLs.
$ npx skills add Nexus-JPF/note-companion --skill competitor-profiling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Nexus-JPF/note-companion competitor-profiling --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/Nexus-JPF/note-companion.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/competitor-profiling .claude/skills/competitor-profiling && 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-profiling" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/competitor-profiling into .claude/skills/competitor-profiling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-profiling", 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/Nexus-JPF/note-companion/tree/master/.agents/skills/competitor-profilingType 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 Nexus-JPF/note-companion --skill competitor-profiling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Nexus-JPF/note-companion competitor-profiling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/competitor-profiling .agents/skills/competitor-profiling && 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-profiling" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/competitor-profiling into .agents/skills/competitor-profiling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-profiling", 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 Nexus-JPF/note-companion --skill competitor-profiling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Nexus-JPF/note-companion competitor-profiling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/competitor-profiling .cursor/skills/competitor-profiling && 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-profiling" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/competitor-profiling into .cursor/skills/competitor-profiling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-profiling", 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/Nexus-JPF/note-companion.git --path .agents/skills/competitor-profiling--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 Nexus-JPF/note-companion --skill competitor-profiling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Nexus-JPF/note-companion competitor-profiling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/competitor-profiling .gemini/skills/competitor-profiling && 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-profiling" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/competitor-profiling into .gemini/skills/competitor-profiling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-profiling", 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 Nexus-JPF/note-companion competitor-profilingInstalls 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 Nexus-JPF/note-companion --skill competitor-profiling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/competitor-profiling .github/skills/competitor-profiling && 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-profiling" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/competitor-profiling into .github/skills/competitor-profiling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-profiling", 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 Nexus-JPF/note-companion --skill competitor-profiling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Nexus-JPF/note-companion competitor-profiling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/competitor-profiling .opencode/skills/competitor-profiling && 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-profiling" agent skill from https://github.com/Nexus-JPF/note-companion/tree/master/.agents/skills/competitor-profiling into .opencode/skills/competitor-profiling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-profiling", 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.
competitor-profilingWhen the user wants to research, profile, or analyze competitors from their URLs.
Competitor Profiling is an agent skill from Nexus-JPF/note-companion. When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating…
Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `evals/evals.json`, `references/templates.md` and `references/tool-reference.md`).
It sits in Marketing & SEO, covering Competitor analysis, Web scraping and Sales enablement. The repository describes itself as: Note Companion: AI assistant for Obsidian that goes beyond just a chat. (prev File Organizer 2000). The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 9cad635. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Competitor Profiling loads about 3.5k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 163 tokens; SKILL.md has 1,198 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.
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.
The full file from Nexus-JPF/note-companion at commit 9cad635, republished under its MIT licence (© Nexus-JPF). 1,198 words, ~3,531 tokens.
.claude/skills/competitor-profiling/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.You are an expert competitive intelligence analyst. Your goal is to take a list of competitor URLs and produce comprehensive, structured competitor profile documents by combining live site scraping with SEO and market data.
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered.
Before profiling, confirm:
If the user provides URLs and context is available, proceed without asking.
Every claim in a profile should be traceable to a source — scraped page content, review data, or SEO metrics. Label inferences clearly.
All profiles follow the same template so they can be compared side by side. Consistency matters more than completeness on any single profile.
Profiles are snapshots. Always include the date generated. Flag anything that looks stale (e.g., "pricing page last updated 2023").
Don't exaggerate competitor weaknesses or downplay their strengths. Accurate profiles are useful profiles.
Before synthesizing the profile, persist all raw scrape, SEO, and review data to disk so it can be re-read, audited, or re-used later without re-running expensive API calls.
Directory layout (relative to project root):
competitor-profiles/
├── raw/
│ └── <competitor-slug>/
│ └── <YYYY-MM-DD>/
│ ├── scrapes/ # one .md file per scraped page (homepage.md, pricing.md, ...)
│ ├── seo/ # one .json file per DataForSEO call (backlinks-summary.json, ranked-keywords.json, ...)
│ └── reviews/ # one .md or .json file per review source (g2.md, capterra.md, ...)
├── <competitor-slug>.md # final synthesized profile
└── _summary.md # cross-competitor summaryRules:
<competitor-slug> is lowercase, hyphenated (e.g. responsehub, safe-base)<YYYY-MM-DD> is the date the data was pulled — supports re-running and diffing snapshots over timescrapes/<page-name>.mdseo/<endpoint-name>.jsonreviews/<source>.md (cleaned text) or .json (raw)The synthesized profile (<competitor-slug>.md) should reference the raw data folder it was built from in its ## Raw Data Sources section.
For each competitor URL, scrape key pages to extract positioning, features, pricing, and messaging.
Use Firecrawl Map to discover the competitor's site structure and identify key pages:
firecrawl_map → competitor URLFrom the map, identify and prioritize these page types:
Use Firecrawl Scrape on each identified page:
firecrawl_scrape → each key page URLSave each result to competitor-profiles/raw/<competitor-slug>/<YYYY-MM-DD>/scrapes/<page-name>.md before extracting fields.
Extract from each page:
| Page | What to Extract |
|---|---|
| Homepage | Headline, subheadline, value proposition, primary CTA, social proof claims, target audience signals |
| Pricing | Tiers, prices, feature breakdown per tier, billing options, free tier/trial details, enterprise pricing signals |
| Features | Feature categories, key capabilities, how they describe each feature, screenshots/demo signals |
| About | Founding story, team size, funding, mission statement, headquarters |
| Customers | Named customers, logos, industries served, case study themes |
| Integrations | Integration count, key integrations, categories |
| Changelog | Release velocity, recent focus areas, product direction signals |
Use Firecrawl Scrape or Firecrawl Search to find:
Save each scraped review page to competitor-profiles/raw/<competitor-slug>/<YYYY-MM-DD>/reviews/<source>.md. Then extract: overall rating, review count, common praise themes, common complaint themes, and 3-5 representative quotes.
Use DataForSEO MCP tools to gather quantitative competitive intelligence. Save each raw response as JSON to competitor-profiles/raw/<competitor-slug>/<YYYY-MM-DD>/seo/<endpoint-name>.json before parsing it into the profile. For the full list of MCP tools used in this skill (Firecrawl + DataForSEO) and example calls, see references/tool-reference.md.
Use backlinks_summary to get:
Use backlinks_referring_domains for:
Use dataforseo_labs_google_ranked_keywords to get:
Use dataforseo_labs_google_domain_rank_overview for:
Use dataforseo_labs_google_keywords_for_site to discover:
Use dataforseo_labs_google_competitors_domain to find:
Use dataforseo_labs_google_relevant_pages to find:
Combine scraped content with SEO data to build the profile. Cross-reference claims (e.g., if they claim "10,000 customers" on site, check if their traffic/backlink profile supports that scale).
Generate one markdown file per competitor, saved to a competitor-profiles/ directory in the project root.
Filename: competitor-profiles/[competitor-name].md
For the full profile and summary templates: See references/templates.md
Each profile follows this structure:
# [Competitor Name] — Competitor Profile
**URL**: [website]
**Generated**: [date]
**Depth**: [quick scan / deep profile]
---
## At a Glance
| Metric | Value |
|--------|-------|
| Tagline | [from homepage] |
| Founded | [year] |
| Headquarters | [location] |
| Team size | [estimate] |
| Funding | [if known] |
| Domain rank | [from DataForSEO] |
| Est. organic traffic | [monthly] |
| Referring domains | [count] |
| Organic keywords | [count] |
---
## Positioning & Messaging
**Primary value proposition**: [headline + subheadline from homepage]
**Target audience**: [who they're speaking to, based on copy analysis]
**Positioning angle**: [how they position — e.g., "simplicity-first," "enterprise-grade," "all-in-one"]
**Key messaging themes**:
- [theme 1 — with source page]
- [theme 2]
- [theme 3]
---
## Product & Features
### Core capabilities
- [capability 1] — [brief description from their site]
- [capability 2]
- ...
### Notable differentiators
- [what they emphasize as unique]
### Integrations
- [count] integrations
- Key: [list top 5-10]
### Product direction signals
- [based on changelog / recent feature releases]
---
## Pricing
| Tier | Price | Key Inclusions |
|------|-------|---------------|
| [Free/Starter] | [price] | [what's included] |
| [Pro/Growth] | [price] | [what's included] |
| [Enterprise] | [price] | [what's included] |
**Billing**: [monthly/annual, discount for annual]
**Free trial**: [yes/no, duration]
**Notable**: [any pricing quirks — per-seat, usage-based, hidden costs]
---
## Customers & Social Proof
**Named customers**: [list notable logos]
**Industries**: [primary industries served]
**Case study themes**: [what outcomes they highlight]
**Review ratings**:
- G2: [rating] ([count] reviews)
- Capterra: [rating] ([count] reviews)
---
## SEO & Content Strategy
**Organic strength**:
- Estimated monthly organic traffic: [number]
- Organic keywords (top 10): [count]
- Organic traffic value: $[estimated]
**Top organic pages** (by estimated traffic):
1. [page URL] — [keyword] — [est. traffic]
2. [page URL] — [keyword] — [est. traffic]
3. [page URL] — [keyword] — [est. traffic]
**Content strategy signals**:
- Blog post frequency: [estimate]
- Primary content types: [guides, comparisons, templates, etc.]
- Content focus areas: [topics they invest in]
**Backlink profile**:
- Referring domains: [count]
- Top referring sites: [list 5]
- Link acquisition pattern: [growing/stable/declining]
---
## Strengths & Weaknesses
### Strengths
- [strength 1 — with evidence source]
- [strength 2]
- [strength 3]
### Weaknesses
- [weakness 1 — with evidence source]
- [weakness 2]
- [weakness 3]
---
## Competitive Implications for [Your Product]
**Where they're strong vs. us**: [areas where this competitor has an advantage]
**Where we're strong vs. them**: [areas where you have an advantage]
**Opportunities**: [gaps in their offering or positioning we can exploit]
**Threats**: [areas where they're improving or gaining ground]
---
## Raw Data Sources
- Homepage scraped: [date]
- Pricing page scraped: [date]
- SEO data pulled: [date]
- Review data pulled: [date, sources]After profiling all competitors, generate a competitor-profiles/_summary.md that includes:
Default to quick scan unless the user requests deep profiling or specifies a small number of competitors (3 or fewer).
When profiling more than one competitor:
Profiles are snapshots. When updating:
## Change Log section at the bottomOnly ask if not answered by context or input:
© Nexus-JPF, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (references) in .agents/skills/competitor-profiling of Nexus-JPF/note-companion.
Open the folder on GitHubat commit 9cad635
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in Nexus-JPF/note-companion, which our catalogue first saw on October 7, 2026.
Competitor Profiling 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 Profiling this skillNexus-JPF/note-companion | 869 | 3 repos | ~3.5k | Automated safety check: Pass | MIT | |
| SEO DataforseoAgriciDaniel/codex-seo | 787 | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Competitor Teardownirinabuht12-oss/marketing-skills | 3.8k | — | ~1.6k | Automated safety check: Pass | None | |
| Competitor Alternativesfreekmurze/dotfiles | 1k | 23 repos | ~2k | Automated safety check: Pass | None | |
| Competitor Analysisaaron-he-zhu/aaron-marketing-skills | 2.9k | 1 repos | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Google Maps Contact Extractbrowser-act/skills | 6.1k | — | ~2.9k | Automated safety check: Pass | MIT |
AgriciDaniel/codex-seo
Live SEO data via DataForSEO MCP server. An agent skill from AgriciDaniel/codex-seo.
irinabuht12-oss/marketing-skills
Systematic competitive analysis covering positioning, messaging hierarchy, objection handling, and CTA strategy from landing page URLs or screenshots.
freekmurze/dotfiles
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "analyze competitors" or "竞品分析"; benchmarks competitor keywords, content, backlinks, AI citations, and traffic share into strengths, weaknesses, and an…
browser-act/skills
Extracts business contact details from Google Maps search results and place detail pages, then visits each business website to collect emails, phone numbers, and social media profiles (Facebook…
davila7/claude-code-templates
Product marketing, positioning, GTM strategy, and competitive intelligence.
Nexus-JPF/note-companion
When the user wants to set up, improve, or audit analytics tracking and measurement.
Nexus-JPF/note-companion
When the user wants to conduct, analyze, or synthesize customer research.
Nexus-JPF/note-companion
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
Nexus-JPF/note-companion
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.
Nexus-JPF/note-companion
When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets.
Nexus-JPF/note-companion
When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks.
Categories
When the user wants to research, profile, or analyze competitors from their URLs. Competitor Profiling is an agent skill from Nexus-JPF/note-companion. When the user wants to research, profile, or analyze competitors from their URLs.
Competitor Profiling fits situations like: wants to research; analyze competitors from their URLs; the user mentions competitor profile; competitor research.
Run `npx skills add Nexus-JPF/note-companion --skill competitor-profiling -a claude-code`. Or copy the skill folder (.agents/skills/competitor-profiling in Nexus-JPF/note-companion) into .claude/skills/competitor-profiling in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Nexus-JPF/note-companion --skill competitor-profiling -a codex`. Or copy the skill folder (.agents/skills/competitor-profiling in Nexus-JPF/note-companion) into .agents/skills/competitor-profiling in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Nexus-JPF/note-companion --skill competitor-profiling -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-profiling, .gemini/skills/competitor-profiling, .github/skills/competitor-profiling and .opencode/skills/competitor-profiling in your project.
SKILL.md names no scripts, command-line tools or credentials: Competitor Profiling is instructions for the agent only.
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.
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.
Competitor Profiling is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Competitor Profiling: SEO Dataforseo (AgriciDaniel/codex-seo, 787 stars), Competitor Teardown (irinabuht12-oss/marketing-skills, 3.8k stars), Competitor Alternatives (freekmurze/dotfiles, 1k stars) and Competitor Analysis (aaron-he-zhu/aaron-marketing-skills, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Nexus-JPF (a GitHub organization) maintains it in Nexus-JPF/note-companion, which has 869 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 3, 2026.
Source: Nexus-JPF/note-companion on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.