knowledge-extraction

Extract structured entities, relations, claims, and evidence from academic papers into KnowledgeItem JSON.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill knowledge-extraction-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-extraction
Source: https://github.com/yakeworld/Synthos/tree/main/skills/core/knowledge-extraction
Command: npx skills add https://github.com/yakeworld/Synthos --skill knowledge-extraction-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reading academic papers and manually converting them into structured, traceable knowledge records is slow and error-prone. This Skill turns a single paper's full text or abstract into a structured KnowledgeItem JSON with provenance-linked entities, relations, claims, and evidence, ready for downstream research pipelines. ## Core Features & Use Cases - Four-Domain Extraction: Decomposes each paper into entities, relations, claims, and evidence, with every item anchored to its source sentence and section/figure/table location. - Confidence Grading: Classifies every claim as stated, suggested, or speculated so author speculation is never mistaken for established fact. - Quality Scoring: Applies a six-dimension weighted rubric (gap significance, methodological soundness, result completeness, clinical translation, reproducibility, narrative quality) with a 0.70 pass threshold. - PW-Bench Reverse Engineering Mode: Optionally reconstructs a paper's research design as sparse/dense idea documents and experimental logs for benchmark creation. - Use Case: After acquiring a set of papers on ADHD eye-tracking research, run this Skill on each paper to produce structured JSON records with methodology classification, key findings, limitations, and evidence chains for downstream association discovery. ## Quick Start Extract structured knowledge from the attached paper PDF and save the KnowledgeItem JSON with entities, relations, claims, and evidence.

Frequently Asked Questions about knowledge-extraction

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

FAQPage Schema
How do I extract structured knowledge from a research paper PDF?

Load the PDF with markitdown to preserve tables and headings, falling back to pdftotext -layout if that fails. Then extract four domains: entities, relations, claims, and evidence, each with provenance pointing to the source sentence and section, and save the result as a KnowledgeItem JSON.

What is the difference between markitdown and pdftotext for PDF extraction?

markitdown converts PDFs to Markdown, preserving table structure and heading hierarchy, which makes evidence extraction and section labeling more accurate. pdftotext -layout is the fallback for scanned, encrypted, or oversized PDFs where markitdown produces empty output.

Can this skill compare findings across multiple papers?

No. It strictly processes one paper at a time. Cross-paper comparison, contradiction detection, and association discovery belong to the downstream association-discovery atom, keeping single-paper extraction free of cross-paper contamination.

How are author opinions separated from factual findings in extraction?

Every claim is labeled with one of three confidence levels: stated for explicit assertions, suggested for implied findings, and speculated for author hypotheses. This prevents author speculation from being recorded as established literature fact.

What happens when a paper has no abstract or the PDF cannot be parsed?

For papers with no abstract, the skill records findings as 'Abstract not available' with methodology set to unspecified instead of failing. If both markitdown and pdftotext yield no text, the paper is flagged as unextractable rather than fabricating content.

What is the PW-Bench reverse engineering mode used for?

It reconstructs a published paper's research design as sparse or dense idea documents plus an experimental log, excluding actual results. This creates benchmark cases for evaluating how research pipelines respond to underspecified inputs.