AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

scientific-writing

Drafts, revises, and audits scientific manuscripts or reports with explicit evidence provenance, reporting-guideline coverage, authorship accountability, confidentiality controls, and local consistency checks. Use for manuscript sections, references, declarations, tables, figures, or submission preparation when scientific accuracy and traceability matter.

Original source
K-Dense-AI
License
MIT
Pinned revision
5f2bc0341354fd5590aef76a533ada1e1e5b4e62

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read k-dense-ai--scientific-writing at revision 5f2bc0341354fd5590aef76a533ada1e1e5b4e62, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 15

references/journal_policies.md

Journal and Publisher Policy Review

Generic guidance never overrides the target journal's current instructions.

Capture a dated policy record

Before drafting and again before submission, record:

  • journal, article type, and policy URL;
  • date accessed;
  • word, abstract, reference, table, figure, and supplement limits;
  • required structure and reporting guideline;
  • registration, protocol, and analysis-plan requirements;
  • ethics, consent, participant privacy, and image requirements;
  • authorship, contributor, acknowledgment, and change-of-authorship rules;
  • funding, conflicts, and sponsor-role disclosures;
  • data, code, materials, and repository policies;
  • preprint, prior dissemination, duplicate submission, and copyright policies;
  • AI use by authors and any restrictions on external tools;
  • peer-review model and confidentiality;
  • file, accessibility, and submission-system requirements.

Do not guess an absent policy. Ask the journal or leave the decision unresolved.

Official examples

  • JAMA's current Instructions for Authors illustrate article-type-specific requirements and should be consulted directly for a JAMA submission [SW-S25].
  • JAMA's AI guidance illustrates author disclosure, human responsibility, and confidentiality limits for peer review [SW-S24].
  • Nature Portfolio's reporting and availability policy illustrates venue requirements for data, materials, code, protocols, restrictions, and access [SW-S22].
  • Nature Portfolio's authorship policy illustrates publisher-specific accountability and contribution statements [SW-S23].
  • PLOS Biology's data policy illustrates how sharing expectations interact with consent, privacy, legal, ethical, and sensitive-data restrictions [SW-S26].

JAMA's live instructions prohibit AI/LLM drafting of Opinion manuscripts, Letters to the Editor, and Online Comments, and advise against AI generation or formatting of references; standard reference managers may be used [SW-S25]. A disclosure does not make a prohibited use permissible. Check article-type restrictions at intake, before drafting. These restrictions are not universal publisher rules.

These are examples, not defaults for other journals. Publisher-level policy and journal-level instructions may both apply.

Submission review

Perform a manual comparison against the live instructions:

  1. Select the exact article type.
  2. Confirm the latest reporting guideline and extensions.
  3. Verify every required statement from source records.
  4. Confirm whether checklists or flow diagrams must be uploaded.
  5. Confirm data, code, and materials deposits actually exist and are accessible as stated.
  6. Confirm author order, corresponding author, CRediT roles, and approvals.
  7. Confirm AI-use disclosure wording and location with the human authors.
  8. Verify files, anonymization, accessibility, permissions, and metadata.
  9. Save the access date and policy URLs in the submission record.

Passing local tools does not establish venue compliance.