---
name: competitor-social-research
description: Use when the user wants to research competitors' social media strategy, compare brands or creators, find what content is working in a niche, identify content gaps, or produce a practical social strategy brief from public social data.
allowed-tools: Bash, Read, Write, WebFetch

version: 1.0.0
author: ScrapeCreators
license: MIT
homepage: https://scrapecreators.com
repository: https://github.com/ScrapeCreators/social-media-research-skills
metadata:
  openclaw:
    requires:
      env:
        - SCRAPECREATORS_API_KEY
    primaryEnv: SCRAPECREATORS_API_KEY
    homepage: https://scrapecreators.com
    tags:
      - social-media
      - research
      - scrapecreators
title: competitor-social-research
canonical_url: https://skilld.dev/gh/scrapecreators/social-media-research-skills/competitor-social-research
last_updated: 2026-10-23T07:46:32.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install scrapecreators/social-media-research-skills/competitor-social-research`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/competitor-social-research`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/scrapecreators/social-media-research-skills/competitor-social-research) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/competitor-social-research`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/competitor-social-research --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/competitor-social-research --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Competitor Social Research

## Overview

Analyze what competitors are doing on social and what appears to be working. This skill combines profile data, recent posts, outlier analysis, transcripts, and optionally comments to produce a practical competitor brief.

## When to Use

Use this skill when the user asks to:

- compare competitors on TikTok, Instagram, YouTube, LinkedIn, Facebook, X, Threads, or other social platforms
- find what content is working in a niche
- benchmark posting frequency, formats, topics, and engagement
- identify content gaps or opportunities
- build a social strategy from competitor research

## Workflow

1. **Define competitors and platforms**
   - Use provided handles/URLs.
   - If only company names are provided, search profiles first and confirm likely matches when ambiguity matters.

2. **Fetch profile snapshots**
   - Followers/subscribers
   - Bio/positioning
   - Links
   - Verification/public metadata

3. **Fetch recent content**
   - Pull comparable recent windows per competitor.
   - Track source URLs, dates, captions, formats, and metrics.

4. **Find outliers per competitor**
   - Use each account's own median baseline.
   - Do not compare raw views between a huge brand and a small brand without context.

5. **Analyze content strategy**
   - Content pillars
   - Formats
   - Hook styles
   - Posting cadence
   - Offers/CTAs
   - Use of founder/creator personality
   - Community/comment patterns

6. **Find gaps and opportunities**
   Look for:
   - topics competitors avoid
   - formats that overperform but few competitors use
   - unanswered audience questions
   - weak hooks or repetitive content
   - platform whitespace

## Useful ScrapeCreators Endpoints

Use the relevant profile/feed/detail/transcript/comment endpoints from `scrapecreators-api`. Common routes include:

- TikTok: `/v1/tiktok/profile`, `/v3/tiktok/profile/videos`
- Instagram: `/v1/instagram/profile`, `/v2/instagram/user/posts`, `/v1/instagram/user/reels`
- YouTube: `/v1/youtube/channel`, `/v1/youtube/channel-videos`, `/v1/youtube/channel/shorts`
- LinkedIn: `/v1/linkedin/company`, `/v1/linkedin/company/posts`
- Facebook: `/v1/facebook/profile`, `/v1/facebook/profile/posts`, `/v1/facebook/profile/reels`
- X/Twitter: `/v1/twitter/profile`, `/v1/twitter/user-tweets`
- Threads: `/v1/threads/profile`, `/v1/threads/user/posts`
- Bluesky: `/v1/bluesky/profile`, `/v1/bluesky/user/posts`

## Output Format

```markdown
# Competitor Social Research Brief

## Executive Summary
- Biggest opportunity:
- Competitor to study closest:
- Content format to test first:

## Competitor Snapshot
| Competitor | Platforms | Audience size | Posting cadence | Best-performing format | Notes |
|---|---|---:|---|---|---|

## What Is Working
### Competitor A
- Content pillars:
- Outlier examples:
- Hooks/formats:

## Cross-Competitor Patterns
1. ...
2. ...

## Gaps and Opportunities
| Opportunity | Evidence | Suggested test |
|---|---|---|

## Recommended Content Tests
1. ...
2. ...
3. ...

## Sources
- [Post/profile/ad](url)
```

## Common Pitfalls

- Do not compare competitors only by follower count. Engagement and outlier lift matter more.
- Do not mix platforms without platform context. A good LinkedIn post and good TikTok are different artifacts.
- Do not assume a profile match from a company name if multiple brands share the name.
- Do not present competitor strategy as fact when it is inferred from public content. Say "appears to" or "suggests".
