agentleFS
XuHo-ITXuHo-IT/Content-Agent-Kit/skills/competitor-analysis/SKILL.md

competitor-analysis

Skill8 starsChanged 4 months agoMITView on GitHub

Analyse competitors' recent content — YouTube channels and any blog or news site with a feed — to see what is breaking out, which title devices they use, when they post, and which topics they cover that the user has not. Keyless. Use when the user says "phân tích đối thủ", "đối thủ đang làm gì", "kênh X đang viral cái gì", "so sánh với kênh Y", "tìm khoảng trống nội dung", "competitor analysis", "what is working for <channel>", or when planning a content calendar and wanting evidence instead of guesses. Writes brain/competitors/<date>.md + .json.

65 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-project-setup, openseo-release-notes and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JwuthriSkill

    seo-project-setup

    Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.

    Also in 11 projects that use this

  • JwuthriSkill

    openseo-release-notes

    Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

    Also in 6 projects that use this

  • akii-technologies-ltdSkill

    keyword-clustering

    Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.

    Also in 11 projects that use this

  • MicrosoftSkill

    competitive-landscape

    Use when a branch manager asks something like \"Who are we up against in each metro\"

    Also in 11 projects that use this

  • +5 more from Jwuthri

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 54 edited versions we read keep these.

  • 5

    Distinctive

    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
  1. Distinctive:

    If the user has more than three, save them once so the next run is one command:

    line 40
  2. Distinctive:

    Open the top 2–3 outliers and watch the first 5 seconds: Write down the hook in one line each.

    line 74
  3. Distinctive:

    Evidence or nothing: Every recommendation names the breakout or the number behind it.

    line 100
  4. Distinctive:

    Never a scraper that needs the user's password.

    line 104
  5. Distinctive:

    Do not run this more than once a day per competitor list.

    line 105

“Common” is measured: kept by at least 6 in 10 of the 54 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Competitor analysis

The user names competitors. You come back with three things they can act on this week — not a data dump. The numbers are computed in code so they are the same every time; your job is the part code cannot do: watch the breakouts and say why they worked.

Antigravity / Gemini: same steps, run the commands directly.

Hướng dẫn từng bước cho người dùng

Chạy lệnh node scripts/… ở thư mục gốc của kit — thư mục có AGENTS.md, hai cấp trên file này (nếu skill được cài bằng install-skills.mjs --kit, đường dẫn nằm trong file .kit-root cạnh file này).

Dẫn người dùng theo đúng các bước dưới, bằng lời đơn giản. Trước khi bắt đầu: một câu nói skill sẽ làm gì, mất khoảng bao lâu, cần người dùng chuẩn bị gì. Đầu mỗi bước báo "Bước n/N — <tên bước>" kèm một câu đang làm gì. Khi cần người dùng làm gì, chỉ hỏi đúng một việc. Kết thúc: kết quả nằm ở đâu và việc nên làm tiếp.

BướcAgent làm gìNgười dùng cần làm
1. Nhận đối thủNhận @kênh, link YouTube, website hoặc chuyên mục báo; từ 3 đối thủ thì lưu vào brain/competitors.jsonGửi danh sách đối thủ
2. QuétChạy node scripts/research/competitor-scan.mjs --file brain/competitors.json --history brain/history.json → in REPORT=<đường dẫn>—
3. Xem video bứt pháMở 2–3 video vượt trội nhất, ghi lại câu mở đầu của từng video—
4. Rút kinh nghiệmĐọc cách đặt tiêu đề, giờ đăng, chủ đề họ có mà mình chưa có—
5. Trao ba việc làm ngay"Làm / Thử / Đổi", mỗi việc kèm bằng chứng; báo cáo ở brain/competitors/<ngày>.mdChọn việc muốn làm, có thể chuyển sang create-video

Hay vướng:

  • Chỉ có 15 video gần nhất → báo cáo là "đang hiệu quả gần đây", không phải toàn bộ kênh.
  • Muốn quét TikTok/Instagram → cần APIFY_TOKEN (có phí nhỏ mỗi lần chạy); Facebook chưa hỗ trợ.
  • Muốn chép tiêu đề đối thủ → chỉ lấy cách đặt (câu hỏi, con số…), viết bằng lời của mình.

