[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79J0CDEY5C92H8663JBX1HY":3,"skill-same:01M79J0CDEY5C92H8663JBX1HY":64},{"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},"01M79J0CDEY5C92H8663JBX1HY","explainer-reading-site-library-base",null,"Internal resource package invoked by reading-site initialize, deploy, and generate flows. Provides the persistent Cloudflare library manager and shared reading-site context assets.","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\u002Fexplainer\u002Fexplainer-reading-site-library-base\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: explainer-reading-site-library-base\ndescription: \"Internal resource package invoked by reading-site initialize, deploy, and generate flows. Provides the persistent Cloudflare library manager and shared reading-site context assets.\"\nuser-invocable: false\n---\n\n# Reading-site library base\n\nOwns the three resources shared across the reading-site skills, so there is one\nsource of truth for each and no cross-skill path reference:\n\n- **`scripts\u002Flibrary.py`** — manages a persistent, document-type-neutral **library**: one deploy root accumulates documents as subpaths, so one Cloudflare Pages project (and one Access policy) can serve the whole collection. The namespace is selected with `--namespace \u003Cname>` (or `LIBRARY_NAMESPACE`); it defaults to `pdf-explainer`, preserving the existing `${XDG_DATA_HOME:-$HOME\u002F.local\u002Fshare}\u002Fpdf-explainer\u002F` library. Local filesystem + JSON only — no network, no wrangler (the site skills run wrangler themselves). **It writes outside the workspace, so a sandboxed agent must run it with the sandbox off** (under Claude Code: `dangerouslyDisableSandbox: true`); the XDG library is not a path a command sandbox grants write access to, and `init`\u002F`add` die with a `PermissionError` there. Needing no network does not make a command sandbox-safe — *where it writes* is what decides that.\n- **`assets\u002Freading-site.css`** — the shared **context layer** of the reading-site design system, **content styling only**. It holds reading-site content components (source anchors, player, hero, cta, index cards, plus the `.hero .lede` tweak); the foundation and Tier 1 reading UI (typography, color model, callouts, chips, tables, pullquote, kicker, lede, keypoints, progressive-enhancement styles) come from the **[[explainer-html-docs]]** base and must be linked first. The reading-site nav *widgets* (the card filter, prev\u002Fnext, and the all-pages drawer) are **not** here — see below.\n- **`filters\u002Freading-site.lua`** — binds reading-site structure provenance. It\n  expands `.editorial-structure` headings into a visible disclosure plus a\n  subdued real-text origin marker, so the article and generated TOC\u002Fsidebar retain\n  the same attribution without competing with the heading. `.source-structure`\n  headings remain the source-derived layer.\n\nThe reading-site navigation widgets are owned by the explainer-html-docs **`reading-nav` opt-in component** (`reading-nav.css` \u002F `reading-nav.js`: the live index-card filter, prev\u002Fnext at the article foot, and a list FAB opening a slide-up **全ページ** drawer, all document-type-neutral). Book and paper consumers pull them in through the generator's `--component reading-nav` (and `library.py` copies them for the index). The nav's **single source of truth is still a per-site generated `nav-manifest.js`** (written via the shared reading-site build pipeline from the fixed page order, assigning `window.__HTMLDOCS_NAV`) — it is data, not a copied design-system asset, so a page list change means regenerating that one file, never touching each page's markup.\n\n[[book-explainer-generate-site]] and the paper consumer build pages through the\n[[explainer-html-docs]] generator, passing this directory as `--context`, its\nfilter as `--filter`, and `--component reading-nav`. `library.py` copies the same\nassets into the library index, so every reading site shares one visual language\nand interaction kit.\n\nThe base design system itself (`base.css` \u002F `base.js`) is **not** owned here — it lives in the sibling **[[explainer-html-docs]]** skill, which pdf-explainer consumes as a copy-mode base (see that skill's \"Consuming this base\"). Color carries meaning only: chapters are not color-coded, and anything colored without a meaning uses `--accent`.\n\n## Delegation\n\nReading-site consumers reference these by the base-skill-relative path (all skills install as siblings under the skills root):\n\n- `python3 explainer-reading-site-library-base\u002Fscripts\u002Flibrary.py \u003Csubcommand> [--namespace \u003Cname>]` — run the library manager. The option follows the subcommand; omit it for the compatible `pdf-explainer` default.\n- `explainer-reading-site-library-base\u002Fassets\u002Freading-site.css` — the shared content context asset to copy into a site's `assets\u002F`.\n- `explainer-reading-site-library-base\u002Ffilters\u002Freading-site.lua` — the\n  source\u002Feditorial structure-provenance filter passed to the generator.\n- `explainer-html-docs\u002Fassets\u002Fcomponents\u002Freading-nav\u002Freading-nav.css` and `...\u002Freading-nav.js` — the reading-nav widget bundle (pulled in via the generator's `--component reading-nav`).\n- `explainer-html-docs\u002Fassets\u002Fbase.css` and `...\u002Fbase.js` — the base substrate to copy alongside them.\n\nIf this base skill (or explainer-html-docs) is not installed, the dependent skill should say so and stop rather than guessing a path — the library layout lives here and the base design system lives in explainer-html-docs by definition. `library.py` resolves `base.css` from the sibling explainer-html-docs skill and falls back to a minimal stylesheet if it is absent.\n\n## library.py subcommands\n\n```\npath                       print the library root\nstatus                     print library.json (or a not-initialized notice)\nproject                    print the recorded Cloudflare Pages project name\npublic                     print the deploy root (\u003Croot>\u002Fpublic)\ninit --project NAME [--title T] [--force]\n                           create the library and an empty index\nadd --slug S --title T [--desc D] --from DIR\n                           copy DIR into public\u002F\u003CS>\u002F, record it, rebuild index\n```\n\n- **Layout it manages:** `\u003Croot>\u002Flibrary.json` (metadata — project name and book list; **never deployed**) and `\u003Croot>\u002Fpublic\u002F` (the deploy root uploaded whole by wrangler: `index.html`, `assets\u002F{base.css, reading-site.css, reading-nav.css, base.js, reading-nav.js}`, and one `\u003Cslug>\u002F` per book).\n- **`library.json` deliberately does NOT record whether Access is on.** Cloudflare Access is configured in the dashboard; nothing here can set it or read it back, so a local copy could only drift — and a stale flag is worse than no record, because it gets believed and reported as fact. State another system owns is not mirrored here. Ask the live URL instead (`curl -sI` → 302 = protected).\n- **`init`** refuses to clobber an existing library unless `--force`; **`add`** copies a `generate-site` `site\u002F` dir into `public\u002F\u003Cslug>\u002F` (rejecting a source with no `index.html`), records\u002Fupdates the book (same slug updates in place), and rebuilds `public\u002Findex.html` from `library.json`.\n- The script copies `base.css`\u002F`base.js` and the `reading-nav` component (`reading-nav.css`\u002F`reading-nav.js`) from the sibling **explainer-html-docs** skill, plus its own bundled `reading-site.css`, into `public\u002Fassets\u002F`; if `base.css` is somehow missing it falls back to a minimal readable stylesheet so the index still renders, and a missing PE script is skipped (its `\u003Cscript>` 404s silently — the index stays readable). The rendered index carries the theme toggle and the card filter as progressive enhancement, like every book page.\n","# Reading-site library base\n\nOwns the three resources shared across the reading-site skills, so there is one\nsource of truth for each and no cross-skill path reference:\n\n- **`scripts\u002Flibrary.py`** — manages a persistent, document-type-neutral **library**: one deploy root accumulates documents as subpaths, so one Cloudflare Pages project (and one Access policy) can serve the whole collection. The namespace is selected with `--namespace \u003Cname>` (or `LIBRARY_NAMESPACE`); it defaults to `pdf-explainer`, preserving the existing `${XDG_DATA_HOME:-$HOME\u002F.local\u002Fshare}\u002Fpdf-explainer\u002F` library. Local filesystem + JSON only — no network, no wrangler (the site skills run wrangler themselves). **It writes outside the workspace, so a sandboxed agent must run it with the sandbox off** (under Claude Code: `dangerouslyDisableSandbox: true`); the XDG library is not a path a command sandbox grants write access to, and `init`\u002F`add` die with a `PermissionError` there. Needing no network does not make a command sandbox-safe — *where it writes* is what decides that.\n- **`assets\u002Freading-site.css`** — the shared **context layer** of the reading-site design system, **content styling only**. It holds reading-site content components (source anchors, player, hero, cta, index cards, plus the `.hero .lede` tweak); the foundation and Tier 1 reading UI (typography, color model, callouts, chips, tables, pullquote, kicker, lede, keypoints, progressive-enhancement styles) come from the **[[explainer-html-docs]]** base and must be linked first. The reading-site nav *widgets* (the card filter, prev\u002Fnext, and the all-pages drawer) are **not** here — see below.\n- **`filters\u002Freading-site.lua`** — binds reading-site structure provenance. It\n  expands `.editorial-structure` headings into a visible disclosure plus a\n  subdued real-text origin marker, so the article and generated TOC\u002Fsidebar retain\n  the same attribution without competing with the heading. `.source-structure`\n  headings remain the source-derived layer.\n\nThe reading-site navigation widgets are owned by the explainer-html-docs **`reading-nav` opt-in component** (`reading-nav.css` \u002F `reading-nav.js`: the live index-card filter, prev\u002Fnext at the article foot, and a list FAB opening a slide-up **全ページ** drawer, all document-type-neutral). Book and paper consumers pull them in through the generator's `--component reading-nav` (and `library.py` copies them for the index). The nav's **single source of truth is still a per-site generated `nav-manifest.js`** (written via the shared reading-site build pipeline from the fixed page order, assigning `window.__HTMLDOCS_NAV`) — it is data, not a copied design-system asset, so a page list change means regenerating that one file, never touching each page's markup.\n\n[[book-explainer-generate-site]] and the paper consumer build pages through the\n[[explainer-html-docs]] generator, passing this directory as `--context`, its\nfilter as `--filter`, and `--component reading-nav`. `library.py` copies the same\nassets into the library index, so every reading site shares one visual language\nand interaction kit.\n\nThe base design system itself (`base.css` \u002F `base.js`) is **not** owned here — it lives in the sibling **[[explainer-html-docs]]** skill, which pdf-explainer consumes as a copy-mode base (see that skill's \"Consuming this base\"). Color carries meaning only: chapters are not color-coded, and anything colored without a meaning uses `--accent`.\n\n## Delegation\n\nReading-site consumers reference these by the base-skill-relative path (all skills install as siblings under the skills root):\n\n- `python3 explainer-reading-site-library-base\u002Fscripts\u002Flibrary.py \u003Csubcommand> [--namespace \u003Cname>]` — run the library manager. The option follows the subcommand; omit it for the compatible `pdf-explainer` default.\n- `explainer-reading-site-library-base\u002Fassets\u002Freading-site.css` — the shared content context asset to copy into a site's `assets\u002F`.\n- `explainer-reading-site-library-base\u002Ffilters\u002Freading-site.lua` — the\n  source\u002Feditorial structure-provenance filter passed to the generator.\n- `explainer-html-docs\u002Fassets\u002Fcomponents\u002Freading-nav\u002Freading-nav.css` and `...\u002Freading-nav.js` — the reading-nav widget bundle (pulled in via the generator's `--component reading-nav`).\n- `explainer-html-docs\u002Fassets\u002Fbase.css` and `...\u002Fbase.js` — the base substrate to copy alongside them.\n\nIf this base skill (or explainer-html-docs) is not installed, the dependent skill should say so and stop rather than guessing a path — the library layout lives here and the base design system lives in explainer-html-docs by definition. `library.py` resolves `base.css` from the sibling explainer-html-docs skill and falls back to a minimal stylesheet if it is absent.\n\n## library.py subcommands\n\n```\npath                       print the library root\nstatus                     print library.json (or a not-initialized notice)\nproject                    print the recorded Cloudflare Pages project name\npublic                     print the deploy root (\u003Croot>\u002Fpublic)\ninit --project NAME [--title T] [--force]\n                           create the library and an empty index\nadd --slug S --title T [--desc D] --from DIR\n                           copy DIR into public\u002F\u003CS>\u002F, record it, rebuild index\n```\n\n- **Layout it manages:** `\u003Croot>\u002Flibrary.json` (metadata — project name and book list; **never deployed**) and `\u003Croot>\u002Fpublic\u002F` (the deploy root uploaded whole by wrangler: `index.html`, `assets\u002F{base.css, reading-site.css, reading-nav.css, base.js, reading-nav.js}`, and one `\u003Cslug>\u002F` per book).\n- **`library.json` deliberately does NOT record whether Access is on.** Cloudflare Access is configured in the dashboard; nothing here can set it or read it back, so a local copy could only drift — and a stale flag is worse than no record, because it gets believed and reported as fact. State another system owns is not mirrored here. Ask the live URL instead (`curl -sI` → 302 = protected).\n- **`init`** refuses to clobber an existing library unless `--force`; **`add`** copies a `generate-site` `site\u002F` dir into `public\u002F\u003Cslug>\u002F` (rejecting a source with no `index.html`), records\u002Fupdates the book (same slug updates in place), and rebuilds `public\u002Findex.html` from `library.json`.\n- The script copies `base.css`\u002F`base.js` and the `reading-nav` component (`reading-nav.css`\u002F`reading-nav.js`) from the sibling **explainer-html-docs** skill, plus its own bundled `reading-site.css`, into `public\u002Fassets\u002F`; if `base.css` is somehow missing it falls back to a minimal readable stylesheet so the index still renders, and a missing PE script is skipped (its `\u003Cscript>` 404s silently — the index stays readable). The rendered index carries the theme toggle and the card filter as progressive enhancement, like every book page.\n",{"name":5,"description":7,"user-invocable":20},"main","08b762ef2ded20d4feadbe6fb7bfdd28747b0848","skills\u002Fexplainer\u002Fexplainer-reading-site-library-base",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 explainer-reading-site-library-base",{"tool":38,"command":39},"bunx","bunx skills add choplin\u002Fexplainer-studio --skill explainer-reading-site-library-base",{"tool":41,"command":42},"pnpm","pnpm dlx skills add choplin\u002Fexplainer-studio --skill explainer-reading-site-library-base","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Fskills\u002Fexplainer\u002Fexplainer-reading-site-library-base\u002FSKILL.md",true,[46,52,58],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"assets\u002Freading-site.css","ASSET","资产文件",4887,"https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Fskills\u002Fexplainer\u002Fexplainer-reading-site-library-base\u002Fassets\u002Freading-site.css",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"filters\u002Freading-site.lua","OTHER","其他",2182,"https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Fskills\u002Fexplainer\u002Fexplainer-reading-site-library-base\u002Ffilters\u002Freading-site.lua",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"scripts\u002Flibrary.py","SCRIPT","脚本",15404,"https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Fskills\u002Fexplainer\u002Fexplainer-reading-site-library-base\u002Fscripts\u002Flibrary.py",[65,71,78,85,92,99],{"skillNo":66,"name":67,"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":68,"categories":69,"keywords":70,"publishedAt":19},"01M79J25VYQ91K75R5HNDYYV4Z","invalid-skill-frontmatter","https:\u002F\u002Fgithub.com\u002Fchoplin\u002Fexplainer-studio\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid-skill-frontmatter\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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",[],[]]