[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CXVFE9PKC630EXN91TCVWP":3,"skill-same:01M7CXVFE9PKC630EXN91TCVWP":49},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CXVFE9PKC630EXN91TCVWP","editorial-document",null,"Write long-form editorial documents as clean, semantic HTML saved as an artifact (kind=document) — reports, briefs, explainers, proposals, write-ups. Covers the house style (structure, voice, typography) AND the security contract (the HTML is sanitized fail-closed, so author within the allowlist). Load when the user wants a polished written document, report, brief, or explainer that should read like a publication, not a chat message.","Sidiora-Labs\u002Fcentra-gideon-agent","Sidiora-Labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F315858149?v=4","01M7CXSE0SZN9PME7BZ77KK2N7","Sidiora Labs","01M7CXSE1TJT3GJDJC6A9B7YD2",212,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSidiora-Labs\u002Fcentra-gideon-agent\u002Fblob\u002Fmain\u002Fruntime\u002Fgideon\u002Fextensions\u002Fskills\u002Fbundled\u002Feditorial-document\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: editorial-document\ndescription: Write long-form editorial documents as clean, semantic HTML saved as an artifact (kind=document) — reports, briefs, explainers, proposals, write-ups. Covers the house style (structure, voice, typography) AND the security contract (the HTML is sanitized fail-closed, so author within the allowlist). Load when the user wants a polished written document, report, brief, or explainer that should read like a publication, not a chat message.\ntriggers: document, write a report, write up, brief, explainer, proposal, white paper, editorial, long-form, publish a doc, formatted document, article, memo, one-pager\n---\n\n# Editorial Documents\n\nGideon renders long-form written documents from semantic HTML, saved as an\nartifact with `kind=document`. Unlike a `widget` (interactive HTML in a sandboxed\niframe) or `markdown`, a document is **prose-first editorial HTML** rendered in the\npage with a tuned reading type scale — it should read like a published piece.\n\nSave with `artifact_save(kind=\"document\", name=\"…\", content=\u003CHTML>)`. The body is\nHTML (semantic tags, no `\u003Chtml>`\u002F`\u003Cbody>` wrapper needed — just the content). The\nviewer renders it with the editorial stylesheet, lets the user edit the HTML with a\nlive split preview, comment on any passage, and export it (standalone HTML \u002F copy).\n\n## When to use this vs other types\n\n- **Document** — a written piece meant to be *read*: reports, briefs, explainers,\n  proposals, post-mortems, design write-ups. Prose is the substance.\n- **Markdown** — quick notes \u002F READMEs \u002F chat-adjacent text where Markdown's\n  shorthand is enough and you don't need editorial typography.\n- **Widget** (`visual-output` skill) — interactive HTML, dashboards, custom charts.\n- **Infographic** (`infographic-syntax` skill) — structured visual info-design.\n\n## The security contract (author within the allowlist)\n\nThe document body is **sanitized fail-closed** before rendering: anything not on\nthe allowlist is dropped. This is a security control because the content may echo\nuntrusted material (e.g. crawled pages). Author accordingly:\n\n- **Allowed:** semantic prose + structure — headings (`h1`–`h6`), `p`, `ul`\u002F`ol`\u002F\n  `li`, `blockquote`, `pre`\u002F`code`, `table`\u002F`thead`\u002F`tbody`\u002F`tr`\u002F`th`\u002F`td`,\n  `figure`\u002F`figcaption`, `img`, `a`, `strong`\u002F`em`, `hr`, `section`\u002F`article`,\n  inline `svg` for simple diagrams.\n- **Dropped (don't bother emitting):** `\u003Cscript>`, `\u003Cstyle>`, `\u003Ciframe>`, `\u003Cobject>`,\n  `\u003Cform>`, inline event handlers (`onclick=…`), inline `style=` attributes, and\n  `javascript:`\u002F`data:text\u002Fhtml` URLs. Links must be `http(s)`, `mailto:`, `tel:`,\n  relative, or `#anchors`; `data:image\u002F*` is allowed for inline images.\n- Don't fight the sanitizer with inline styles — the editorial stylesheet handles\n  typography. Write clean structure and let it style.\n\n## House style\n\n**Structure.** Open with an `\u003Ch1>` title and a one-paragraph lede that states the\npoint. Use `\u003Ch2>` for major sections, `\u003Ch3>` for sub-sections. Prefer short\nsections with descriptive headings over one long wall. Close with a clear takeaway\nor next-steps section when the piece calls for it.\n\n**Voice.** Direct and concrete. Lead with the conclusion, then support it (BLUF).\nActive voice. Cut filler (\"it should be noted that\", \"in order to\"). One idea per\nparagraph; 2–4 sentences each.\n\n**Evidence.** Use `\u003Ctable>` for comparisons\u002Fdata, `\u003Cul>` for parallel points, a\n`\u003Cblockquote>` for a pulled quote or key caveat. Link sources with real `\u003Ca href>`.\nUse `\u003Cfigure>` + `\u003Cfigcaption>` for images\u002Fdiagrams.\n\n**Typography.** Don't hand-set fonts\u002Fsizes\u002Fcolors — the reader stylesheet owns the\ntype scale (heading hierarchy, a measure of roughly 75 characters, readable\nline-height) and is theme-aware. Your job is correct *semantics*; the styling\nfollows.\n\n## Example\n\n```html\n\u003Ch1>Q3 Reliability Review\u003C\u002Fh1>\n\u003Cp>Availability held at 99.95% despite a 40% traffic increase — but two incidents\nshare a root cause we haven't fixed. This brief lays out what happened and the one\nchange that closes both.\u003C\u002Fp>\n\n\u003Ch2>What happened\u003C\u002Fh2>\n\u003Cp>…\u003C\u002Fp>\n\u003Ctable>\n  \u003Cthead>\u003Ctr>\u003Cth>Incident\u003C\u002Fth>\u003Cth>Duration\u003C\u002Fth>\u003Cth>Root cause\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\n  \u003Ctbody>\n    \u003Ctr>\u003Ctd>Aug 12 latency\u003C\u002Ftd>\u003Ctd>34 min\u003C\u002Ftd>\u003Ctd>Connection-pool exhaustion\u003C\u002Ftd>\u003C\u002Ftr>\n    \u003Ctr>\u003Ctd>Sep 3 errors\u003C\u002Ftd>\u003Ctd>18 min\u003C\u002Ftd>\u003Ctd>Connection-pool exhaustion\u003C\u002Ftd>\u003C\u002Ftr>\n  \u003C\u002Ftbody>\n\u003C\u002Ftable>\n\n\u003Ch2>The fix\u003C\u002Fh2>\n\u003Cblockquote>One change — bounded pools with backpressure — removes the shared cause.\u003C\u002Fblockquote>\n\u003Cp>…\u003C\u002Fp>\n```\n\n## Workflow\n\n1. Confirm a *document* is right (a written piece to be read, not interactive).\n2. Draft semantic HTML within the allowlist; structure with headings + the lede.\n3. `artifact_save(kind=\"document\", name=\"…\", content=\u003CHTML>)` (or `artifact_update`\n   a prior one — `artifact_list` first, per the `artifacts` skill).\n4. The user reads it, edits the HTML with live preview, comments on passages (those\n   route back to you), and can export a standalone HTML file.\n\n## Pitfalls\n\n- Don't emit `\u003Cscript>`\u002F`\u003Cstyle>`\u002Finline `style=`\u002F`onclick=` — they're stripped.\n- Don't wrap the body in `\u003Cwidget>` — `kind=document` is its own type.\n- Don't hand-style — semantics + the reader stylesheet, not inline CSS.\n- Keep links to safe schemes (http(s)\u002Fmailto\u002Ftel\u002Frelative\u002F#).\n","# Editorial Documents\n\nGideon renders long-form written documents from semantic HTML, saved as an\nartifact with `kind=document`. Unlike a `widget` (interactive HTML in a sandboxed\niframe) or `markdown`, a document is **prose-first editorial HTML** rendered in the\npage with a tuned reading type scale — it should read like a published piece.\n\nSave with `artifact_save(kind=\"document\", name=\"…\", content=\u003CHTML>)`. The body is\nHTML (semantic tags, no `\u003Chtml>`\u002F`\u003Cbody>` wrapper needed — just the content). The\nviewer renders it with the editorial stylesheet, lets the user edit the HTML with a\nlive split preview, comment on any passage, and export it (standalone HTML \u002F copy).\n\n## When to use this vs other types\n\n- **Document** — a written piece meant to be *read*: reports, briefs, explainers,\n  proposals, post-mortems, design write-ups. Prose is the substance.\n- **Markdown** — quick notes \u002F READMEs \u002F chat-adjacent text where Markdown's\n  shorthand is enough and you don't need editorial typography.\n- **Widget** (`visual-output` skill) — interactive HTML, dashboards, custom charts.\n- **Infographic** (`infographic-syntax` skill) — structured visual info-design.\n\n## The security contract (author within the allowlist)\n\nThe document body is **sanitized fail-closed** before rendering: anything not on\nthe allowlist is dropped. This is a security control because the content may echo\nuntrusted material (e.g. crawled pages). Author accordingly:\n\n- **Allowed:** semantic prose + structure — headings (`h1`–`h6`), `p`, `ul`\u002F`ol`\u002F\n  `li`, `blockquote`, `pre`\u002F`code`, `table`\u002F`thead`\u002F`tbody`\u002F`tr`\u002F`th`\u002F`td`,\n  `figure`\u002F`figcaption`, `img`, `a`, `strong`\u002F`em`, `hr`, `section`\u002F`article`,\n  inline `svg` for simple diagrams.\n- **Dropped (don't bother emitting):** `\u003Cscript>`, `\u003Cstyle>`, `\u003Ciframe>`, `\u003Cobject>`,\n  `\u003Cform>`, inline event handlers (`onclick=…`), inline `style=` attributes, and\n  `javascript:`\u002F`data:text\u002Fhtml` URLs. Links must be `http(s)`, `mailto:`, `tel:`,\n  relative, or `#anchors`; `data:image\u002F*` is allowed for inline images.\n- Don't fight the sanitizer with inline styles — the editorial stylesheet handles\n  typography. Write clean structure and let it style.\n\n## House style\n\n**Structure.** Open with an `\u003Ch1>` title and a one-paragraph lede that states the\npoint. Use `\u003Ch2>` for major sections, `\u003Ch3>` for sub-sections. Prefer short\nsections with descriptive headings over one long wall. Close with a clear takeaway\nor next-steps section when the piece calls for it.\n\n**Voice.** Direct and concrete. Lead with the conclusion, then support it (BLUF).\nActive voice. Cut filler (\"it should be noted that\", \"in order to\"). One idea per\nparagraph; 2–4 sentences each.\n\n**Evidence.** Use `\u003Ctable>` for comparisons\u002Fdata, `\u003Cul>` for parallel points, a\n`\u003Cblockquote>` for a pulled quote or key caveat. Link sources with real `\u003Ca href>`.\nUse `\u003Cfigure>` + `\u003Cfigcaption>` for images\u002Fdiagrams.\n\n**Typography.** Don't hand-set fonts\u002Fsizes\u002Fcolors — the reader stylesheet owns the\ntype scale (heading hierarchy, a measure of roughly 75 characters, readable\nline-height) and is theme-aware. Your job is correct *semantics*; the styling\nfollows.\n\n## Example\n\n```html\n\u003Ch1>Q3 Reliability Review\u003C\u002Fh1>\n\u003Cp>Availability held at 99.95% despite a 40% traffic increase — but two incidents\nshare a root cause we haven't fixed. This brief lays out what happened and the one\nchange that closes both.\u003C\u002Fp>\n\n\u003Ch2>What happened\u003C\u002Fh2>\n\u003Cp>…\u003C\u002Fp>\n\u003Ctable>\n  \u003Cthead>\u003Ctr>\u003Cth>Incident\u003C\u002Fth>\u003Cth>Duration\u003C\u002Fth>\u003Cth>Root cause\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\n  \u003Ctbody>\n    \u003Ctr>\u003Ctd>Aug 12 latency\u003C\u002Ftd>\u003Ctd>34 min\u003C\u002Ftd>\u003Ctd>Connection-pool exhaustion\u003C\u002Ftd>\u003C\u002Ftr>\n    \u003Ctr>\u003Ctd>Sep 3 errors\u003C\u002Ftd>\u003Ctd>18 min\u003C\u002Ftd>\u003Ctd>Connection-pool exhaustion\u003C\u002Ftd>\u003C\u002Ftr>\n  \u003C\u002Ftbody>\n\u003C\u002Ftable>\n\n\u003Ch2>The fix\u003C\u002Fh2>\n\u003Cblockquote>One change — bounded pools with backpressure — removes the shared cause.\u003C\u002Fblockquote>\n\u003Cp>…\u003C\u002Fp>\n```\n\n## Workflow\n\n1. Confirm a *document* is right (a written piece to be read, not interactive).\n2. Draft semantic HTML within the allowlist; structure with headings + the lede.\n3. `artifact_save(kind=\"document\", name=\"…\", content=\u003CHTML>)` (or `artifact_update`\n   a prior one — `artifact_list` first, per the `artifacts` skill).\n4. The user reads it, edits the HTML with live preview, comments on passages (those\n   route back to you), and can export a standalone HTML file.\n\n## Pitfalls\n\n- Don't emit `\u003Cscript>`\u002F`\u003Cstyle>`\u002Finline `style=`\u002F`onclick=` — they're stripped.\n- Don't wrap the body in `\u003Cwidget>` — `kind=document` is its own type.\n- Don't hand-style — semantics + the reader stylesheet, not inline CSS.\n- Keep links to safe schemes (http(s)\u002Fmailto\u002Ftel\u002Frelative\u002F#).\n",{"name":5,"triggers":24,"description":7},"document, write a report, write up, brief, explainer, proposal, white paper, editorial, long-form, publish a doc, formatted document, article, memo, one-pager","main","d2af2361d07479c31299731cd2aab81a99a1b0ae","runtime\u002Fgideon\u002Fextensions\u002Fskills\u002Fbundled\u002Feditorial-document",33,"https:\u002F\u002Fgithub.com\u002FSidiora-Labs\u002Fcentra-gideon-agent","https:\u002F\u002Fcentra.ag","https:\u002F\u002Fgithub.com\u002FSidiora-Labs","sidioralabs.com","An Applied Lab for Systems That Connect Ideas to Action.","2026-11-05 23:31:58",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Sidiora-Labs\u002Fcentra-gideon-agent --skill editorial-document",{"tool":41,"command":42},"bunx","bunx skills add Sidiora-Labs\u002Fcentra-gideon-agent --skill editorial-document",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Sidiora-Labs\u002Fcentra-gideon-agent --skill editorial-document","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSidiora-Labs\u002Fcentra-gideon-agent\u002Fblob\u002Fmain\u002Fruntime\u002Fgideon\u002Fextensions\u002Fskills\u002Fbundled\u002Feditorial-document\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7CXXG9ZW9SRRET92XBGS5W3","web-verify","Verify a built web page or app actually renders and works — drive it in a real browser, check the console and network, confirm the thing you changed is the thing being served, and capture evidence. Use before claiming a frontend change works.","https:\u002F\u002Fgithub.com\u002FSidiora-Labs\u002Fcentra-gideon-agent\u002Fblob\u002Fmain\u002Fruntime\u002Fgideon\u002Fextensions\u002Fskills\u002Fbundled\u002Fweb-verify\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CXX9RXMRB1ZHTRETSDVB8B","visual-output","Emit rich visual output in chat via \u003Cwidget> tags — styled HTML cards, charts, tables, interactive tools, and drawn SVG\u002Fcanvas diagrams, illustrations, and animations — theme-aware, centered, and responsive instead of clashing or cramped.","https:\u002F\u002Fgithub.com\u002FSidiora-Labs\u002Fcentra-gideon-agent\u002Fblob\u002Fmain\u002Fruntime\u002Fgideon\u002Fextensions\u002Fskills\u002Fbundled\u002Fvisual-output\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"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},"01M7CXX48DZZ7JTV0RRS4406Y7","task-and-project","Track work as Tasks (the \u002Fapi\u002Ftasks CRUD + native task provider), and decompose larger projects into independent, verifiable units — fanning parallel investigation out to subagents while keeping one coherent plan; hand open-ended goal-driven work to a goal loop.","https:\u002F\u002Fgithub.com\u002FSidiora-Labs\u002Fcentra-gideon-agent\u002Fblob\u002Fmain\u002Fruntime\u002Fgideon\u002Fextensions\u002Fskills\u002Fbundled\u002Ftask-and-project\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},"01M7CXWYSRFM4BX63CY3TD0PA6","research-campaign","Run a multi-cycle research campaign — grill the question, decompose it into answerable sub-questions, investigate each against sources, then synthesize with confidence and gaps stated. Use for open questions that need real investigation rather than one lookup.","https:\u002F\u002Fgithub.com\u002FSidiora-Labs\u002Fcentra-gideon-agent\u002Fblob\u002Fmain\u002Fruntime\u002Fgideon\u002Fextensions\u002Fskills\u002Fbundled\u002Fresearch-campaign\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},"01M7CXWSF6REG8ST1X0M7HN563","memory-discipline","When and how to persist durable memory — save genuine user preferences, facts, and corrections; NEVER persist transient environment failures (a failed command, a flaky network call, a one-off tool error) as lessons; recall before re-asking.","https:\u002F\u002Fgithub.com\u002FSidiora-Labs\u002Fcentra-gideon-agent\u002Fblob\u002Fmain\u002Fruntime\u002Fgideon\u002Fextensions\u002Fskills\u002Fbundled\u002Fmemory-discipline\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},"01M7CXWJDSGB37A4E74EFK748F","loop-worker","Per-cycle protocol for an autonomous goal loop worker — the unified autonomous goal engine that runs one self-directed cycle per turn until its goal is met, then self-retires. Drives one cycle against a loop's file interface (status.json gate, brief.md goal, guidance.txt nudges, findings\u002Fcycle_NNN.json, FINDINGS.md, the type-appropriate deliverable, STOP sentinel). The worker produces work and reports evidence; a deterministic check or a separate judge — never the worker — decides done-ness.","https:\u002F\u002Fgithub.com\u002FSidiora-Labs\u002Fcentra-gideon-agent\u002Fblob\u002Fmain\u002Fruntime\u002Fgideon\u002Fextensions\u002Fskills\u002Fbundled\u002Floop-worker\u002FSKILL.md",[],[]]