MCPInstall

literature-research

Use when the user wants to find related work, survey a research area, identify literature gaps, or discover open-source implementations. Triggers on phrases like "find papers on", "related work", "literature review", "what papers exist", "open source implementation", or "papers with code".

Installs
84
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/fcakyon/phd-skills --skill literature-research
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads literature-research automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Literature Research Methodology

You are helping a researcher conduct systematic literature research. Follow this methodology to ensure thorough, accurate coverage.

Step 1: Scope Definition

Before searching:

  • Clarify the exact research question or topic boundary
  • Identify key terms and their synonyms (e.g., "content moderation" = "safety filtering" = "NSFW detection")
  • Define inclusion/exclusion criteria (year range, venue type, methodology type)
  • Ask if the user has seed papers to start from

Step 2: Systematic Search

Use multiple search strategies in order:

2a. Direct Search

Use Paper Search CLI; follow setup if it is missing.

paper-search search 'object detection' -s fast -n 5
paper-search search 'object detection' -s arxiv,crossref -n 5

Inspect the JSON errors field and retain each paper's source ID and URL. Report unavailable providers rather than treating errors as an empty literature search. Vary search terms to catch different framings of the same concept. Use web search for proceedings and sources the CLI cannot access.

2b. Citation Chaining

From seed papers or initial results:

  • Forward chaining: run paper-search tool get_citing_papers <doi>
  • Backward chaining: run paper-search tool get_referenced_papers <doi>
  • Both accept a DOI or OpenAlex work ID, not a title. Inspect pagination and truncation metadata; neither command promises an exhaustive citation list. Read the paper's reference section to verify cited works.
  • This catches papers that use different terminology but address the same problem

2c. Venue Mining

  • Identify top venues for the topic (conferences, journals, workshops)
  • Check recent proceedings of these venues for relevant papers
  • Workshop papers often contain early-stage work not yet in main conferences

2d. Open Source Discovery

  • Search GitHub for implementations related to the topic
  • Check Papers With Code for the specific task/dataset
  • Look for "awesome-X" lists curated by the community

Step 3: Categorization

Organize found papers into a structured taxonomy:

| Paper | Year | Venue | Approach | Key Result | Code? | Relevance |
|-------|------|-------|----------|-----------|-------|-----------|

Group by methodology or approach type, not chronologically.

Step 4: Gap Identification

Map what exists vs. what's missing:

  1. Coverage matrix: rows = problem aspects, columns = existing approaches
  2. Empty cells = potential gaps
  3. For each candidate gap:
    • Search specifically for work filling this gap (it may exist under different terms)
    • Check very recent papers (last 6 months) that might have addressed it
    • Assess whether the gap is meaningful (would filling it advance the field?)

Step 5: Gap Validation

For each identified gap, verify it's real:

  • Searched with at least 3 different phrasings
  • Checked proceedings of top-3 venues from last 2 years
  • No preprint on arXiv addressing this gap
  • The gap is technically feasible to address
  • Filling the gap would be a meaningful contribution

Rate confidence: HIGH (extensively searched, clearly missing), MEDIUM (searched but might have missed niche work), LOW (limited search, gap may exist elsewhere).

Step 6: Output Format

Produce a structured research landscape:

  1. Topic summary — 2-3 sentence overview of the research area
  2. Paper table — categorized list with year, venue, approach, results, code availability
  3. Gap table — identified gaps with confidence levels and evidence
  4. Recommended readings — top 5-10 most relevant papers for the user's specific work
  5. Candidate citations — BibTeX entries for papers worth citing (MUST verify against DBLP before presenting)

Citation Integrity

Every paper mentioned must have verified metadata:

  • Author names: cross-check with DBLP or the paper's official page
  • Venue and year: confirm against the published version (not preprint)
  • Claims about results: only include numbers you can trace to a specific table/figure in the paper
  • If uncertain about any detail, flag it explicitly rather than guessing

FAQ

What does the literature-research skill do?

Use when the user wants to find related work, survey a research area, identify literature gaps, or discover open-source implementations. Triggers on phrases like "find papers on", "related work", "literature review", "what papers exist", "open source implementation", or "papers with code".

How do I install literature-research?

Run npx skills add https://github.com/fcakyon/phd-skills --skill literature-research in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/literature-research/ (personal) or .claude/skills/literature-research/ (project).

Which AI agents can use literature-research?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is literature-research safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains literature-research?

It is published by fcakyon in fcakyon/phd-skills. It has 84 recorded installs.

More from fcakyon/phd-skills

View all →

paper-writing

fcakyon/phd-skills

Open the skill to read its SKILL.md instructions.

Docs & Writing156 installs

reproduce

fcakyon/phd-skills

Open the skill to read its SKILL.md instructions.

84 installs

paper-verification

fcakyon/phd-skills

Open the skill to read its SKILL.md instructions.

experiment-design

fcakyon/phd-skills

Use when the user wants to design experiments, plan ablation studies, structure baselines, or create incremental evaluation strategies. Triggers on phrases like "design ablation", "plan experiment", "what experiments should I run", "baseline comparison", or "experiment matrix".

reviewer-defense

fcakyon/phd-skills

Use when the user wants to anticipate reviewer questions, select the strongest ablations to present, prepare rebuttals, or identify paper weaknesses before submission. Triggers on phrases like "reviewer questions", "anticipate reviewers", "rebuttal", "paper weaknesses", "defend the paper", or "strengthen the paper".

dataset-curation

fcakyon/phd-skills

Open the skill to read its SKILL.md instructions.

Data & Databases66 installs

Popular productivity & automation skills

View category →

agent-browser

vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

OfficialProductivity & Automation1.3M installs

lark-doc

open.feishu.cn

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

lark-base

open.feishu.cn

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。

lark-drive

open.feishu.cn

飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。

lark-shared

open.feishu.cn

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.

lark-im

open.feishu.cn

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。