anything-to-journal
AGENT SKILL / MANUSCRIPT WORKFLOW

Anything in.
Journal out.

Drop every source into one folder. Your agent builds the LaTeX, PDF, references, audit, and submission files—then opens a local workspace for the final edit.

Start with a folder ↗Read the docs →
New in v1.2.0 · Trace a PDF result to its source
01 / INSTALL

One command to begin.

Run it yourself, or copy one prompt and let your agent handle installation or updates.

Already installed? Use the update command.

Requires Node.js 18 or newer. The default target is ~/.codex/skills/anything-to-journal.

02 / SOURCE WORKSPACE

One folder is the interface.

No form builder. No import ritual. Keep the full research context together.

anything-to-journal / workspaceREADY
FRESH WORKSPACE

Put every useful source in one new folder.

Notes, PDFs, tables, figures, references, transcripts, drafts—keep the context together. Before opening the content, the agent asks which output mode you want.

INPUT / 6 ITEMS•••
my-research/
field-notes.md
results.xlsx
interviews.pdf
figures/
references.bib
agent reads everything in context
AGENT INTAKEMODE CONFIRMEDMANUSCRIPT PACKAGED
03 / WORKFLOW

From source pile to final edit.

Four explicit steps. One real manuscript shared by the agent and the local editor.

01ASSEMBLE

Start with a fresh folder.

Create one clean workspace and put every relevant source inside. Mixed formats are expected.

02CONFIRM

Choose draft or template.

Before reading the sources, the agent confirms a flexible draft or a manuscript matched to a supplied venue template.

03GENERATE

Build the complete paper.

Anything-to-Journal produces editable LaTeX, a compiled PDF, references, audit reports, and submission files.

04REFINE

Finish in one workspace.

Edit the same LaTeX through Codex or by hand. Save, recompile, and watch the PDF preview update automatically.

04 / MODE GATE

The agent asks
before it reads.

Format is a deliberate choice, never a silent guess. The workflow pauses before source content is opened until draft mode or a specific journal target is confirmed.

ADEFAULT

Journal draft

A clear, portable manuscript structure for review, iteration, and choosing a venue later.

  • Standard article sections
  • Readable LaTeX sources
  • Conservative dependencies
Use draft mode →
BTARGETED

Specific template

A manuscript aligned to the supplied journal class, example article, and submission requirements.

  • Uses journal-provided files
  • Preserves required structure
  • Records compiler instructions
Add a template →
05 / MANUSCRIPT WORKSPACE

NEW IN v1.2.0

Read a result. See its source.

Review the PDF with reference nodes beside recorded terms, numbers, and figure or table captions. Open a node to inspect the source file and its recorded location, then keep editing the real LaTeX in the same local workspace.

  • Click a reference beside a result such as accuracy 0.9.
  • See the file, page or line, and yellow-highlighted source text.
  • Compare multiple sources; missing or ambiguous locations stay explicit.
  • PDF.js ships with the skill and loads locally, without a CDN.
  • Codex and manual LaTeX edits stay synchronized with the PDF preview.

Precise highlights need recorded source locations. Scanned PDFs use recorded regions; no automatic OCR.

Explore source references →
Keep editing in Codex chatOpen the same URL in any browser

LOCALHOST ONLY · NO CLOUD UPLOAD

127.0.0.1:43127LOCAL
manuscript.texjournal-output / manuscript
SAVED
INTERACTIVE EXAMPLE · Click the reference beside 0.9
RESEARCH ARTICLE

Evidence-Aware
Manuscript Workflows

A. Researcher · B. Collaborator

3. Results

The model achieved a held-out accuracy of 0.9.

1
2
WATCHING EXTERNAL CHANGESPDF IN SYNC
06 / OUTPUT

A manuscript you still own.

Every major section stays legible. Figures remain replaceable, citations stay in a bibliography file, and the editor works on the actual generated source.

01Editable source
02Compiled PDF
03Upload-ready ZIP
04Local workspace
DELIVERABLES / FINALEDITABLE
OVERLEAF ROUTENew Project → Upload Project

Choose submission/overleaf-upload.zip. main.tex is already at the ZIP root.

07 / HANDOFF

One ZIP.
Straight to Overleaf.

1

Open Overleaf and choose New Project.

2

Select Upload Project.

3

Upload submission/overleaf-upload.zip.

Open the Overleaf guide ↗
08 / FAQ

Questions, resolved.

01What can I put in the source folder?

Anything that helps explain the work: PDFs, notes, Word files, spreadsheets, CSV data, figures, transcripts, citations, code, earlier drafts, and journal instructions.

02Do I need to organize everything first?

No. Clear names help, but the skill is designed to inspect mixed material. Keep the folder dedicated to one manuscript and exclude secrets or unrelated files.

03How do I update the skill?

Run npx --yes anything-to-journal@latest update. The updater verifies the existing skill, stages the newest published release, and replaces the old copy safely.

04Does every result get a verified source automatically?

Reference nodes use evidence recorded for the manuscript. They can point to multiple source files, but a highlight only locates evidence; you still assess whether it supports the claim. Missing or ambiguous locations are shown for review. Existing evidence maps remain usable and can be enriched with precise locators.

05Can I edit the manuscript in Codex and by hand?

Yes. Both routes edit the same generated LaTeX files. The workspace detects external changes, recompiles after saved edits, and refreshes the PDF preview.

06What happens if LaTeX compilation fails?

The workspace shows the compile error and keeps the last successful PDF available, so a broken edit never destroys the usable preview.

07Can I still use Overleaf?

Yes. Upload journal-output/submission/overleaf-upload.zip using New Project → Upload Project. The local workspace is an additional editing option, not a replacement for the existing handoff.

READY / WHEN YOU ARE

Make a folder.
Make it a journal.

Generate the full manuscript, then keep refining it in Codex, the local workspace, or Overleaf.

Get started ↗