agentleFS
tatashbartatashbar/Economic-Modeling-Studio/.agents/skills/literature-review/SKILL.md

literature-review

Skill4 starsChanged 6 days agoMITView on GitHub

Reviews the theoretical and empirical literature and existing models in use for a modeling question.

92 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pdf-explore, paper-narrative and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JimLiuSkill

    pdf-explore

    Use this skill when the user has attached a PDF, paper, report, or other document and the answer needs content from more than one place in it: summarize the methods or any other section, compare sections, find where a topic is discussed, read a value or label off a figure or chart, or find/list/extract every instance of something across the whole document (datasets, benchmarks, citations, figures, table rows, accession numbers — including appendices). Skip it only for a single lookup of 1–4 pages quoted in your very next response — `read_file(pages=[...])` attaches pages as images that are dropped from context after one turn, so multi-section answers end up re-reading the same ranges repeatedly. Parses the PDF once in the Python kernel: `pdf_pages` (pages as persistent text), `pdf_outline` (TOC), `pdf_scan` (rank pages by relevance), `pdf_map`/`pdf_extract` (per-page summary / structured fields via parallel haiku calls). For PDF creation/manipulation, use reportlab/pypdf directly.

    Also in 9 projects that use this

  • JimLiuSkill

    paper-narrative

    Judge and reshape the STORY a paper's figures tell. Input is the work itself — manuscript (or abstract) + figure deck — no hand-written brief. `derive_paper_brief(abstract, captions)` extracts pitch/vision/per-figure-claims; a handling-editor reviewer on the full deck returns hook_verdict (would Fig 1 make me send this for review?), arc (hook→mechanism→evidence→application), figure_moves (panels in the wrong figure), missing_panels (concrete analyses to RUN), kill_list, and boldest_defensible_fig1. Hands per-figure claims to `figure-composer`. Load when writing or revising a paper.

    Also in 5 projects that use this

  • Norman-burySkill

    brainstorming-research

    Use before writing any paper - clarifies paper type, discipline, topic, methodology, and chapter structure through natural dialogue

    Also in 4 projects that use this

  • lingzhi227Skill

    latex-formatting

    Handle LaTeX formatting, templates, and styling for academic papers. Set up conference templates (ICML, ICLR, NeurIPS, AAAI, ACL), fix formatting issues, manage packages, and ensure venue-specific compliance. Use when the user needs to set up a paper template, fix LaTeX formatting, or prepare for submission.

    Also in 4 projects that use this

  • lingzhi227Skill

    novelty-assessment

    Assess research idea novelty through systematic literature search. Multi-round search-evaluate loops with harsh critic persona. Binary novel/not-novel decision with justification. Use before committing to a research direction.

    Also in 4 projects that use this

  • +6 more from JimLiu
  • +1 more from lingzhi227

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 72 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.

    line 25
  2. Very specific:

    Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …

    line 27
  3. Distinctive:

    Search the project's reference collection first.

    line 46
  4. Distinctive:

    Verify every cited number against its source.

    line 50
  5. Distinctive:

    Never cite from memory alone

    line 51
  6. Distinctive:

    After scope: confirm questions the review must answer

    line 55
  7. Distinctive:

    After the evidence table: confirm which estimates feed the model

    line 56
  8. Distinctive:

    Every cited number is traceable to a source.

    line 70

“Common” is measured: kept by at least 6 in 10 of the 72 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Generated from .claude/skills/literature-review/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->

/literature-review — Literature Review

Category: Scoping & Design · Primary agent: economic-reasoning-specialist

Reviews the theoretical and empirical literature and existing models in use for a modeling question.

Arguments: whatever the user wrote after the command name.

Purpose

Review the theory, empirical evidence and existing models relevant to a modeling question, so that mechanisms, parameter values and benchmarks are grounded in what is known. The output is an annotated bibliography and an evidence table in which every number is traceable to a verified source and anything unverified is clearly flagged.

Use it when starting a model, choosing calibrations, explaining results, or checking whether a finding is in line with the literature.

Do not use it when a quick orientation is enough and no numbers will be used.

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Topic; document corpus if available (docs/references/) If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
  2. Check confidentiality. Identify the data classification level of the inputs (.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow.
  3. Collaboration. Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and update production/session-state/active.md after each approved section.

Agents

  • economic-reasoning-specialist — primary agent; coordinates the work and integrates results
  • growth-productivity-specialist — Analyzes growth and productivity
  • llm-economic-analyst — Uses LLMs for economic analysis
  • rag-knowledge-specialist — Builds retrieval-augmented knowledge systems over document collections

Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.

Key design decisions (present options, let the user choose)

DecisionTypical optionsWhat it changes
Scopemechanisms, parameter estimates, existing models, policy evidenceFocus of the table
Sourcesproject reference collection, journals, working papersCoverage and reliability
Depthkey references, systematic review, meta-analysisEffort and confidence
Country focusglobal, region, comparable economiesTransferability

Workflow

  1. Search the project's reference collection first; use external sources only where permitted
  2. Summarize the core theoretical mechanisms, standard calibrations and empirical estimates
    • Note sample, method and country for each estimate
  3. List existing models and known strengths and weaknesses
  4. Verify every cited number against its source; mark unverifiable claims clearly
    • Never cite from memory alone
  5. Produce an annotated bibliography and an evidence table

Checkpoints with the user

  • After scope: confirm questions the review must answer
  • After the evidence table: confirm which estimates feed the model

Common pitfalls

  • Citations from memory that turn out wrong
  • Estimates transferred across very different economies
  • Ignoring publication bias in the literature
  • Reviewing only supportive evidence

Output

docs/references/<topic>-review.md

The review contains the annotated bibliography, the evidence table with sample, method and country for each estimate, and flags on unverified items.

Gate / verdict

  • Every cited number is traceable to a source; unverified items are flagged
  • Evidence contrary to the expected result is included

Suggested next steps

  • /model-spec
  • /calibration-plan

Download now (ZIP)

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.