paper-delivery-summary

Renders deterministic paper delivery summaries from verified PDF compilation and citation statistics.

6.8k|540|Updated May 6, 2026
One-click install
npx skills add https://github.com/opensquilla/opensquilla --skill paper-delivery-summary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paper-delivery-summary
Source: https://github.com/opensquilla/opensquilla/tree/main/src/opensquilla/skills/bundled/paper-delivery-summary
Command: npx skills add https://github.com/opensquilla/opensquilla --skill paper-delivery-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It produces a final delivery summary for an automated paper-writing workflow without relying on an LLM, ensuring that reported PDF page counts and citation statistics come only from verified, machine-readable upstream outputs rather than inferred prose.

Core Features & Use Cases

  • Verified PDF Reporting: Parses PDF_PATH, PDF_PAGES, and PDF_TARGET_PAGES markers from compile output and fails closed if they are missing, duplicated, or inconsistent.
  • Citation Summary Validation: Requires a complete, internally consistent citation SUMMARY line (total, strong, ok, weak, invalid, unused) before rendering any statistics.
  • Bilingual Output: Renders the delivery note in Chinese or English based on the confirmed paper language contract, with a neutral fallback for other languages.
  • Use Case: After an automated paper-writing pipeline compiles a PDF and maps citations, this formatter emits the final user-facing delivery message with exact page counts, citation quality breakdown, and warnings about weak or unused references.

Quick Start

Run the render script with a JSON payload containing the paper contract, language instruction, compile_pdf output, and citation_map output to print the verified delivery summary.

Frequently Asked Questions about paper-delivery-summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a paper delivery summary from compile output?

Pipe a JSON object with paper_contract, language_instruction, compile_pdf, and citation_map fields into the render script via stdin. The script prints a formatted summary with the PDF path, page counts, and citation statistics, exiting with code 0 on success.

What input format does the citation summary validation require?

The citation_map output must contain exactly one SUMMARY line with all six fields: total_cite_keys, strong, ok, weak, invalid, and unused as non-negative integers. The classified counts must add up to total_cite_keys or the render fails.

Does the delivery summary support Chinese and English output?

Yes, the renderer selects Chinese or English text from the LANGUAGE marker in the paper contract, cross-checked against the runtime language instruction. Other language codes fall back to a neutral symbol-based format.

Why does the delivery summary fail with a blocked error?

Rendering fails closed when PDF markers are missing or duplicated, PDF_PATH is not absolute, page counts violate target constraints, or the citation SUMMARY is incomplete or inconsistent. The error message is printed to stdout and stderr with exit code 2.

Can this formatter estimate page or citation counts from prose?

No, the formatter never calls an LLM and never infers counts from prose. It only reports values parsed from exact machine-readable markers produced by the compile and citation-map steps.