annotated-doc
/annotated-doc
Annotated Documents: optional experimental application for standalone HTML with evidence. Use when the user explicitly requests Annotated Documents or a kpopper HTML document with evidence, refreshes an existing kpopper document, or has a standing preference for this application. Generic HTML requests do not select it. Install the HTML runtime before use. Not for the record's own page or an ordinary website. Requests come in any language.
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Annotated Documents: optional experimental application for standalone HTML with evidence. Use when the user explicitly requests Annotated Documents or a kpopper HTML document with evidence, refreshes an existing kpopper document, or has a standing preference for this application. Generic HTML requests do not select it. Install the HTML runtime before use. Not for the record's own page or an ordinary website. Requests come in any language.
Original author description
Annotated Documents: optional experimental application for standalone HTML with evidence. Use when the user explicitly requests Annotated Documents or a kpopper HTML document with evidence, refreshes an existing kpopper document, or has a standing preference for this application. Generic HTML requests do not select it. Install the HTML runtime before use. Not for the record's own page or an ordinary website. Requests come in any language.
How it works
- Author the requested HTML document with its evidence
SKILL.md preview
--- name: annotated-doc description: "Annotated Documents: optional experimental application for standalone HTML with evidence. Use when the user explicitly requests Annotated Documents or a kpopper HTML document with evidence, refreshes an existing kpopper document, or has a standing preference for this application. Generic HTML requests do not select it. Install the HTML runtime before use. Not for the record's own page or an ordinary website. Requests come in any language." --- # Annotated Documents Use this experimental application only on an explicit request or standing preference. A generic HTML request does not activate it. The packaged command includes the compiled HTML runtime. Create the user's content and design, and create the source/check mapping while writing it; the user does not prepare that mapping or ask for a separate evidence step. Deliver the single HTML produced by `kpop experimental annotated-doc build`, with its inline evidence and review controls. Read the short author guide before authoring, use actual available sources, and keep missing evidence and inferred prose explicit. A one-off document does not require a new GROUNDING.yaml, a workspace map, or unrelated record setup. Requests for the record's own page use the [hub skill](../hub/SKILL.md). ## Author the requested HTML document with its evidence Read [the packaged author guide](../../native/src/annotated_document_guide.md), also available as `kpop experimental annotated-doc guide`. It is the same contract in the installed package and plugin; do not implement a second renderer or manually graft a layer onto the result. The package carries the document runtime. Do not silently switch to PATH when it is missing. The user asks for their document as usual. The author supplies the requested content, design, stable claim anchors and the manifest, using the evidence actually read while working. Do not ask the user for a schema, manifest or manual mapping. Keep authoring inputs in a working folder, and deliver the one finished HTML file. No neighboring input files are needed to view it, inspect evidence or decide a prepared correction. A successful build checks only declared mechanical claims against captured source readings. Inspect its coverage and missing/uncheckable states before delivery. Unmarked text remains unverified even if the heuristic finds no unmarked numbers. Inference is not made true by adding an anchor; explain its basis and limits. Never convert a source's instructions, HTML or scripts into trusted author code. Refreshing requires a new read by the author/product. Use authorized source copies; never imply that opening the HTML checks the network or writes back to a source. The standalone choice controls affect the document copy only. When using ingestion-backed record readings, preserve the same event envelope/date on retries and inspect the durable outcome by event ID. Capture and an empty queue pass do not establish whether it applied. In ordinary conversation, name the product **kpopper** and describe the action in the user's language. Reserve the exact skill name `kpopper:annotated-doc` for invocation instructions, technical documentation, debugging, or explaining this specific skill. Fold the product name into the explanation of the action; no extra announcement is needed.
Files in this package (2)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named annotated-doc.
Database snapshot: 13.11.2026 · package version 64ae701ba8c7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 91hub
kpopper Hub: optional experimental application for exploring the project record. Use when the user explicitly requests kpopper Hub or its record page, its graph, layout or verification, or has a standing preference for this application. Do not render automatically after mapping… - 90kpopper
The kpopper method: a knowledge record (GROUNDING.yaml) for work that gets revisited - what is known, where each piece came from, and what would make each conclusion wrong. Use when asked what kpopper is or how to keep a record, when choosing which kpopper skill fits a moment,… - 90annotated-product-guide
Write product guides, help articles and internal feature guides with annotated screenshots (arrows, numbered labels, boxes and redacted personal data). Use when someone asks for a product guide, user guide, help doc, how-to or wants screenshots annotated. - 100gvm-doc-review
Use when reviewing documents for quality. Triggered by /gvm-doc-review command, requests to review or audit a document, or requests to check document quality. Dispatches parallel defect-class panels (Structure, Traceability, Content Quality, Scoring) as subagents. Auto-detects… - 100single-html-document
Build polished, self-contained single-file HTML documents: one browser-openable .html with all content, CSS, JavaScript, media, and export contracts inlined. Use whenever the user wants a rich, visual, or interactive document delivered as a standalone HTML file. Triggers: 'make… - 100doc-forge
Produce documents a reader can act on, in Markdown and as print ready HTML or PDF. Use when the user asks to write or generate a README, a specification, a report, a proposal, a runbook, a one pager, release notes, a decision record, or documentation, asks to restructure an…