niche-research
- Repo stars 1,355
- Author updated Live
- Author repo social-media-skills
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @charlie947 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: niche-research
description: > When this skill triggers, go straight to Step 1. Do not summarise the research method. This sk…
category: other
runtime: no special runtime
---
# niche-research output preview
## PART A: Task fit
- Use case: > When this skill triggers, go straight to Step 1. Do not summarise the research method. This skill needs live browsing. Use this order of preference: Pick the best available path and continue. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “CRITICAL: Auto-start on load / Prerequisites / Step 1. Gather the niche” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “> When this skill triggers, go straight to Step 1. Do not summarise the research method. This skill needs live browsing. Use this order of preference: Pick the best available path and continue. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “CRITICAL: Auto-start on load / Prerequisites / Step 1. Gather the niche” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “CRITICAL: Auto-start on load / Prerequisites / Step 1. Gather the niche”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: niche-research
description: > When this skill triggers, go straight to Step 1. Do not summarise the research method. This sk…
category: other
source: charlie947/social-media-skills
---
# niche-research
## When to use
- > When this skill triggers, go straight to Step 1. Do not summarise the research method. This skill needs live browsin…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “CRITICAL: Auto-start on load / Prerequisites / Step 1. Gather the niche” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "niche-research" {
input -> user goal + target files + boundaries + acceptance criteria
context -> CRITICAL: Auto-start on load / Prerequisites / Step 1. Gather the niche
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Niche Research
CRITICAL: Auto-start on load
When this skill triggers, go straight to Step 1. Do not summarise the research method.
Prerequisites
This skill needs live browsing. Use this order of preference:
- Claude for Chrome extension (preferred). Check that the extension is enabled and Claude has permission to browse on the current tab. If not, tell the user:
Enable the Claude for Chrome extension and open a blank tab. I need to drive the browser to scroll Reddit, X, and run Google searches with verified dates.
- Playwright MCP as a fallback if the Claude for Chrome extension is not available.
- WebSearch + WebFetch tools as a last resort (less thorough on feed scrolling).
Pick the best available path and continue.
Step 1. Gather the niche
Call AskUserQuestion:
[
{
"question": "What niche do you want to research?",
"header": "Niche",
"multiSelect": false,
"options": [
{"label": "I will type my niche", "description": "Type the exact niche phrase after this"},
{"label": "Pull from about-me.md", "description": "Use the niche and audience already in my voice files"}
]
}
]If the user picks "Pull from about-me.md", read the file from the project root. If the file does not exist or does not name a clear niche, fall back to asking the user to type it.
Step 2. Browse like a human researcher
Drive the browser through these actions in order. Verify publish dates on every item. Exclude anything older than 7 days from today without exception.
2a. Reddit feed scanning
- Navigate to https://www.reddit.com/ (home feed).
- Scroll the feed. Load more posts.
- Open niche-relevant posts. On each post, check the "posted X days ago" timestamp.
- Discard posts older than 7 days.
- Repeat with https://www.reddit.com/r/popular/.
- Also search any niche-specific subreddits that come up while scrolling.
2b. X (Twitter) feed scanning
- Navigate to https://x.com/home (For You feed).
- Scroll multiple screens.
- Open full threads for niche-relevant tweets.
- Check the post timestamp on each thread.
- Discard posts older than 7 days, even if engagement is high.
2c. Google web search
Run these searches one by one, open the top results, verify publish dates.
[niche] news(set Tools → Any time → Past week)[niche] launch(past week)[niche] controversy(past week)[niche] research(past week)[niche] regulation(past week)
For each promising result:
- Open the page.
- Locate the visible publish date.
- Verify it is within the last 7 days.
- If the date is missing, unclear, or older than 7 days, exclude it.
Step 3. Synthesise into themes
Collect a broad pool of verified, in-window items. Group related items into themes. Each theme may combine social discussion and news coverage.
Select themes that show at least two of:
- Strong attention or discussion
- Clear disagreement or debate
- Novel insight or new information
- Real-world implications for the niche
Target 20 themes. Fewer is acceptable if genuinely limited.
Step 4. Output
First line before the table:
As of [DD/MM/YYYY]Then a markdown table with these exact columns:
| Theme / Emerging Story | Platforms (Reddit, X, News) | Key Communities / Accounts / Sources | Representative Links | Attention Signals | What's Happening or Being Debated | Why It Matters for [NICHE] | Shareable Angle |No prose outside the table.
Step 5. Offer the next move
After the table, ask:
Any row here you want me to turn into a LinkedIn post? Call the post-writer skill with the row number, or the post-formatter skill to apply a framework.
Rules
- Never invent links, metrics, or dates.
- Exclude anything older than 7 days without exception.
- Verify every publish date before including an item. No shortcuts.
- Table only at the end. No commentary, no summary paragraph.
- If fewer than 20 themes pass the filter, say so. Do not pad with weak items.
- If Claude for Chrome is not available and neither Playwright MCP nor WebSearch can cover feed scrolling properly (Reddit and X), tell the user what is missing rather than faking the scan.
- British English throughout. DD/MM/YYYY date format.
- Never use em dashes.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review