paper-analyzer

Synthesize module documentation into structured evidence and analysis files.

Updated Nov 25, 2025
One-click install
npx skills add https://github.com/NikhilVijayakumar/Yantra --skill paper-analyzer-nikhilvijayakumar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paper-analyzer
Source: https://github.com/NikhilVijayakumar/Yantra/tree/main/.agent/skills/paper-analyzer
Command: npx skills add https://github.com/NikhilVijayakumar/Yantra --skill paper-analyzer-nikhilvijayakumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synthesizes documentation across Amsha, Yantra, Bodha, and cross-module plans into structured evidence and models.

Core Features & Use Cases

  • Targeted Reading: Reads only files listed in the YAML plan's data_sources section to avoid data leakage.
  • Evidence Synthesis: Extracts specific facts, models, dependencies, and diagrams (LaTeX, Mermaid) from multiple module layers and compiles them into a raw analysis document.
  • Use Case: When drafting cross-library research, generate a consolidated analysis that can feed into the drafting and review stages.

Quick Start

Provide the YAML plan at docs/paper/Yantra/drafts/plan/plan_[section_name].yaml and run the analyzer to produce analysis_[section_name].md.

Frequently Asked Questions about paper-analyzer

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

FAQPage Schema
How do I synthesize documentation from multiple libraries into a single research analysis?

Documentation synthesis is performed by extracting specific facts, models, and diagrams from multiple module layers and compiling them into a raw analysis document. This process requires a YAML plan to define the exact data sources and output structure.

How do I extract evidence and models from cross-module YAML plans?

Evidence extraction from YAML plans is executed by reading only the files listed in the plan's data_sources section. The analyzer then compiles extracted dependencies, LaTeX equations, and Mermaid diagrams into a structured markdown analysis document.

Does the documentation analyzer preserve LaTeX equations and Mermaid diagrams during data extraction?

Yes, data extraction strictly preserves LaTeX equations and Mermaid diagrams found within the source documentation. This ensures mathematical models and visual flows remain intact when compiled into the final raw analysis markdown file.

What is the best way to avoid data leakage when analyzing cross-library research documentation?

Targeted reading is the best approach to avoid data leakage, ensuring the analyzer reads only files explicitly listed in the YAML plan's data_sources section. This prevents unapproved documents from influencing the synthesized evidence models.

What are the file path requirements for generating a drafted analysis document?

Generating a drafted analysis document requires providing a YAML plan at docs/paper/Yantra/drafts/plan/plan_[section_name].yaml. The output analysis file is then generated at docs/paper/Yantra/drafts/details/[N]. [Section Name]/analysis_[section_name].md.