agentsclimarketplace
Sign in

Research synthesis

Skill viktorbezdek/skillstack/research-synthesis/skills/research-synthesis

Structured research and evidence synthesis for knowledge-intensive tasks. Use for multi-source research coordination, evidence triangulation across conflicting sources, competing-hypothesis analysis, literature/documentation sweeps, claim verification, and synthesis reports. Trigger phrases: "research this topic", "synthesise findings from", "compare sources on", "what does the evidence say about", "triangulate these claims". NOT for primary data collection (interviews, surveys) — this skill synthesises existing sources. NOT for code research or codebase exploration — use CodeGraph and Semble for that. NOT for creative content generation — synthesis produces structured analysis, not narrative content.From its SKILL.md

Install
npx -y skills add viktorbezdek/skillstack --skill research-synthesis

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 358 tokens by cl100k_base, as published. Nobody here has run it

research-synthesis

Multi-source research coordination, evidence triangulation, competing-hypothesis analysis, and structured synthesis for knowledge-intensive tasks.

When to use

  • Research the tradeoffs between gRPC and REST for internal microservice communication
  • Synthesise what the evidence says about daily standups harming deep work
  • Compare three sources on the effectiveness of TDD — what do they agree and disagree on?
  • I have 5 conflicting reports on LLM inference costs — triangulate the actual picture
  • Do a literature sweep on context window utilisation patterns in production LLMs
  • Research prompt injection attack vectors and summarise defensive patterns
  • What competing hypotheses exist for why the attention mechanism scales so well?
  • Synthesise our internal incident post-mortems to find common root-cause patterns

When NOT to use

  • Run a customer survey to validate our product hypothesis — Primary data collection — not synthesis
  • Explore this codebase and find where authentication happens — Code research — use CodeGraph/Semble
  • Write a blog post about distributed systems — Creative content generation — not evidence synthesis
  • What is the capital of France? — Single-fact lookup — no synthesis needed

Anti-patterns

Symptom

Invoking this skill for tasks outside its scope — e.g., infrastructure concerns when the request is about application code, or vice versa.

Problem

Scope mismatch wastes context and produces advice tuned for the wrong domain. A database schema skill answering a connection-pooling question gives schema advice when the real problem is operational configuration.

Solution

Read the NOT for clauses carefully. If the request matches an exclusion, identify the correct skill (check SkillStack for the right domain) rather than stretching this skill to cover adjacent ground.

What ships with it: 2 files

6.0 KB alongside SKILL.md

evals/

Keep looking

Skills are one crate of 326,851. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.