docpage-digest

Docpage Digest

Turn one online documentation page into a verified, durable knowledge slice: the unaltered original, a structural inventory, per-section digests, independent verification records, and a handoff artifact an interview can walk. The pipeline engine here is generic; everything publisher-specific (fetch channel, applicability filter, digest-agent model matching, the doc queue) lives in a separable publisher profile under context/.

Work root

Configured library dir: ${user_config.library_dir}

This skill's .work/ root is formally carved out of the marketplace topic-docs convention (https://raw.githubusercontent.com/melodic-software/claude-code-plugins/main/docs/conventions/topic-docs/README.md): the work root resolves through the knowledge plugin's own library_dir seam, not the concern file's memory_dir.

Resolve the root once, before the first write, and record the resolved absolute path in the checklist's Provenance block. Every <work-root> path below is relative to it, and a resumed session reads it back instead of re-deriving it. Resolution rules for the rendered value above (the README's option table owns the value forms; this is how a run turns one into a directory):

• Unset, an empty value, or a surviving literal ${user_config.library_dir} token, means the option was never configured. Use the default .; never create a directory named after the token.
• Relative (including the default .). Resolve against the project directory, ${CLAUDE_PROJECT_DIR}/<value>.
• Absolute. Use verbatim, with no project-directory prefix.
• Leading ~, the home directory, with no project-directory prefix.
• ${NAME} / %NAME% env-var reference. Read the variable yourself (printenv NAME in bash, $env:NAME in PowerShell) and use its value with no project-directory prefix. An unset variable fails the run loudly. Report it and stop. Never hand the reference to a shell for expansion: an unset variable expands to the empty string there, silently writing the slice to the wrong root.