[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79J0ZBE29CTVEQVMPJ3F480":3,"skill-same:01M79J0ZBE29CTVEQVMPJ3F480":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M79J0ZBE29CTVEQVMPJ3F480","paper-explainer-generate-site",null,"Internal paper site-production phase that builds a local reading site from an exact run request, Content brief, Run Manifest, source structure\u002Fevidence, and report set.","choplin\u002Fexplainer-studio","choplin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F342798?v=4","01M79HWTA907677Q3R963A4PVZ","Akihiro Okuno","01M79HWTB0VNAN238405SZ6ESK",1,"MIT","https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Fskills\u002Fpaper-explainer\u002Fpaper-explainer-generate-site\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: paper-explainer-generate-site\ndescription: \"Internal paper site-production phase that builds a local reading site from an exact run request, Content brief, Run Manifest, source structure\u002Fevidence, and report set.\"\nuser-invocable: false\n---\n\n# Generate Site — paper-explainer reports as an authored website\n\nApply [[explainer-content-workflow-base]], read its Artifact contract, and\nrequire the `paper` profile. Own only site authoring and local build; do not\nperform workflow discovery, user consultation, Content modeling, or Planning.\n\nRequire exact paths\u002Fdigests for the run request, selected Content brief, Run\nManifest, `source-structure.md`, `spine.md`, and every planned report. The unique\nsite entry must be `create` or `replace`; otherwise return a structured\nmissing\u002Fincompatible-input result. Never infer latest planning Artifacts.\n\nPlanning Artifacts supplement rather than replace reports and paper evidence.\nConsult the narrow source\u002FOCR locus whenever fidelity requires it.\n\nTurn a **paper-explainer** work dir (`\u003Cdir>\u002F\u003Cslug>\u002F`, at least one report under\n`reports\u002F` — typically `overview.md` plus the perspective reports) into a\nreading-guide website under `\u003CWORK_DIR>\u002Fsite\u002F`: a landing page with report cards and\none authored page per report, the overview's audio guide playable in-page.\n\nThe whole build pipeline — scaffold, parallel semantic-Markdown authoring, the single\ngenerator build, the semantic landing page, the nav manifest, the gotchas, and the\nsuccess criteria — is the **shared reading-site pipeline** owned by\n[[explainer-reading-site-generate-base]]. **Delegate the build to that skill.** This skill\nadds only what is paper-specific: the canonical source-structure path,\npage-ordering profile, and landing vocabulary below. Do not re-derive the pipeline\nhere; follow the base skill for every phase.\n\n## paper-explainer inputs\n\n### Source locator kind\n\nPass `pdf-page` to the shared page-authoring and fan-in sweep contracts. Paper\nprose continues to use `[pNN]{.p}` \u002F `[pNN–pMM]{.p}`; no EPUB locator map applies.\n\n### Canonical source structure\n\nPass the absolute path to `\u003CWORK_DIR>\u002Fsource-structure.md` to the shared pipeline.\nIt records the paper's source-authored headings separately from `spine.md`, which\nremains the authority for confirmed facts. Perspective-report headings are\neditorial artifacts and are never a substitute for this source structure.\n\n### Ordered page list — `[{ slug, kicker }]`\n\nA paper's reports are not chapters; they are **fixed perspectives**. Resolve\n`reports\u002F*.md` into the base skill's ordered list with this canonical table, keeping\nonly the reports that exist and preserving this order:\n\n| report slug (`reports\u002F\u003Cslug>.md`) | kicker |\n|-----------------------------------|--------|\n| `overview`      | 全体レポート |\n| `background`    | 背景 |\n| `method`        | 手法 |\n| `experiments`   | 実験 |\n| `discussion`    | 議論 |\n| `related-work`  | 関連研究 |\n\n- `overview` is always first and is the landing hero CTA \u002F home. Do not renumber when\n  a subset is present — keep the canonical order for whichever exist.\n- Any report whose slug is **not** in the table (a hand-added report) is **appended last** in natural sort, with a\n  kicker derived from a readable title-case of its slug. Do not drop it.\n\nThis satisfies the base contract (overview first; every existing report once;\ndeterministic order; non-empty kicker). Reports are **not** color-coded — which report\nyou are on is answered by the nav, the title, and the index.\n\n### Landing document-type vocabulary\n\n- **guide kicker** (hero eyebrow): `論文ガイド`\n- **cards-section heading**: `レポート`\n- **count-chip unit**: `レポート` (hero chip reads `全Nレポート`)\n\nSite title = the paper title (from `reports\u002Foverview.md`'s `\u003Ch1>`).\n\n## Build\n\nHand the profile and canonical source-structure path above to [[explainer-reading-site-generate-base]] and run its pipeline\n(Phase 1 scaffold → Phase 2 author reports + landing → Phase 3 build + nav manifest →\nhand off to [[explainer-reading-site-deploy]]). The base skill's Success criteria are the\nacceptance for this skill. Return the exact output inventory\u002Fdigest and AI checks\nto the coordinator. Human interaction belongs to the coordinator. If `site` is a\nselected human gate, return the checked site as its checkpoint subject. Never\ntreat approval as permission to deploy.\n","# Generate Site — paper-explainer reports as an authored website\n\nApply [[explainer-content-workflow-base]], read its Artifact contract, and\nrequire the `paper` profile. Own only site authoring and local build; do not\nperform workflow discovery, user consultation, Content modeling, or Planning.\n\nRequire exact paths\u002Fdigests for the run request, selected Content brief, Run\nManifest, `source-structure.md`, `spine.md`, and every planned report. The unique\nsite entry must be `create` or `replace`; otherwise return a structured\nmissing\u002Fincompatible-input result. Never infer latest planning Artifacts.\n\nPlanning Artifacts supplement rather than replace reports and paper evidence.\nConsult the narrow source\u002FOCR locus whenever fidelity requires it.\n\nTurn a **paper-explainer** work dir (`\u003Cdir>\u002F\u003Cslug>\u002F`, at least one report under\n`reports\u002F` — typically `overview.md` plus the perspective reports) into a\nreading-guide website under `\u003CWORK_DIR>\u002Fsite\u002F`: a landing page with report cards and\none authored page per report, the overview's audio guide playable in-page.\n\nThe whole build pipeline — scaffold, parallel semantic-Markdown authoring, the single\ngenerator build, the semantic landing page, the nav manifest, the gotchas, and the\nsuccess criteria — is the **shared reading-site pipeline** owned by\n[[explainer-reading-site-generate-base]]. **Delegate the build to that skill.** This skill\nadds only what is paper-specific: the canonical source-structure path,\npage-ordering profile, and landing vocabulary below. Do not re-derive the pipeline\nhere; follow the base skill for every phase.\n\n## paper-explainer inputs\n\n### Source locator kind\n\nPass `pdf-page` to the shared page-authoring and fan-in sweep contracts. Paper\nprose continues to use `[pNN]{.p}` \u002F `[pNN–pMM]{.p}`; no EPUB locator map applies.\n\n### Canonical source structure\n\nPass the absolute path to `\u003CWORK_DIR>\u002Fsource-structure.md` to the shared pipeline.\nIt records the paper's source-authored headings separately from `spine.md`, which\nremains the authority for confirmed facts. Perspective-report headings are\neditorial artifacts and are never a substitute for this source structure.\n\n### Ordered page list — `[{ slug, kicker }]`\n\nA paper's reports are not chapters; they are **fixed perspectives**. Resolve\n`reports\u002F*.md` into the base skill's ordered list with this canonical table, keeping\nonly the reports that exist and preserving this order:\n\n| report slug (`reports\u002F\u003Cslug>.md`) | kicker |\n|-----------------------------------|--------|\n| `overview`      | 全体レポート |\n| `background`    | 背景 |\n| `method`        | 手法 |\n| `experiments`   | 実験 |\n| `discussion`    | 議論 |\n| `related-work`  | 関連研究 |\n\n- `overview` is always first and is the landing hero CTA \u002F home. Do not renumber when\n  a subset is present — keep the canonical order for whichever exist.\n- Any report whose slug is **not** in the table (a hand-added report) is **appended last** in natural sort, with a\n  kicker derived from a readable title-case of its slug. Do not drop it.\n\nThis satisfies the base contract (overview first; every existing report once;\ndeterministic order; non-empty kicker). Reports are **not** color-coded — which report\nyou are on is answered by the nav, the title, and the index.\n\n### Landing document-type vocabulary\n\n- **guide kicker** (hero eyebrow): `論文ガイド`\n- **cards-section heading**: `レポート`\n- **count-chip unit**: `レポート` (hero chip reads `全Nレポート`)\n\nSite title = the paper title (from `reports\u002Foverview.md`'s `\u003Ch1>`).\n\n## Build\n\nHand the profile and canonical source-structure path above to [[explainer-reading-site-generate-base]] and run its pipeline\n(Phase 1 scaffold → Phase 2 author reports + landing → Phase 3 build + nav manifest →\nhand off to [[explainer-reading-site-deploy]]). The base skill's Success criteria are the\nacceptance for this skill. Return the exact output inventory\u002Fdigest and AI checks\nto the coordinator. Human interaction belongs to the coordinator. If `site` is a\nselected human gate, return the checked site as its checkpoint subject. Never\ntreat approval as permission to deploy.\n",{"name":5,"description":7,"user-invocable":20},"main","08b762ef2ded20d4feadbe6fb7bfdd28747b0848","skills\u002Fpaper-explainer\u002Fpaper-explainer-generate-site",0,"https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio","https:\u002F\u002Fgithub.com\u002Fchoplin","http:\u002F\u002Fwww.chopl.in\u002F","2026-10-27 17:11:10",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add choplin\u002Fexplainer-studio --skill paper-explainer-generate-site",{"tool":38,"command":39},"bunx","bunx skills add choplin\u002Fexplainer-studio --skill paper-explainer-generate-site",{"tool":41,"command":42},"pnpm","pnpm dlx skills add choplin\u002Fexplainer-studio --skill paper-explainer-generate-site","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Fskills\u002Fpaper-explainer\u002Fpaper-explainer-generate-site\u002FSKILL.md",true,[],[47,53,60,67,74,81],{"skillNo":48,"name":49,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M79J25VYQ91K75R5HNDYYV4Z","invalid-skill-frontmatter","https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid-skill-frontmatter\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79J1ZWAX4EYVXPKTMB2WBMG","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.","https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Fskills\u002Fpdf-explainer\u002Fpdf-explainer-summarize\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79J1WEQW2GT78X92RMFY1AF","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.","https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Fskills\u002Fpdf-explainer\u002Fpdf-explainer-pdf-stitch\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79J1RZTE0VSWAJ26BYSPDD9","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.","https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Fskills\u002Fpdf-explainer\u002Fpdf-explainer-pdf-extract\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79J1NVVQY4XP1BQAEJJ4A23","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.","https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Fskills\u002Fpdf-explainer\u002Fpdf-explainer-pdf-detail\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79J1JQM36YS9WVXFPFJHWC7","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.","https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Fskills\u002Fpdf-explainer\u002Fpdf-explainer-generate-site\u002FSKILL.md",[],[]]