论文测试
- 作者仓库星标 1,355
- 作者更新于 实时读取
- 作者仓库 social-media-skills
- 领域
- 通用
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @charlie947 · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: niche-research
description: > When this skill triggers, go straight to Step 1. Do not summarise the research method. This sk…
category: 通用
runtime: 无特殊运行时
---
# niche-research 输出预览
## PART A: 任务判断
- 适用问题:通用任务拆解、检查和交付。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“CRITICAL: Auto-start on load / Prerequisites / Step 1. Gather the niche”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于通用任务拆解、检查和交付,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“CRITICAL: Auto-start on load / Prerequisites / Step 1. Gather the niche”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
先用一个小任务确认它会围绕“CRITICAL: Auto-start on load / Prerequisites / Step 1. Gather the niche”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: niche-research
description: > When this skill triggers, go straight to Step 1. Do not summarise the research method. This sk…
category: 通用
source: charlie947/social-media-skills
---
# niche-research
## 什么时候使用
- 把通用方向的常用动作沉淀成 Agent 可调用的技能 适合处理通用任务拆解、检查、交付和复盘,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤;通常不需要额外…
- 面向通用任务拆解、检查和交付,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「CRITICAL: Auto-start on load / Prerequisites / Step 1. Gather the niche」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "niche-research" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> CRITICAL: Auto-start on load / Prerequisites / Step 1. Gather the niche
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} 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.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核