Step 1 — Collect the targets

Accept any of: @handle, a YouTube channel URL, a UC… id, a website, or — with APIFY_TOKEN set — tiktok:@handle / instagram:@handle / a TikTok or Instagram profile URL. Vietnamese news sections work as-is (https://vnexpress.net/so-hoa, https://tuoitre.vn/cong-nghe.htm) — the script finds their /rss/<section>.rss feed itself.

If the user has more than three, save them once so the next run is one command:

// brain/competitors.json
["@kenh-doi-thu-1", "@kenh-doi-thu-2", "https://blog-doi-thu.vn"]

Step 2 — Run the scan

node scripts/research/competitor-scan.mjs --file brain/competitors.json --history brain/history.json
# or ad hoc:
node scripts/research/competitor-scan.mjs --channel @Fireship --channel https://vnexpress.net/so-hoa --dry-run

It prints REPORT=<path>. --history is what turns on the topic-gap table (phrases the competitors use that never appear in the user's own published titles) — always pass it when the project has one.

flagwhen
--breakout 1.5a small or very consistent channel where nothing reaches 2×
--tz 7default — posting times are shown in Vietnam time
--lang enthe user wants the report in English
--jsonyou want to post-process the numbers yourself

Step 3 — Read it like an editor, not a spreadsheet

The report has five sections. What to take from each:

  1. Overview — posts/week and median views tell you the bar. A channel posting 5×/week with 20K median is a different competitor from one posting weekly with 2M.
  2. Breakouts — outlier (≥2× the channel's own median) is the signal. rising is a young video gaining fast — note it, do not build a strategy on it yet. Open the top 2–3 outliers and watch the first 5 seconds. Write down the hook in one line each. That line is worth more than the whole table.
  3. Title patterns — the device that shows up in breakouts more than in the channel's average is the one the audience rewards. Fireship's trailing "…" is a real example.
  4. Posting schedule — only matters if the user's slots are random today.
  5. Topic gaps — the shortlist for new content. A gap that also appears in a breakout is the strongest candidate.

YouTube's public feed carries the 15 most recent uploads only. Say so when you report — this is "what is working lately", not a channel history. RSS sites have no view counts: for them the report compares cadence and topics, never performance, and it says so itself.

Step 4 — Hand back three moves

1. Làm: <topic from the gap table> — vì <breakout evidence>
2. Thử: <title device from breakouts> trên video tới — ví dụ: "<a title for OUR topic>"
3. Đổi: <schedule or format change> — vì <what the numbers showed>

Then offer the next step: topic-radar on the chosen topic, or create-video directly.

Rules

  • Never copy a title or a script. Take the device (number, question, trailing "…", versus), write the user's own words. Copyright and the review gate both care.
  • Evidence or nothing. Every recommendation names the breakout or the number behind it.
  • TikTok / Instagram need APIFY_TOKEN (optional, paid): tiktok:@kenh, instagram:@kenh. Tell the user it costs a little per run before you add them to a daily list. Facebook is not supported — use their own exports or the ad-library MCP servers (docs/18-ads-and-marketing.md). Never a scraper that needs the user's password.
  • Do not run this more than once a day per competitor list; the numbers do not move faster.

Method and caveats: docs/24-competitor-analysis.md.

To see HOW a breakout video works, not just that it broke out: install the watch-video skill once (node scripts/install-skills.mjs watch-video, MIT) and give it the video's URL. It returns timestamped frames and a transcript, so the report can name the hook in the first three seconds, the cut rhythm and what is on screen. Take the device; never reuse the footage.

From gaps to insight. A topic gap says what competitors do not cover; it does not say what customers struggle with. Feed their low-star reviews and repeated questions into brand-lessons → grab ("Khách muốn ___, nhưng ___, vì ___") — docs/32-bai-hoc-thuong-hieu.md.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.