Paper Ingest Normalizer

v1.0.0

Normalize papers, PDFs, URLs, and literature notes into structured research records for project memory and retrieval. Use when: (1) a new paper, PDF, DOI, or...

0· 50·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the requested inputs and outputs: it asks for PDFs, URLs, raw text, or metadata and specifies a structured schema and writeback behavior. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions stay within the paper-normalization scope (extract text from PDF/URL/text, parse bibliographic and research fields, assemble record). It correctly warns not to write to project memory without project_id. Note: it relies on access to local PDF paths or URLs — giving the agent those paths/links grants it access to those documents, so users should avoid supplying sensitive files unless intended.
Install Mechanism
Instruction-only skill with no install spec or code files. It suggests using pdfplumber/PyMuPDF or a separate 'summarize' skill for extraction, which is appropriate and low-risk for an instruction-only skill.
Credentials
No environment variables, credentials, or config paths are requested; the declared inputs (pdf_path, url, raw_text, project_id) are proportionate to the task.
Persistence & Privilege
Does not request always:true and does not change other skills or system-wide settings. The documented rule to never write without project_id reduces risk of unintended persistence.
Assessment
This skill appears to do what it claims: normalize literature into structured records and avoid writes unless project_id is provided. Before installing/using: (1) only supply PDFs or URLs you want the agent to read (do not give sensitive files), (2) confirm the agent has access to any external 'summarize' skill or PDF libraries it will call and that you trust those components, and (3) verify writeback behavior in a safe test project to ensure records are written only when writeback_ready is true and project_id is set.

Like a lobster shell, security has layers — review code before you run it.

latestvk979tpsfsd8am7bd5mywjg0xhs83p1rf

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments