summary

Summary

Compose a concise structured summary of one paper and register it as a child note under the matching Zotero item.

When to invoke

Invoke this skill when the user provides one of the following and asks for a summary:

• A PDF path on disk.
• A paper title or citation key already present in the user's Zotero library.

If the user explicitly asks for a deeper lesson, derivation, or pin-point analysis, call pinpoint-lesson instead.

Invocation schema

Use:

/summary <PDF-path | Zotero-paper-title | citation-key> [language: <language>]

Examples:

/summary /path/to/paper.pdf
/summary "Paper title already in Zotero" language: Korean
/summary @citationKey language: Japanese

Language resolution:

1. If language: <language> is present, use that language for the note body.
2. Otherwise, if the user's request contains natural-language instructions, use that request language.
3. Otherwise, default to English.

Pipeline

1. Identify the target Zotero item.
   • For a PDF path: verify the file exists, then locate the existing parent item via the zotero-mcp server. If the PDF is not in Zotero yet, prompt the user to add it.
   • For a title or citation key: search via zotero-mcp.
2. Extract evidence from the PDF.
   • Run scripts/prepare_pdf_artifacts.py <pdf> --out <work-dir> --render-pages.
   • Use pdftotext output as the primary text source.
   • Use images/figure-NNN.png for raster figures and pages/page-NNN.png for vector figures.
3. Read existing Zotero context: title, abstract, tags, attachments, child notes. Do not duplicate an existing summary unless the user wants a replacement.
4. Compose the summary in Markdown following the structure below.
5. Run the summary quality check below before registration.
6. Register the note via scripts/zotero_register_note.py to the local plugin endpoint http://localhost:23119/aisummary/note.

Note structure

The note is a single Markdown file with these sections, in order. Use plain prose. Do not pad with section headers that have no content.