agentleFS
jurgendnjurgendn/agent-skills/skills/research-evidence/literature-triangulation/SKILL.md

literature-triangulation

Skill15 starsChanged 2 months agoNo licenceView on GitHub

Build a source-grounded map of a research topic by comparing papers, benchmarks, code, and genuine disagreements. Use whenever the user wants to understand a research area, not just find papers — including phrasings like "what's the current state of X", "what should I read on Y", "is X still SOTA", "are there good baselines for Z", "what does the field believe about W", "survey this area for me", "what are the key papers on X", "compare these two approaches", or "is this claim actually well-supported". Also use when the user is about to build on a method and should first verify the evidence base is solid. If the user already has a source map and wants polished Related Work prose, use related-work-writer instead. The skill's main job is preventing hallucinated consensus — confidently synthesized positions that aren't grounded in the actual sources.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.