Token导航 LogoToken导航

Agent Skill · 研究检索

research(研究)

research 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

research 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 40,980。

总安装 1,234周安装 53GitHub Stars 124下载 432核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:research(研究)
来源仓库:https://github.com/kenneth-liao/ai-launchpad-marketplace
仓库路径:skills/research
安装命令:
npx skills add https://github.com/kenneth-liao/ai-launchpad-marketplace --skill research
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/kenneth-liao/ai-launchpad-marketplace --skill research

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

research 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于关键词搜索、任务场景匹配或来源线索筛选等研究检索场景。通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 确认具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。research 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/research

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/kenneth-liao/ai-launchpad-marketplace --skill…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

research 怎么安装?

在终端执行 npx skills add https://github.com/kenneth-liao/ai-launchpad-marketplace --skill research。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

research 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

research 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

research 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

research 用的人多吗?

公开数据是累计安装 1,234 次,近一周安装 53 次,下载 432 次,GitHub 124 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

research 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
research

研究 · 本页

1,234124调用外部服务未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Content Research

Overview

This skill conducts topic and competitor research for any content type. Execute all steps to produce actionable insights that identify content gaps and analyze competitors. This skill focuses ONLY on research — it does not generate titles, hooks, or other creative assets.

Core Principle: Focus on insights and big levers, not data dumping. Research should be comprehensive yet concise, backed by data, and designed to inform strategic decisions.

When to Use

Use this skill when:

  • You need to research a topic before creating content
  • The user asks to research a content idea or topic
  • You want to understand the competitive landscape for a topic
  • You need to identify content gaps and opportunities
  • Preparing for title generation, hook creation, or full content planning

Platform-Specific Research Tools

This skill is designed to work across platforms. Orchestrator skills may provide platform-specific tools for research:

PlatformTools Provided By OrchestratorFallback
YouTubeYouTube Analytics MCP (search, video details, channel details)Web search
Newsletter/BlogContent analytics, email platform dataWeb search
Social MediaPlatform analytics, engagement dataWeb search
GeneralN/AWeb search (default)

Platform-specific research strategies are available in the references/ directory:

  • references/research-frameworks.md — General research frameworks
  • references/substack-notes-strategy.md — Substack Notes strategy
  • references/youtube-community-strategy.md — YouTube community strategy

When no platform-specific tools are available, use web search as a general-purpose research tool to find existing content, competitor analysis, and trending topics.

Research Subagents

You can invoke research subagents using the Agent tool with run_in_background: true to conduct specific, focused research tasks in parallel. Each agent prompt should be focused and specific, with a clear objective.

Bias towards using the Agent tool rather than executing all research sequentially. Parallel research greatly improves performance.

Research Workflow

Execute all steps below to complete the research.

Step 0: Initialize Research Document

Create a research document at the location specified by the orchestrator or the user. If no location is specified, ask the user where to save the output.

All research MUST be written to this file. If the file already exists, read it to understand what research has been done so far and continue from there.

Step 1: Understand the Topic

Analyze and document:

  • What problem does this content solve?
  • Why would someone engage with this content?
  • What makes this topic relevant now?
  • Who is the target audience?

Step 2: Research Existing Content

Execute these actions using available tools (platform-specific MCP tools if provided, otherwise web search):

  1. Find the user's related existing content on the topic
  2. Gather performance metrics where available
  3. Identify what has already been covered and how to differentiate

Document in research file:

  • Related existing content (title, link, key metrics if available)
  • Performance insights (what worked, what did not)
  • Differentiation strategy for new content

Step 3: Competitor Research

Execute these actions:

  1. Find 5-8 top-performing pieces of content on the topic
  2. Filter for recent content with high engagement
  3. Gather details and metrics for each
  4. Analyze patterns in successful content

Document for each competitor:

  • Title, creator/publication, link
  • Key metrics (views, engagement, shares — whatever is available)
  • Focus/angle and what makes it successful

Synthesize key insights: Identify common patterns and different approaches across competitors.

Step 4: Content Gap Analysis

Analyze and identify:

  • What subtopics or angles are saturated?
  • What is missing or underexplored?
  • Where can the user add unique value?

Document in research file:

  • What's Already Well-Covered: 3-5 saturated topics/approaches
  • Content Gaps (Opportunities): Specific opportunities rated by potential

- Rating: * (high), (medium), * (low)

  • Recommended Focus: The specific angle and unique value proposition

Rating Criteria:

  • *** High: Significant gap, strong demand, clear differentiation possible
  • ** Medium: Moderate gap, some competition, good potential
  • - Low: Minor gap, heavily competed, incremental value

Step 5: Recommended Angle

Based on the gap analysis, define:

  • The specific angle to take
  • The unique value proposition
  • Why this angle is better than what already exists
  • What makes the user uniquely qualified to cover this

Output Structure

Use this template structure for the research document:

# [Topic] - Research

## Content Overview
**Topic**: [Brief description]
**Target Audience**: [Who this is for]
**Content Type**: [YouTube video, newsletter, social post, etc.]
**Goal**: [What the audience will learn/gain]

## Research Notes
### Key Concepts to Cover
[High-level list]

## Existing Content Landscape
### User's Related Content
[Analysis of user's previous content on this topic]

### Top Competing Content
[5-8 pieces with analysis]

### Key Insights
[Patterns and findings across competitors]

## Content Gap Analysis
### What's Already Well-Covered
[List of saturated angles]

### Content Gaps (Opportunities)
[Rated list of specific gaps]

### Recommended Focus
[Specific angle and unique value proposition]

## Production Notes
**Status**: Research Complete
**Created**: [Date]
**Updated**: [Date]

Voice Application

Before finalizing any written output, invoke the creator-stack:voice skill to apply voice rules. Research documents should reflect the user's authentic voice, not generic analyst language.

Brand Compliance

When creating assets for The AI Launchpad, invoke creator-stack:brand-guidelines to resolve the correct design system and check anti-patterns.

Execution Guidelines

Focus on Insights, Not Data

Execute research with these principles:

  • Synthesize patterns from research
  • Identify 3-5 key insights with supporting data
  • Explain WHY approaches work
  • Limit competitor research to 5-8 pieces of content

Prioritize Big Levers

Focus research on these impact areas in order:

  1. Content Gaps (unique value)
  2. Competitor Patterns
  3. Audience Needs
  4. Technical/Format Requirements

Back Recommendations with Data

When documenting findings:

  • Bad: "Write about AI agents"
  • Good: "Focus on AI agent memory systems (*** gap) — competitors get high engagement but none cover persistent memory"

Quality Checklist

Verify completion before finalizing research:

  • Topic clearly understood with audience and goal defined
  • User's existing related content reviewed
  • 5-8 competitors documented with analysis
  • Content gaps identified with star ratings
  • Research is concise yet comprehensive (not data dumping)
  • All recommendations backed by data
  • Unique value proposition clearly stated
  • Voice skill applied to final output

Common Pitfalls to Avoid

  1. Data Dumping: Listing every piece of content found without synthesis. Limit to 5-8 top competitors, focus on patterns.
  2. Vague Content Gaps: "Not much content on this topic." Identify specific angles that are missing.
  3. Over-Researching Technical Details: Deep implementation research when high-level coverage suffices. Keep focused on what to cover, not how.
  4. Long Reports: 800+ line documents with low signal. Focus on insights and big levers.
  5. Platform Assumptions: Assuming YouTube tools are available when they may not be. Check what tools the orchestrator has provided.

Example Execution

Scenario: User requests research for content about "Building AI agents with memory"

Execute workflow:

  1. Understand topic: Practical guide to AI agent memory, targeting developers
  2. Find related content: Search user's existing content, find related pieces on personal assistants
  3. Competitor research: Search and analyze 8 top pieces, identify they cover theory not implementation
  4. Gap analysis: Document *** opportunity for practical memory implementation tutorial
  5. Save research: Write to user-specified location

Result: Comprehensive research document ready for review or to proceed to title/hook generation.

Next Step: If the user has asked to plan content, invoke creator-stack:title to generate title options based on this research.

平台分布

Codex

39.84%
按下载量换算172

Claude

28.32%
按下载量换算122

Cursor

19.83%
按下载量换算86

Gemini CLI

9.77%
按下载量换算42

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills