Skip to content
Back to search

scientific-paper-skill

A Claude Code skill to write scientific papers from the author's own materials, with every reference and number checked

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 21 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/javimarlop/scientific-paper-skill with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/javimarlop/scientific-paper-skill'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/javimarlop--scientific-paper-skill/badge.svg)](/listings/javimarlop--scientific-paper-skill)

HTML

<a href="/listings/javimarlop--scientific-paper-skill"><img src="/api/listings/javimarlop--scientific-paper-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Copy the folder `scientific-paper/` to where Claude Code looks for skills:

git clone https://github.com/javimarlop/scientific-paper-skill.git
# for you, in every project:
cp -R scientific-paper-skill/scientific-paper ~/.claude/skills/
# or only for one project, shared with its team through the repository:
cp -R scientific-paper-skill/scientific-paper /path/to/project/.claude/skills/

Then ask in Claude Code, for example: *"ayúdame a escribir el artículo con los resultados de esta carpeta"* or *"write the discussion of this paper"*. It loads by itself when the request is about writing, restructuring or reviewing a paper.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 70 lines
  1. # scientific-paper
  2. A skill for [Claude Code](https://claude.com/claude-code) that helps write a scientific article in **ecology** (and
  3. related fields: conservation, biogeography, environmental science, remote sensing of ecosystems) **from the author's
  4. own materials** (idea, field or remote-sensing data, results, figures, notes), in stages and with every claim, number
  5. and reference checked.
  6. The author knows the science; the skill organises, drafts and checks. Its rules:
  7. - **Never invents** a reference, DOI, number or result: what is missing is a `[TODO]` for the author.
  8. - **Every reference is verified** against Crossref and DataCite (`scripts/check_dois.py`).
  9. - **Every number has a source**, listed in `NUMBERS.md` and checked against the final text.
  10. - Claims that go beyond the data are **marked**, and the author decides.
  11. - Nothing is sent or published; the authors answer for the text.
  12. ## Stages
  13. 0. Intake (question, contribution, target journal, materials) → 1. Outline of the argument → 2. Literature, verified →
  14. 3. Draft section by section → 4. Figures and tables, from the author's scripts → 5. Consistency pass (`REVIEW.md`) →
  15. 6. Journal template and submission checklist. Also: replies to reviewers.
  16. It carries what ecology reviewers look at (pseudoreplication, scale, sampling, spatial autocorrelation, effect sizes,
  17. model validation, taxonomy, data and code archiving, permits, sensitive locations, PRISMA for reviews) and where to
  18. find the **LaTeX and Word templates** of the main publishers and societies (Elsevier, Springer Nature, Wiley with BES
  19. and ESA, MDPI, Frontiers, PLOS, Taylor & Francis, Copernicus) with links to their instructions and to Overleaf.
  20. ## Install
  21. Copy the folder `scientific-paper/` to where Claude Code looks for skills:
  22. ```bash
  23. git clone https://github.com/javimarlop/scientific-paper-skill.git
  24. # for you, in every project:
  25. cp -R scientific-paper-skill/scientific-paper ~/.claude/skills/
  26. # or only for one project, shared with its team through the repository:
  27. cp -R scientific-paper-skill/scientific-paper /path/to/project/.claude/skills/
  28. ```
  29. Then ask in Claude Code, for example: *"ayúdame a escribir el artículo con los resultados de esta carpeta"* or *"write
  30. the discussion of this paper"*. It loads by itself when the request is about writing, restructuring or reviewing a
  31. paper.
  32. ## What is inside
  33. | File | What |
  34. |---|---|
  35. | `scientific-paper/SKILL.md` | The rules and the stages |
  36. | `scientific-paper/references/structure.md` | Structure of a paper and the argument check |
  37. | `scientific-paper/references/literature.md` | Finding, verifying and citing the literature |
  38. | `scientific-paper/references/style.md` | Style of scientific writing, numbers and units |
  39. | `scientific-paper/references/latex.md` | Working with a template: LaTeX, Word, figures, units |
  40. | `scientific-paper/references/ecology.md` | Design, statistics, data, ethics and reporting in ecology |
  41. | `scientific-paper/references/templates.md` | Where to find the template and instructions of each journal and publisher |
  42. | `scientific-paper/scripts/check_dois.py` | Checks DOIs against Crossref and DataCite (needs only Python 3 and a network) |
  43. | `scientific-paper/scripts/checklist.md` | Checklist before submitting |
  44. `check_dois.py`: `python scientific-paper/scripts/check_dois.py 10.1016/j.rse.2017.06.031` or `--bib refs.bib`. It
  45. asks only for the public metadata of the DOI; read the title, authors and year it returns, because a DOI that
  46. resolves to another paper is as wrong as one that does not resolve.
  47. ## Not
  48. This is not an automatic paper generator: it does not write a paper from nothing, and it does not replace the authors'
  49. judgement. For a multi-agent pipeline that does, see
  50. [PaperOrchestra](https://github.com/google-research/paper-orchestra) (it needs API keys of other providers and is
  51. aimed at AI conferences).
  52. ## Licence
  53. Apache License 2.0 (see `LICENSE`).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.