Social Media Research Ops logo

Social Media Research Ops

Community
HunterSUNSUN
social-media-research-ops

Social media competitor research and operations workflow for turning real platform browsing into reusable content strategy, account positioning, post ideas, and Obsidian-ready research notes. Use when the user asks to research competitor social accounts, analyze X/Twitter, Xiaohongshu, TikTok, Reddit or similar platforms, plan social media growth, create a posting strategy, study comments and platform dynamics, produce daily research notes, or reuse a prior social media research process.

Overview

PublisherHunterSUNSUN
Repositorysocial-media-research-ops
Skill namesocial-media-research-ops
Stars
55
Forks
3
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by HunterSUNSUN on GitHub. Read the source before you install it.

Installation

Install the Social Media Research Ops AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/HunterSUNSUN/social-media-research-ops/tree/main/social-media-research-ops
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/HunterSUNSUN/social-media-research-ops.git /tmp/social-media-research-ops
mkdir -p .claude/skills
cp -r /tmp/social-media-research-ops/social-media-research-ops .claude/skills/social-media-research-ops
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Social Media Research Ops in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Social Media Research Ops on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Social Media Research Ops is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Social Media Research Ops

Overview

Use this skill to run a repeatable social media research process: define the research target, browse real platform samples, record posts and comments, infer platform-specific methods, and write structured outputs into Obsidian.

Use the Obsidian vault path provided by the user. If no path is provided, inspect the available workspace or ask only when writing files is required and no reasonable location can be inferred.

Operating Rules

  • Browse slowly and behave like a reader when using logged-in social platforms.
  • Do not like, follow, comment, post, DM, bookmark, collect, change settings, or otherwise mutate social accounts.
  • If a platform shows verification, captcha, login, rate limit, or unusual security prompt, stop that platform and tell the user.
  • Separate verified observations from inferred conclusions.
  • Prioritize real posts, comment sections, search suggestions, profile positioning, and repeated patterns over generic marketing theory.
  • Write durable findings to Obsidian whenever the task is research-heavy or the user asks for reusable output.

Workflow

1. Set Research Scope

Clarify or infer:

  • Product or project being promoted.
  • Target users and regions.
  • Platforms to study.
  • Competitor categories.
  • Desired output: strategy, platform playbook, post ideas, account matrix, daily report, or all of these.

If the user gives no platform priority, start with:

  1. X/Twitter for global AI/video/creator ecosystem and model discourse.
  2. Xiaohongshu for Chinese search, tutorials, save-worthy content, and comment demand.
  3. TikTok for short-form visual hooks.
  4. Reddit for honest demand research and anti-promo constraints.

2. Build The Sample Map

Collect samples across three layers:

  • Direct competitors: same product category or same user job.
  • Adjacent accounts: creator tools, AI video generators, model labs, workflow creators, tool curators.
  • Demand communities: Reddit threads, search result pages, comment sections, Q&A posts.

For each account or query, record:

  • Platform, account/query, URL, date accessed.
  • Positioning and audience.
  • Follower or visible credibility signal.
  • Representative post titles/topics.
  • Engagement signals.
  • Repeated content formats.
  • Comment-section questions and objections.

3. Read Posts And Comments

For high-value posts, capture:

  • Hook/title/cover.
  • Content structure.
  • Offer or implicit promise.
  • Tool/model/workflow mentioned.
  • Engagement numbers when visible.
  • Comment questions, objections, buying signals, and confusion.
  • What the creator replies to and ignores.

Do not over-index on one viral post. Look for repeated needs across accounts, searches, and comments.

4. Infer Platform Logic

Analyze each platform separately before making cross-platform conclusions.

For X/Twitter:

  • Look for model launches, creator workflows, benchmark demos, quote/reply dynamics, credibility-building threads, and founder/creator conversations.
  • Favor tested judgment over plain links or news reposts.

For Xiaohongshu:

  • Look for search terms, related searches, high-save tutorials, workflow diagrams, tool selection tables, price/cost discussions, and comments asking how, where, free, member, prompt, queue, and can it do my scene.
  • Favor scenario-led, save-worthy content over abstract product claims.

For TikTok:

  • Look for first-second hook, visual result, on-screen text, save/share triggers, comment questions, and pinned tool/cost details.
  • Favor short demos and same-input comparisons.

For Reddit:

  • Read community rules before proposing posts.
  • Treat Reddit as demand research and transparent comparison, not hard promotion.

5. Convert Findings Into Strategy

Produce strategy in this order:

  1. Core positioning.
  2. Platform-specific role.
  3. Content pillars.
  4. First 10-30 post ideas.
  5. Account matrix if useful.
  6. Comment/reply strategy.
  7. Risks and anti-patterns.
  8. Next research breakpoint.

For AI video aggregation products, a useful default hypothesis is:

Do not lead with "tool directory"; lead with "AI video workflow researcher / tool selection advisor / cost and limitation guide".

Validate or revise this hypothesis against new data.

Obsidian Outputs

Use Obsidian links and short, navigable files. Prefer a main index plus platform-specific notes instead of one giant document.

For an existing vault, preserve its established grouping. A useful structure has a social media operations folder with platform folders for X, Xiaohongshu, Reddit, and TikTok, plus overview, competitor library, execution plan, and raw research or method folders.

Recommended structure:

  • social-media-index.md
  • social-media-x-deep-dive-stage-n.md
  • social-media-xiaohongshu-deep-dive-stage-n.md
  • social-media-tiktok-observations-stage-n.md
  • social-media-reddit-observations-stage-n.md
  • social-media-stage-conclusion-yyyy-mm-dd.md
  • social-media-competitor-account-library.md
  • daily-reports/yyyy-mm-dd-work-report.md
  • memory/ai-collaboration-memory-project-and-working-style.md

When producing substantial outputs, read references/templates.md for reusable note templates.

Daily Memory And Reports

When the user asks for daily work logging, end-of-day reports, project memory, or continuity:

  • Write a daily report under the daily reports folder.
  • Update long-term memory only with durable facts: project state, preferences, decisions, constraints, repeated workflows.
  • Do not store one-off browsing noise in long-term memory.

Daily reports should include:

  • Work completed.
  • Files created or updated.
  • Key judgments.
  • User preferences learned.
  • Unfinished items.
  • Next continuation point.
  • Risks or account/platform issues.

Quality Bar

Before finishing, check:

  • Each platform has its own conclusion.
  • Comment-section demand is captured, not just post topics.
  • Recommendations are actionable enough to publish from.
  • The user can resume from the next breakpoint.
  • Obsidian notes are easy to navigate from a main index.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Social Media Research Ops AI skill do?

Social media competitor research and operations workflow for turning real platform browsing into reusable content strategy, account positioning, post ideas, and Obsidian-ready research notes. Use when the user asks to research competitor social accounts, analyze X/Twitter, Xiaohongshu, TikTok, Reddit or similar platforms, plan social media growth, create a posting strategy, study comments and platform dynamics, produce daily research notes, or reuse a prior social media research process.

Why use Social Media Research Ops on TypingMind?

Because you install it once and use it with any model. Social Media Research Ops is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Social Media Research Ops in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/HunterSUNSUN/social-media-research-ops/tree/main/social-media-research-ops. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Social Media Research Ops?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Social Media Research Ops?

As many as you like. As long as a model supports skills, you can use Social Media Research Ops with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Social Media Research Ops AI skill free?

Yes. It is published on GitHub by HunterSUNSUN under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