paper-explainer-generate-site
Internal paper site-production phase that builds a local reading site from an exact run request, Content brief, Run Manifest, source structure/evidence, and report set.
- License 许可
- MIT
- 最近更新
- 2026-10-27
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- paper-explainer-generate-site
- description
- Internal paper site-production phase that builds a local reading site from an exact run request, Content brief, Run Manifest, source structure/evidence, and report set.
- user-invocable
- false
03 SKILL.md 正文
Generate Site — paper-explainer reports as an authored website
Apply [[explainer-content-workflow-base]], read its Artifact contract, and
require the paper profile. Own only site authoring and local build; do not
perform workflow discovery, user consultation, Content modeling, or Planning.
Require exact paths/digests for the run request, selected Content brief, Run
Manifest, source-structure.md, spine.md, and every planned report. The unique
site entry must be create or replace; otherwise return a structured
missing/incompatible-input result. Never infer latest planning Artifacts.
Planning Artifacts supplement rather than replace reports and paper evidence. Consult the narrow source/OCR locus whenever fidelity requires it.
Turn a paper-explainer work dir (<dir>/<slug>/, at least one report under
reports/ — typically overview.md plus the perspective reports) into a
reading-guide website under <WORK_DIR>/site/: a landing page with report cards and
one authored page per report, the overview's audio guide playable in-page.
The whole build pipeline — scaffold, parallel semantic-Markdown authoring, the single generator build, the semantic landing page, the nav manifest, the gotchas, and the success criteria — is the shared reading-site pipeline owned by [[explainer-reading-site-generate-base]]. Delegate the build to that skill. This skill adds only what is paper-specific: the canonical source-structure path, page-ordering profile, and landing vocabulary below. Do not re-derive the pipeline here; follow the base skill for every phase.
paper-explainer inputs
Source locator kind
Pass pdf-page to the shared page-authoring and fan-in sweep contracts. Paper
prose continues to use [pNN]{.p} / [pNN–pMM]{.p}; no EPUB locator map applies.
Canonical source structure
Pass the absolute path to <WORK_DIR>/source-structure.md to the shared pipeline.
It records the paper's source-authored headings separately from spine.md, which
remains the authority for confirmed facts. Perspective-report headings are
editorial artifacts and are never a substitute for this source structure.
Ordered page list — [{ slug, kicker }]
A paper's reports are not chapters; they are fixed perspectives. Resolve
reports/*.md into the base skill's ordered list with this canonical table, keeping
only the reports that exist and preserving this order:
report slug (reports/<slug>.md) |
kicker |
|---|---|
overview |
全体レポート |
background |
背景 |
method |
手法 |
experiments |
実験 |
discussion |
議論 |
related-work |
関連研究 |
overviewis always first and is the landing hero CTA / home. Do not renumber when a subset is present — keep the canonical order for whichever exist.- Any report whose slug is not in the table (a hand-added report) is appended last in natural sort, with a kicker derived from a readable title-case of its slug. Do not drop it.
This satisfies the base contract (overview first; every existing report once; deterministic order; non-empty kicker). Reports are not color-coded — which report you are on is answered by the nav, the title, and the index.
Landing document-type vocabulary
- guide kicker (hero eyebrow):
論文ガイド - cards-section heading:
レポート - count-chip unit:
レポート(hero chip reads全Nレポート)
Site title = the paper title (from reports/overview.md's <h1>).
Build
Hand the profile and canonical source-structure path above to [[explainer-reading-site-generate-base]] and run its pipeline
(Phase 1 scaffold → Phase 2 author reports + landing → Phase 3 build + nav manifest →
hand off to [[explainer-reading-site-deploy]]). The base skill's Success criteria are the
acceptance for this skill. Return the exact output inventory/digest and AI checks
to the coordinator. Human interaction belongs to the coordinator. If site is a
selected human gate, return the checked site as its checkpoint subject. Never
treat approval as permission to deploy.
04 同仓库更多 Skills
invalid-skill-frontmatter
暂无简介
pdf-explainer-summarize
Digest a book, manual, or other long non-paper PDF into a source-anchored Markdown overview. Use when the requested deliverable is only a report, digest, or summary. Use paper-explainer-summarize for academic papers, direct reading for short PDFs, and book-explainer for coordinated reports, audio, site, rebuild, or resume.
pdf-explainer-pdf-stitch
Internal Phase 2 worker invoked once by pdf-explainer-summarize after chunk extraction. Reconciles sections across chunk boundaries, deduplicates the material, and writes the canonical structural spine and outline.
pdf-explainer-pdf-extract
Internal Phase 1 worker invoked by pdf-explainer-summarize once per page chunk. Reads the chunk visually or from a faithful text layer and writes structured source material with a verbatim heading stream, not a finished report.
pdf-explainer-pdf-detail
Internal per-chapter worker invoked by book-explainer for PDF input. Re-read one resolved chapter span visually or from a faithful text layer and write a standalone detail report with [pNN] source anchors.
pdf-explainer-generate-site
Compatibility entry point for requesting a local PDF reading site from an existing work directory. Route through book-explainer so Artifact reconciliation and Planning still occur.