eda-pdf-local-summary

Summarize local PDFs into structured notes with page-level citations.

8|3|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Mr-Fang-VLSI/EDAgent --skill eda-pdf-local-summary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eda-pdf-local-summary
Source: https://github.com/Mr-Fang-VLSI/EDAgent/tree/main/skills/eda-pdf-local-summary
Command: npx skills add https://github.com/Mr-Fang-VLSI/EDAgent --skill eda-pdf-local-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires grobid_client, lxml, pypdf, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables researchers to convert local PDF papers into structured, citation-grounded evidence notes, preserving page-level traceability for methods, assumptions, results, and limitations.

Core Features & Use Cases

  • Extract and organize key claims, experimental details, and hypotheses from local PDFs.
  • Map evidence to current EDA hypotheses and generate reusable summary notes stored under docs/papers/summaries.
  • Preserve provenance by including page references and references sections.

Quick Start

Provide the path to a local PDF to generate a structured, citation-grounded summary.

Frequently Asked Questions about eda-pdf-local-summary

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

FAQPage Schema
How do I summarize a local PDF into structured research notes?

To summarize local PDFs, provide the file path and the Skill extracts methods, assumptions, results, and limitations into structured Markdown notes with page-level citations.

How does page-level citation work when extracting evidence from PDF papers?

Page-level citation works by mapping extracted claims, experimental details, and hypotheses to specific page numbers in the PDF, ensuring provenance and traceability for research evidence.

Can I use GROBID to extract methods and results from local PDF files?

Yes, the Skill orchestrates extraction via GROBID to parse local PDFs, with a local fallback mechanism using pypdf if the GROBID client is unavailable.

Do I need a GROBID server running to extract assumptions and limitations from PDFs?

No, a running GROBID server is not strictly required because the Skill includes a local fallback using pypdf to extract structured evidence if GROBID client extraction fails.

What is the best way to map extracted paper evidence to current EDA hypotheses?

The best way to map evidence to EDA hypotheses is using this Skill to extract key claims from local PDFs and automatically align them with current hypotheses in the generated summary notes.

What happens to the Markdown summaries and manifest after processing local PDFs?

The Skill outputs a Markdown summary plus an updated manifest, storing reusable citation-grounded notes under docs/papers/summaries for subsequent knowledge management.