Agent skill

Competitor Profiling

by Nexus-JPF in Nexus-JPF/note-companion

When the user wants to research, profile, or analyze competitors from their URLs.

MITAuto-check passedMarketing & SEO

Install Competitor Profiling

skills CLI
$ npx skills add Nexus-JPF/note-companion --skill competitor-profiling -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Nexus-JPF/note-companion competitor-profiling --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
competitor-profiling
GitHub stars
869
Used in
3 other repos
Token cost
~3.5k tokens
SKILL.md length
1,198 words
Files
4 (incl. references)
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to research, profile, or analyze competitors from their URLs.

  • Works in 7 steps: Facts Over Opinions → Structured and Comparable → Current Data → …
  • Wants to research
  • SKILL.md covers Initial Assessment, Core Principles, Saving Raw Data and Research Process, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

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.

When your agent uses it

  • Wants to research
  • Analyze competitors from their URLs
  • The user mentions competitor profile
  • Competitor research

Example prompts

  • “competitor profile,”
  • “competitor research,”
  • “competitor analysis,”
  • “/competitor-profiling”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Facts Over Opinions
  2. Structured and Comparable
  3. Current Data
  4. Honest Assessment
  5. Site Scraping (Firecrawl)
  6. SEO & Market Data (DataForSEO)
  7. Synthesis

What it can do on your machine

Read from SKILL.md and the folder at commit 9cad635. 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 (its code samples are markdown).

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

Always · name and description, kept in context so the agent knows when to use it
~163
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.5k

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 Nexus-JPF/note-companion at commit 9cad635, republished under its MIT licence (© Nexus-JPF). 1,198 words, ~3,531 tokens.

Download SKILL.mdSave it as .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.
name
competitor-profiling
description
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 comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
metadata.version
2.0.0

Competitor Profiling

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.

Initial Assessment

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:

  1. Competitor URLs — the list of competitor website URLs to profile
  2. Your product — what you do (if not in product marketing context)
  3. Depth level — quick scan (key facts only) or deep profile (full research)
  4. Focus areas — any specific dimensions to prioritize (e.g., pricing, positioning, SEO strength, content strategy)

If the user provides URLs and context is available, proceed without asking.


Core Principles

1. Facts Over Opinions

Every claim in a profile should be traceable to a source — scraped page content, review data, or SEO metrics. Label inferences clearly.

2. Structured and Comparable

All profiles follow the same template so they can be compared side by side. Consistency matters more than completeness on any single profile.

3. Current Data

Profiles are snapshots. Always include the date generated. Flag anything that looks stale (e.g., "pricing page last updated 2023").

4. Honest Assessment

Don't exaggerate competitor weaknesses or downplay their strengths. Accurate profiles are useful profiles.


Saving Raw Data

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 summary

Rules:

  • <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 time
  • Save each Firecrawl scrape as raw markdown to scrapes/<page-name>.md
  • Save each DataForSEO response as raw JSON to seo/<endpoint-name>.json
  • Save each review source to reviews/<source>.md (cleaned text) or .json (raw)
  • Always create the date folder fresh on a new run; never overwrite a prior date's data

The synthesized profile (<competitor-slug>.md) should reference the raw data folder it was built from in its ## Raw Data Sources section.


Research Process

Phase 1: Site Scraping (Firecrawl)

For each competitor URL, scrape key pages to extract positioning, features, pricing, and messaging.

Step 1: Map the site

Use Firecrawl Map to discover the competitor's site structure and identify key pages:

firecrawl_map → competitor URL

From the map, identify and prioritize these page types:

  • Homepage
  • Pricing page
  • Features / product pages
  • About / company page
  • Blog (top-level, for content strategy signals)
  • Customers / case studies page
  • Integrations page
  • Changelog / what's new (if exists)
Step 2: Scrape key pages

Use Firecrawl Scrape on each identified page:

firecrawl_scrape → each key page URL

Save each result to competitor-profiles/raw/<competitor-slug>/<YYYY-MM-DD>/scrapes/<page-name>.md before extracting fields.

Extract from each page:

