annotated-doc
/annotated-doc
Tworzy samodzielne strony HTML z dowodami w eksperymentalnej aplikacji Annotated Documents, na wyraźne życzenie.
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Tworzy samodzielne strony HTML z dowodami w eksperymentalnej aplikacji Annotated Documents, na wyraźne życzenie.
Oryginalny opis (EN)
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.
Jak działa
- Author the requested HTML document with its evidence
Podgląd SKILL.md
--- 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.
Pliki w paczce (2)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
Wersje
W bazie nie ma innych skilli o nazwie annotated-doc.
Migawka bazy z 13.11.2026 · wersja paczki 64ae701ba8c7 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 91hub
Otwiera opcjonalną aplikację kpopper Hub do przeglądania zapisu projektu, jego grafu i weryfikacji, na wyraźną prośbę. - 90kpopper
Opisuje metodę kpopper, czyli zapis wiedzy w pliku GROUNDING.yaml z tym, skąd pochodzi każdy fakt i co by go obaliło. - 90annotated-product-guide
Pisze przewodniki produktowe i artykuły pomocy z adnotowanymi zrzutami ekranu: strzałkami, numerami i zamazanymi danymi. - 100gvm-doc-review
Recenzuje jakość dokumentów równoległymi panelami (struktura, śledzalność, jakość treści, punktacja), ocenia w skali 10 i tworzy raport HTML w stylu Tuftego i Few z priorytetowymi problemami. - 100single-html-document
Tworzy jednoplikowe dokumenty HTML z treścią, CSS i JavaScriptem w środku, np. interaktywny raport lub wyjaśnienie. - 100doc-forge
Pisze dokumenty czytelne do działania: README, specyfikacje, raporty, runbooki i notatki wydania, w Markdown oraz jako HTML lub PDF.