agentleFS
Xuzhen-LiXuzhen-Li/literature-review-skills/skills/exemplar-review-analysis/SKILL.md

exemplar-review-analysis

Skill2 starsChanged 35 days agoMITView on GitHub

Reads 3 to 5 recent reviews the user can legally open and writes a style brief: structure, section length, figure count, citation density, and tone. Trigger on "style brief", "exemplar reviews", "match the journal's reviews", or "how are reviews structured here". Do not use it to copy their prose, and do not use it before the included papers have notes.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user cannot supply three PDFs, stop and ask.

    line 31
  2. Very specific:

    Ask the user for 3 to 5 reviews (DOI or PDF).

    line 35
  3. Very specific:

    Write 06-exemplars/style_brief.md from the template.

    line 45
  4. Very specific:

    After journal_lock, and again only if the user asks to refresh from the included set, follow references/journal_refresh.md.

    line 47
  5. Distinctive:

    Do not download an exemplar from an unauthorized copy.

    line 68
  6. Distinctive:

    Do not treat an exemplar's citations as papers you have read.

    line 69
  7. Very specific:

    Do not adopt an exemplar's claim.

    line 70
  8. Very specific:

    Do not set journal_lock because several exemplars share a journal.

    line 71
  9. Distinctive:

    Do not rank exemplar or included papers by an impact factor, a citation count, or a partition you did not open that day.

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Exemplar review analysis

Opening

On first use in a project, say this verbatim:

I am exemplar review analysis. I describe the structure of reviews you can open, and I refresh that brief after the journal lock.

When to use

Every included record has a reading note or a logged skip, and either 06-exemplars/style_brief.md does not exist yet or journal_lock is true and that brief still says Refreshed after journal lock: no. The user wants the outline skill, and later the polishing skill, to inherit a structure, not a paraphrase of someone else's review.

Inputs (paths) / Preconditions

  • <project>/project.yaml — target_journal and review_type.
  • <project>/00-scope/scope_report.md — locked question, so exemplars can be judged for relevance.
  • Three to five review PDFs the user already has legal access to, ideally from the target journal and published within the last five years. If target_journal is undecided, use reviews in the same field and mark the venue as provisional.
  • Template: references/style_brief_template.md.

If the user cannot supply three PDFs, stop and ask. Do not select stand-in papers from memory and pretend they were read.

Procedure (numbered steps)

  1. Ask the user for 3 to 5 reviews (DOI or PDF). Record the DOI only as printed on the PDF. If it is unreadable, [VERIFY].
  2. For each PDF, count rather than estimate:
    • word count of the body, excluding references, or [VERIFY] if the PDF text layer is unusable (ask the user for the count)
    • heading list, in order
    • word count per major section, or [VERIFY]
    • number of figures and number of tables
    • number of citations in the reference list
    • citation density: citations per 1000 body words, rounded to one decimal, and only when both counts are numbers you calculated
  3. Describe the pattern across the set in your own words: where the gap sentence sits, whether a methods section exists, how long the conclusion is relative to the body, and the grammatical person (this review versus we). Do not quote more than a short clause, and do not quote it if you can describe the pattern without it.
  4. Note what not to copy: their sentences, their figures, their reference list, and any table that is a published data compilation.
  5. Write 06-exemplars/style_brief.md from the template. The "Implications" section is a constraint list for review-outline-builder (section order, a starting word budget, a figure budget). It is not an outline of this review's claims.
  6. Append YYYY-MM-DD | exemplar-review-analysis | style brief from <N> reviews | agent. Leave Refreshed after journal lock: no unless the journal is already locked. In that case, write the brief as the post-lock refresh in references/journal_refresh.md instead of a second file.
  7. After journal_lock, and again only if the user asks to refresh from the included set, follow references/journal_refresh.md. Do not pick exemplars by an impact factor or any metric you did not open that day. User-supplied lawful PDFs stay the only source.

Human gate(s)

No project lock. If fewer than three exemplars were actually opened, do not write the brief. Ask the user for another PDF or for permission to proceed with the ones opened; if they accept fewer than three, record that in LOG.md (style brief based on <N> reviews | human) and state the limit in the brief.

Outputs (exact paths + formats)

  • 06-exemplars/style_brief.md — sections in references/style_brief_template.md.

Quality checklist

  • Each exemplar row has a year and a venue taken from the PDF, or [VERIFY].
  • Word counts, figure counts, and citation counts are calculated or [VERIFY], never a round number offered as a memory.
  • Citation density is blank when either input count is [VERIFY].
  • The brief contains no paragraph copied from an exemplar.
  • Implications name a word budget, a heading pattern, an abstract shape, and a figure budget. Before journal lock they are a starting point. After the refresh they are the pattern polishing must follow.
  • The post-lock brief names the locked journal and says Refreshed after journal lock: yes.

Guardrails

  • Do not download an exemplar from an unauthorized copy.
  • Do not treat an exemplar's citations as papers you have read. They are not added to the evidence table here.
  • Do not adopt an exemplar's claim. Claims come from evidence/evidence_table.csv.
  • Do not set journal_lock because several exemplars share a journal.
  • Do not rank exemplar or included papers by an impact factor, a citation count, or a partition you did not open that day.

Next step

review-outline-builder when the journal is not locked yet. manuscript-polishing after the post-lock refresh.

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.