PageWhat to Extract
HomepageHeadline, subheadline, value proposition, primary CTA, social proof claims, target audience signals
PricingTiers, prices, feature breakdown per tier, billing options, free tier/trial details, enterprise pricing signals
FeaturesFeature categories, key capabilities, how they describe each feature, screenshots/demo signals
AboutFounding story, team size, funding, mission statement, headquarters
CustomersNamed customers, logos, industries served, case study themes
IntegrationsIntegration count, key integrations, categories
ChangelogRelease velocity, recent focus areas, product direction signals
Step 3: Scrape competitor reviews (optional but high-value)

Use Firecrawl Scrape or Firecrawl Search to find:

  • G2 reviews page for the competitor
  • Capterra reviews page
  • Product Hunt launch page
  • TrustRadius profile

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.


Phase 2: SEO & Market Data (DataForSEO)

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:

  • Domain rank / authority score
  • Total backlinks
  • Referring domains count
  • Spam score

Use backlinks_referring_domains for:

  • Top referring domains (quality signals)
  • Link acquisition patterns
Keyword & Traffic Intelligence

Use dataforseo_labs_google_ranked_keywords to get:

  • Total organic keywords ranking
  • Keywords in top 3, top 10, top 100
  • Estimated organic traffic

Use dataforseo_labs_google_domain_rank_overview for:

  • Domain-level organic metrics
  • Estimated traffic value
  • Top keywords by traffic

Use dataforseo_labs_google_keywords_for_site to discover:

  • What keywords they target
  • Content gaps vs. your site
Show full SKILL.md (488 more words)Show less
Competitive Positioning Data

Use dataforseo_labs_google_competitors_domain to find:

  • Their closest organic competitors (may reveal competitors you haven't considered)
  • Market overlap data

Use dataforseo_labs_google_relevant_pages to find:

  • Their highest-traffic pages
  • Content that drives the most organic value

Phase 3: Synthesis

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


Output Format

Profile Document Structure

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:

markdown
# [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]

Summary Document

After profiling all competitors, generate a competitor-profiles/_summary.md that includes:

  1. Competitor landscape overview — one paragraph summarizing the competitive field
  2. Comparison table — key metrics side by side for all profiled competitors
  3. Positioning map — where each competitor sits (e.g., simple↔complex, cheap↔premium)
  4. Key takeaways — 3-5 strategic observations from the research
  5. Gaps and opportunities — where the market is underserved

Quick Scan vs. Deep Profile

Quick Scan (faster, lower cost)
  • Scrape: homepage + pricing page only
  • SEO: domain rank overview + ranked keywords summary
  • Skip: reviews, technology stack, backlink details
  • Output: abbreviated profile (At a Glance + Positioning + Pricing + SEO summary)
Deep Profile (comprehensive)
  • Scrape: all key pages + review sites
  • SEO: full backlink analysis + keyword intelligence + competitor discovery
  • Include: technology stack, content strategy analysis, review mining
  • Output: full profile template

Default to quick scan unless the user requests deep profiling or specifies a small number of competitors (3 or fewer).


Handling Multiple Competitors

When profiling more than one competitor:

  1. Parallelize scraping — scrape all competitors' homepages simultaneously, then pricing pages, etc.
  2. Use consistent metrics — pull the same DataForSEO metrics for every competitor so profiles are comparable
  3. Build the summary last — after all individual profiles are complete
  4. Prioritize by relevance — if the user has 10+ competitors, suggest profiling the top 5 first based on domain overlap or market similarity

Updating Profiles

Profiles are snapshots. When updating:

  • Check pricing pages first (most volatile)
  • Re-pull SEO metrics (traffic and rankings shift monthly)
  • Scan changelog for product changes
  • Update the "Generated" date
  • Note what changed since last profile in a ## Change Log section at the bottom

Task-Specific Questions

Only ask if not answered by context or input:

  1. What competitor URLs should I profile?
  2. Quick scan or deep profile?
  3. Any specific dimensions to focus on (pricing, SEO, positioning)?
  4. Should I compare findings against your product?

  • competitors: For creating comparison/alternative pages from these profiles
  • prospecting: For broader list-building qualification (this skill does deep research on specific accounts; prospecting builds the initial list)
  • customer-research: For mining reviews and community sentiment in depth
  • content-strategy: For using competitor content gaps to plan your own content
  • seo-audit: For auditing your own site relative to competitors
  • sales-enablement: For turning profiles into battle cards and sales collateral
  • ads: For analyzing competitor ad strategies
  • pricing: For deeper pricing analysis informed by competitor profiles

© 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

Files

SKILL.md and 3 other files (references) in .agents/skills/competitor-profiling of Nexus-JPF/note-companion.

  • SKILL.md
  • evals/evals.json
  • references/templates.md
  • references/tool-reference.md

Open the folder on GitHubat commit 9cad635

Used in 3 other repositories

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.

Compare with similar skills

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.

Competitor Profiling compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Competitor Profiling this skillNexus-JPF/note-companion8693 repos~3.5kAutomated safety check: PassMIT
SEO DataforseoAgriciDaniel/codex-seo7872 repos~4.6kAutomated safety check: PassMIT
Competitor Teardownirinabuht12-oss/marketing-skills3.8k—~1.6kAutomated safety check: PassNone
Competitor Alternativesfreekmurze/dotfiles1k23 repos~2kAutomated safety check: PassNone
Competitor Analysisaaron-he-zhu/aaron-marketing-skills2.9k1 repos~2kAutomated safety check: PassApache-2.0
Google Maps Contact Extractbrowser-act/skills6.1k—~2.9kAutomated safety check: PassMIT

Similar skills

  • SEO Dataforseo

    AgriciDaniel/codex-seo

    Live SEO data via DataForSEO MCP server. An agent skill from AgriciDaniel/codex-seo.

    787 GitHub starsUsed in 2 repos~4.6k tokens
    Marketing & SEOAuto-check passed
  • Competitor Teardown

    irinabuht12-oss/marketing-skills

    Systematic competitive analysis covering positioning, messaging hierarchy, objection handling, and CTA strategy from landing page URLs or screenshots.

    3.8k GitHub stars~1.6k tokensUpdated 13 days ago
    Marketing & SEOAuto-check passed
  • Competitor Alternatives

    freekmurze/dotfiles

    When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.

    1k GitHub starsUsed in 23 repos~2k tokens
    Marketing & SEOAuto-check passed
  • Competitor Analysis

    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…

    2.9k GitHub starsUsed in 1 repo~2k tokens
    Marketing & SEOAuto-check passed
  • Google Maps Contact Extract

    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…

    6.1k GitHub stars~2.9k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • Marketing Strategy Pmm

    davila7/claude-code-templates

    Product marketing, positioning, GTM strategy, and competitive intelligence.

    32k GitHub starsUsed in 2 repos~9.6k tokens
    Marketing & SEOAuto-check passed

More from Nexus-JPF/note-companion

All 18 skills in this repo
  • Analytics

    Nexus-JPF/note-companion

    When the user wants to set up, improve, or audit analytics tracking and measurement.

    869 GitHub starsUsed in 6 repos~2.2k tokens
    Auto-check passed
  • Customer Research

    Nexus-JPF/note-companion

    When the user wants to conduct, analyze, or synthesize customer research.

    869 GitHub starsUsed in 5 repos~3.2k tokens
    Auto-check passed
  • Marketing Plan

    Nexus-JPF/note-companion

    When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.

    869 GitHub starsUsed in 4 repos~5.2k tokens
    Auto-check passed
  • Onboarding

    Nexus-JPF/note-companion

    When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.

    869 GitHub starsUsed in 3 repos~1.6k tokens
    Auto-check passed
  • Image

    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.

    869 GitHub starsUsed in 2 repos~3.9k tokens
    Auto-check passed
  • Video

    Nexus-JPF/note-companion

    When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks.

    869 GitHub starsUsed in 2 repos~3.6k tokens
    Auto-check passed

Categories

Questions about Competitor Profiling

What does Competitor Profiling do?

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.

When should I use Competitor Profiling?

Competitor Profiling fits situations like: wants to research; analyze competitors from their URLs; the user mentions competitor profile; competitor research.

How do I install Competitor Profiling in Claude Code?

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.

How do I install Competitor Profiling in Codex?

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.

Can I use Competitor Profiling 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 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.

What does Competitor Profiling need to run?

SKILL.md names no scripts, command-line tools or credentials: Competitor Profiling is instructions for the agent only.

Does Competitor Profiling 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 Profiling 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 Profiling use?

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.

How many tokens does Competitor Profiling use?

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.

What are the alternatives to Competitor Profiling?

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.

Who maintains Competitor Profiling?

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.