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

survey-generator

Compile a structured literature survey on any AI/ML topic. Agent curates a research bundle (taxonomy + sections + bibliography of real papers) from a public anchor resource, then a chosen LLM generates the survey artifact. Output target is a wiki page (markdown), not a one-off HTML — survey lands in `<wiki>/derived/surveys/<slug>.md` with full bibliography rows in `sources.md`. Provider-agnostic (Anthropic/OpenAI/OpenRouter/Fireworks/custom OpenAI-compat). Use when the user asks for a "survey", "literature review", "lit review", or "deep dive" on a technical topic.

インストール方法を見る

含まれるファイル(3)

  • SKILL.md6.2 KB
  • scripts/build-survey.js10.3 KB
  • templates/research_bundle.template.json1.7 KB

SKILL.md(原文)

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

Survey Generator

Provider-agnostic literature-survey artifact generator. Output flows into a pro-workflow wiki, not a standalone HTML file — survives sessions and indexes for FTS5 retrieval.

Diff vs dair-academy version

dairpro-workflow
Hardcoded Kimi K2.6 on FireworksProvider-agnostic (Anthropic/OpenAI/OpenRouter/Fireworks/custom)
Output = single-file HTML with inline SVGOutput = wiki markdown page + bibliography rows in sources.md
One-off artifact, no follow-upPersists in FTS5 index; reused by wiki-research-loop
Manual run onlyComposable with /wiki research for auto-bibliography expansion

When to use

  • "Survey on <topic>" / "lit review on <topic>"
  • Onboarding a new domain — generate the map-of-the-field
  • After a wiki has 10-30 sources, compile a synthesis page over them
  • Pre-step before /wiki research runs: gives the loop a high-quality seed bundle

Inputs

InputRequiredDescription
topicyes"Reasoning Models", "Agentic Engineering"
source_urlyesPublic anchor: arXiv survey, GitHub awesome-list, canonical blog post
--wiki <slug>yesTarget wiki for the artifact
--bibliography-size NnoDefault 20. 40-50 comprehensive, 80-100 exhaustive
--section-count NnoDefault 6-10 numbered sections
--provider namenoOverride provider (default: first explicitly configured provider)
--model idnoOverride model

Workflow (the agent runs these in order)

Step 1 — Read the anchor

WebFetch source_url. Extract subtopics + cited papers. For GitHub awesome-lists, walk README + linked papers files. For arXiv survey PDFs, use abstract + ToC.

Step 2 — Build research_bundle.json

Use templates/research_bundle.template.json as scaffold. Required keys:

{
  "topic": "...",
  "anchor_source": "...",
  "abstract_hints": ["..."],
  "taxonomy": [{"branch": "...", "children": [{"name": "...", "description": "..."}]}],
  "sections": [{"title": "...", "guidance": "...", "papers": ["key1","key2"]}],
  "bibliography": [{"key": "author-year-shortname", "authors": "...", "year": 2024, "title": "...", "venue": "...", "summary": "..."}]
}

Hard rules:

  • Every paper in bibliography must be real. No invented entries.
  • Every key referenced in sections[].papers must exist in bibliography.
  • 4-8 taxonomy branches, 2-4 children each.
  • 6-10 numbered sections covering: introduction → foundations → methods → evaluation → open problems.

Step 3 — Run the generator

In a plugin session, call the providers MCP server's run_provider_task tool with task: "survey" and args: ["--bundle", "/absolute/path/research_bundle.json", "--wiki", "<slug>", "--provider", "openai"]. Keys come from the plugin configuration dialog. Never request keys in chat or retrieve existing machine credentials.

The direct commands below are for standalone CLI use with explicit PRO_WORKFLOW_*_API_KEY variables. See provider configuration.

node $SKILL_ROOT/scripts/build-survey.js \
  --bundle <path-to-research_bundle.json> \
  --wiki <slug> \
  [--provider anthropic|openai|openrouter|fireworks|custom] \
  [--model <id>]

Generator:

  1. Reads bundle.
  2. Sends to LLM with strict markdown spec (numbered sections, inline [^paper-key] citations, no HTML).
  3. Writes output to <wiki>/derived/surveys/<topic-slug>.md.
  4. Appends bibliography rows to <wiki>/sources.md (deduped by key).
  5. Calls wiki-cli.js page to upsert into FTS5 index.

Step 4 — Iterate

If prose is thin: tighten sections[].guidance and rerun. Output filename versions automatically (<slug>-v2.md, <slug>-v3.md).

To compare providers:

node build-survey.js --bundle bundle.json --wiki agent-memory --provider openai --model gpt-4o
node build-survey.js --bundle bundle.json --wiki agent-memory --provider anthropic --model claude-opus-5-5

Each writes a separate versioned file; diff them.

Output structure

<wiki-root>/
├── sources.md                                 # bibliography rows appended (deduped)
└── derived/surveys/
    └── <topic-slug>-v1.md                     # the survey
        # title (h1)
        # ## 1. Introduction
        # ## 2. Foundations
        # ...
        # ## References
        # [^src-bib-<slug>] author year. title. venue.

Hard rules

  1. Never invent bibliography entries — every paper must be a real work with venue.
  2. Every section's papers array references keys in bibliography.
  3. Output is markdown ONLY. No HTML, no inline SVG, no JS.
  4. Bibliography rows in sources.md use the slug-style id src-bib-<slug> (derived from the bibliography key); cite as [^src-bib-<slug>]. Manual non-bibliography sources continue to use src-NNN.
  5. Iterate on inputs (research_bundle.json), not on the generated output.
  6. Provider+model selection is the user's call — never hardcode.

Composing with research loop

/wiki init reasoning-models --title "Reasoning Models" --flavor research
# Manually compile a research_bundle.json
node skills/survey-generator/scripts/build-survey.js --bundle bundle.json --wiki reasoning-models
# Now the wiki has a structured survey + 50 bibliography rows
# Enable auto-research to expand:
# (edit reasoning-models/wiki.config.md, set auto_research.enabled: true)
node skills/wiki-research-loop/scripts/research-loop.js seed reasoning-models "chain-of-thought failure modes" --depth 0
node skills/wiki-research-loop/scripts/research-loop.js run reasoning-models

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.

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

rohitg00/pro-workflow2,9132026年9月29日 更新

Auto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.

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

rohitg00/pro-workflow2,9132026年9月29日 更新

Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.

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

rohitg00/pro-workflow2,9132026年9月29日 更新

Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".

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

rohitg00/pro-workflow2,9132026年9月29日 更新

Smart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual compact or when auto-compact triggers.

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

rohitg00/pro-workflow2,9132026年9月29日 更新

Master the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to keep AI sessions sharp and efficient.

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

rohitg00/pro-workflow2,9132026年9月29日 更新

rohitg00 のスキルをすべて見る

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