Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问许可证需确认审计提醒

research研究

Agent Skill

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

总安装

1,234

周安装

53

GitHub Stars

124

下载量

432
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

research 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于关键词搜索、任务场景匹配或来源线索筛选等研究检索场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 确认具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。
  • research 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

39.84%
按下载量换算172

Claude

28.32%
按下载量换算122

Cursor

19.83%
按下载量换算86

Gemini CLI

9.77%
按下载量换算42

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

external-service

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills