agentleFS
ChangChrisLiuChangChrisLiu/academic-writing-audit/skills/related-work-synthesis/SKILL.md

related-work-synthesis

Skill4 starsChanged 31 days agoMITView on GitHub

Draft or revise a literature review as a source-supported narrative that develops the introduction's research question. Use for paper lists, artificial taxonomies, disconnected method families, or repeated self-comparison; preserve citation and LaTeX or Word conventions.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Related Work Synthesis

Explain the relevant literature through the problem the introduction has established. Synthesize what prior studies did and found, and how they connect, in concise paragraphs.

Establish the question and sources

Read the introduction or supplied research question before organizing the review. Identify the direction, established progress, and specific unresolved issue. If the introduction is unavailable, build only a provisional organization from the supported question and state the missing context. Do not invent the paper's gap from a method name.

During explicitly requested early investigation, treat that question and its gap as provisional. Read recent relevant introductions and related work for framing, then inspect consequential methods, findings and original cited sources. Consider foundations, closest prior solutions and counterevidence, and let them revise the introduction's story before fixing the review's progression. Do not filter the literature to validate a predetermined gap. A finished review follows the resulting argument; it need not preserve the initial hypothesis. Distinguish discovery, bibliographic identity, methodological appraisal and claim support. Search only when authorized or needed for the requested task, and preserve the actual access limits.

Distinguish full papers, abstracts, excerpts, source cards, and earlier summaries. Check each claim against the source actually available. A source that does not mention a property establishes unknown, not absent. Do not fabricate references, author names, dates, missing capabilities, or exhaustive priority claims.

Develop the literature argument

Start from the question the introduction has made consequential and identify what the reader should understand from the cited work. Order scientific points so each prepares or qualifies the next. Do not first choose a number of directions, assign papers to categories, or turn a source matrix into manuscript prose. A long review may use substantive headings when they help the argument or the format requires them; connected prose remains the default, with a reason for each transition across paragraphs or headings.

Explain the relevant question, scientific operation and supported finding of prior work. Synthesize sources that support the same point and distinguish findings whose conditions matter. Establish the relationship before saying that one work extends, builds on or replaces another. A shared topic or citation does not establish intellectual dependence, a common mechanism or a linear history. Do not group datasets, systems, training rules and interfaces under a predicate they do not all satisfy. Preserve distinctions needed for accuracy while connecting them through the research question. Author chronology, one paragraph per paper and a sequence of method-family descriptions are weak defaults even without headings or bullets.

Differences among prior studies can illuminate their relationship. Comparisons with the present paper are not the default literature narrative. Do not end each paragraph with our method overcomes this limitation or replay the current method. Keep present-paper positioning in the introduction or discussion. If the author explicitly requests a current-paper comparison or novelty audit, provide it as that bounded task and distinguish difference from demonstrated superiority.

Explain prior contributions in their own studied settings. Do not organize paragraph endings around what those studies did not establish for this paper's task; that is still a current-paper comparison even without the word our. Include a limitation when it is needed to interpret the prior finding itself, rather than to advertise the present study's gap. Put unresolved source-coverage notes outside the manuscript passage when they do not affect its scientific meaning.

A small working source-to-claim map may help the editor; its labels are planning aids, not a required structure for the manuscript. A small source set cannot establish first, only, or no prior work, and an unreported property must remain unresolved.

Treat supplied sources as candidates, not a coverage checklist. Include a study when it establishes, qualifies or challenges a point the review needs. If a transition has only a broad topical connection, narrow the passage or omit the tangential study rather than invent a stronger relationship. Keep consequential counterevidence even when it complicates the story; narrative focus is not permission to select only favorable findings. Explain a material scope choice outside the passage when needed.

Write and format the synthesis

Give each paragraph a scientific point, the sources supporting it, and a connection to the next point. Put citations beside the propositions they support. Split claims with different source support when needed. Preserve accurate author-approved prose instead of forcing every review into the same shape.

When adding, returning or validating BibTeX, use each intended publication's actual Google Scholar Cite → BibTeX entry verbatim, with its exported key. Retain its provenance and check identity against primary records through the two independent verifiers. Missing export or unresolved identity leaves the reference pending outside the prose. Preserve existing citation markers during a prose-only edit. Never synthesize BibTeX from source cards, DOI metadata or memory.

In LaTeX, preserve the existing section commands, citation commands and keys, labels, and bibliography system. In Word, use the supplied citation style and native heading and paragraph styles when editing a document; preserve reference-manager fields. Paste-ready Word prose should not contain Markdown heading marks, LaTeX commands, or invented bibliographic details. Claim compilation or rendered layout checks only when performed. Author or venue requirements govern headings and formatting.

Worked example

A fictional introduction asks how to obtain informative crop observations and combine records of differing quality. Source A describes targeted follow-up sampling after anomalous readings. Source B aligns observations recorded at different times. Source C weights aligned measurements by sensor calibration quality. Their findings are supplied as excerpts, not full papers.

A coherent synthesis can connect targeted acquisition to the integration of heterogeneous records. It explains the operation and supported result of each line of work and why alignment and quality weighting address different properties of observations. It does not create historical and interactive camps or add a final sentence claiming that the present system uniquely combines the ideas. Unreported capabilities remain unknown.

Prose when drafting or revising

When drafting or revising prose, including audit explanations, read prose editing rules. Preserve scientific meaning, necessary reasoning and valid technical terms. Keep sound passages, do not add unreported properties, and limit edits to the requested scope. The local reference covers concept accuracy, clear sentences, repetition and punctuation, including the required exceptions.

Deliver and stop

Return the requested literature passage or located audit findings, with material source uncertainties outside the passage. Prefer concise connected prose to a paper catalogue or classification list. Preserve accurate prior-work explanations and stop when the permitted sources support the narrative. Do not expand into an unsolicited search, method rewrite, or new study.

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.