本文へ移動
cccskills
無料GitHub で公開

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".

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

compare

無料

Same-epoch comparison of training runs across wandb, neptune, tensorboard, or mlflow. Aligns runs at the student's current step (never current-vs-final-of-baseline) and separates proxy metrics from downstream targets. Use when the user asks to compare runs, check if a run is improving, track lag against a baseline, rank experiments, or evaluate run-vs-run performance.

日本語の概要は準備中です。原文の説明を表示しています。

fcakyon/phd-skills4182026年10月12日 更新

Use when the user wants to analyze dataset bias, create stratified samples, evaluate fairness, or plan dataset collection. Triggers on phrases like "dataset bias", "stratified sample", "class imbalance", "data distribution", "fairness analysis", or "ethical review".

日本語の概要は準備中です。原文の説明を表示しています。

fcakyon/phd-skills4182026年10月12日 更新

debug

無料

Evidence-before-action diagnosis of failing ML experiments. Probes the system before guessing causes, process list, dmesg, GPU stats, log scrollback, checkpoint state, then states a hypothesis as a hypothesis and runs a smoke before claiming a root cause. Use when the user asks why a run is failing, diverging, OOMing, hanging, slow, producing weird metrics, has crashed, or asks to debug, diagnose, troubleshoot, or investigate a training issue.

日本語の概要は準備中です。原文の説明を表示しています。

fcakyon/phd-skills4182026年10月12日 更新

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".

日本語の概要は準備中です。原文の説明を表示しています。

fcakyon/phd-skills4182026年10月12日 更新

Use when the user wants to set up or troubleshoot a LaTeX environment, choose between biber and bibtex, install packages for a specific venue template, or configure compilation. Triggers on phrases like "setup latex", "biber vs bibtex", "latex compilation error", "install latex packages", "venue template", or "texlive setup".

日本語の概要は準備中です。原文の説明を表示しています。

fcakyon/phd-skills4182026年10月12日 更新

launch

無料

Pre-flight checklist for long-running ML training jobs covering config diff, run naming, path verification, monitoring setup, and restart-cleanup. Use when the user asks to launch, kick off, start, restart, or kill a training run, or mentions launching a multi-hour or multi-day GPU job (python train, accelerate launch, torchrun, deepspeed, sbatch, tmux training).

日本語の概要は準備中です。原文の説明を表示しています。

fcakyon/phd-skills4182026年10月12日 更新

fcakyon のスキルをすべて見る

このスキルの問題を報告する