Skip to content

2654400439/Paper2Seminar / skills/paper-ppt-orchestrator

paper-ppt-orchestrator

Verified

Build complete fixed-layout academic-paper presentations from a PDF with bundled PPTX and one-page HTML templates. Use for full paper reading, complexity-aware slide budgeting, subsection coverage mapping, figure extraction, TikZ or Matplotlib evidence visuals, deterministic PPTX assembly, and final QA. Trigger for requests to turn a paper PDF into a discussion-group deck, especially 12-16+ page systems, security, networking, or measurement papers.

FileKindSize
SKILL.mdskill md17.9 KB
agents/openai.yamlconfig296 B
assets/one-page-summary.htmlother7.8 KB
assets/seminar-template.pptxbinary572.7 KB
references/content-design.mdmarkdown5.7 KB
references/data-viz.schema.jsonconfig2.9 KB
references/deck-plan.schema.jsonconfig8.5 KB
references/deck-sizing.mdmarkdown3.4 KB
references/environment-compatibility.mdmarkdown2.8 KB
references/feature-registry.jsonconfig1.4 KB
references/figure-extraction.mdmarkdown5.1 KB
references/job-request.defaults.jsonconfig1.6 KB
references/job-request.schema.jsonconfig7.5 KB
references/one-page-template.mdmarkdown3.1 KB
references/qa-gates.mdmarkdown10.0 KB
references/speaker-notes.mdmarkdown3.1 KB
references/template-contract.mdmarkdown5.1 KB
references/tikz-layout.mdmarkdown12.2 KB
references/visual-selection.mdmarkdown6.5 KB
references/workflow.mdmarkdown9.8 KB
requirements-doclayout.txtmarkdown238 B
requirements-ui.txtmarkdown39 B
requirements.txtmanifest68 B
scripts/apply_speaker_notes.pyscript6.1 KB
scripts/build_ppt.pyscript16.3 KB
scripts/crop_author_block.pyscript7.9 KB
scripts/crop_image_region.pyscript2.4 KB
scripts/export_pptx_pages.ps1script1.3 KB
scripts/extract_paper_assets.pyscript22.3 KB
scripts/job_request.pyscript17.1 KB
scripts/make_contact_sheet.pyscript4.0 KB
scripts/paper_ppt.pyscript17.1 KB
scripts/preflight_capabilities.pyscript8.3 KB
scripts/render_data_viz.pyscript14.6 KB
scripts/render_deck_overview.pyscript2.4 KB
scripts/render_one_page_html.pyscript13.4 KB
scripts/render_readability.pyscript4.1 KB
scripts/update_qa_status.pyscript10.1 KB
scripts/validate_deck_plan.pyscript33.9 KB
webapp/__init__.pyscript49 B
webapp/backend.pyscript14.5 KB
webapp/job_runner.pyscript3.2 KB
webapp/streamlit_app.pyscript17.3 KB

references/speaker-notes.md

View on GitHub
# Post-QA speaker notes

Speaker-note writing is a separate finalization stage. Finish the core deck, complete visual review, and record slide approval before drafting the script. This ordering prevents narration needs from distorting slide structure or visual decisions.

## Source boundary

The agent may use only:

- `deck-plan.json`: titles, body runs, purpose, takeaway, and visual metadata;
- `paper-notes.json`, evidence records, and the paper's extractable text;
- figure/table labels, captions, source pages, and approved data-redraw specifications.

Do not read rendered slide screenshots to write the script. Screenshots are visual-QA evidence, not a semantic source. Do not infer chart values from pixels or introduce a claim that is absent from the paper inventory or evidence records.

## Output contract

When `project.speaker_notes.enabled` is true, use this configuration:

```json
{
  "speaker_notes": {
    "enabled": true,
    "generation_stage": "post_qa",
    "delivery_style": "verbatim",
    "target_minutes": 30,
    "pace_units_per_minute": 220
  }
}
```

After core approval, add `speaker_notes` and `speaker_seconds` to every slide, including cover, paper-information, one-page, contents, section dividers, and closing. The script must be natural spoken prose rather than bullet fragments or instructions to the presenter.

For a normal 30-minute seminar, start with these budgets:

| Slide role | Typical time |
|---|---:|
| Cover | 15-25 seconds |
| Paper information | 45-70 seconds |
| One-page summary | 60-90 seconds |
| Contents | 20-30 seconds |
| Section divider | 8-15 seconds |
| Content slide | 55-95 seconds, adjusted by evidence density |
| Closing | 10-20 seconds |

Allocate the remaining time across content slides by conceptual and evidence density. The validator accepts a total within 15% of the configured target. `pace_units_per_minute` is only a drafting aid for mixed Chinese and English; the explicit `speaker_seconds` values are the timing contract.

## Writing rules

- Open each content page with the question or transition that makes the page necessary.
- Explain the visible figure, table, or mechanism using its recorded caption, source, and rationale.
- State metric, unit, baseline, and condition when presenting a numerical result.
- Preserve uncertainty, limitations, and attribution from the paper notes.
- Do not mechanically read the bullets. Expand them with reasoning and transitions, while keeping the same factual boundary.
- Keep fixed-role slides brief. Section-divider notes should connect the preceding conclusion to the next question.
- Write a complete verbatim script; do not write prompts such as "introduce this figure" or "improvise here".

## Apply and validate

The core builder intentionally does not write notes. After `approve-slides`, update the plan and run:

```text
python scripts/paper_ppt.py apply-notes deck-plan.json
python scripts/validate_deck_plan.py deck-plan.json --stage final
```

`apply-notes` validates the post-QA state, writes every note on a temporary PPTX, runs OfficeCLI validation, and replaces the output only after all checks pass. It writes `presentation.notes.json` beside the deck.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall