Skip to content
Back to skills

003 Name Skill 10221f10

ASecurity

Ingest a submitted manuscript into plain text (`output/PAPER.md`) so downstream review skills can extract claims with source pointers. **Trigger**: ingest paper, manuscript text, provide paper, paper.md, 输入论文, 导入稿件, 审稿输入. **Use when**: You are running the `peer-review` pipeline and need `output/PAPER.md` before `claims-extractor`. **Skip if**: `output/PAPER.md` already exists and looks like the full manuscript text. **Network**: none. **Guardrail**: Do not summarize or rewrite the paper; stor...

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
researchgo

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 003-name-skill_10221f10 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 003 Name Skill 10221f10?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 003 Name Skill 10221f10
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-003-name-skill-10221f10/badge)](https://www.skillsdirectory.com/skills/tools-only-003-name-skill-10221f10)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
name: manuscript-ingest
description: |
  Ingest a submitted manuscript into plain text (`output/PAPER.md`) so downstream review skills can extract claims with source pointers.
  **Trigger**: ingest paper, manuscript text, provide paper, paper.md, 输入论文, 导入稿件, 审稿输入.
  **Use when**: You are running the `peer-review` pipeline and need `output/PAPER.md` before `claims-extractor`.
  **Skip if**: `output/PAPER.md` already exists and looks like the full manuscript text.
  **Network**: none.
  **Guardrail**: Do not summarize or rewrite the paper; store the raw text (or a faithful extraction) so claims stay traceable.
---

# Manuscript Ingest (paper -> text)

Goal: create `output/PAPER.md` as the single source of truth for the submitted manuscript text.

Downstream skills (e.g., `claims-extractor`) rely on this file to produce *traceable* claims (section/page/quote pointers).

## Inputs

One of the following (choose the simplest):
- The user pastes the manuscript text in chat (recommended).
- A local PDF provided by the user (extract to text, then paste into `output/PAPER.md`).

Optional context:
- `GOAL.md` (review focus / constraints)

## Outputs

- `output/PAPER.md`

## Procedure

1) Decide the input route
- If `GOAL.md` exists, treat it as the review focus/constraints (but do not rewrite the paper to fit it).
- If the user can paste text: use that.
- If only PDF is available: extract text (any faithful extraction is OK; do not paraphrase).

2) Write `output/PAPER.md`
- Include the full text in order.
- Preserve section headings if possible.
- If page numbers are available, keep simple markers like `\n\n[page 7]\n\n` (helps traceability).

3) Quick sanity check
- Confirm `output/PAPER.md` contains the paper body (not just title/abstract).
- Confirm key sections exist (Intro/Method/Experiments/Conclusion), if the paper has them.

## Acceptance

- `output/PAPER.md` exists.
- The file contains the full manuscript text (or a faithful extraction), sufficient to quote with pointers.

## Troubleshooting

### I only have a PDF and the extracted text is messy

Fix:
- Keep the messy text anyway, but preserve:
  - section headings
  - figure/table captions (if present)
  - page separators (if present)

### The paper is very long

Fix:
- Still ingest the full text.
- If you must split, keep `output/PAPER.md` as the concatenated master file.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.