[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CY57ED279GA6QC3BFMPXG5":3,"skill-same:01M7CY57ED279GA6QC3BFMPXG5":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CY57ED279GA6QC3BFMPXG5","apply-comments",null,"Apply pending @slide-comment markers written by the open-slide inspector tool. Use when the user asks to \"apply comments\", \"process slide comments\", \"apply the inspector comments\", or references markers left inside `slides\u002F\u003Cid>\u002Findex.tsx`.","BotHarness\u002FDeepSeekBot","BotHarness","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F330270786?v=4","01M7CX37EXWM53FHAQ28JNKZTZ","01M7CX37FHA8NY5D2KXFZWV63Y",852,"MIT","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fapply-comments\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: apply-comments\ndescription: Apply pending @slide-comment markers written by the open-slide inspector tool. Use when the user asks to \"apply comments\", \"process slide comments\", \"apply the inspector comments\", or references markers left inside `slides\u002F\u003Cid>\u002Findex.tsx`.\n---\n\n# Apply slide comments\n\nThe open-slide editor has an inspector tool that lets the user click on a rendered page element and attach a textual comment (e.g. *\"make this red\"*, *\"change to 'Open Slide Rocks'\"*). Each comment is persisted as an in-source JSX marker inside `slides\u002F\u003CslideId>\u002Findex.tsx`.\n\nYour job: read those markers, perform the described edits, and delete the markers.\n\n> **Before making any page edit**, consult the **`slide-authoring`** skill — it is the technical reference for how `slides\u002F\u003Cid>\u002Findex.tsx` is structured (canvas, type scale, palette, assets, file contract). A comment like *\"make this bigger\"* or *\"change the accent colour\"* should be applied in a way that stays consistent with those rules.\n\n## Marker format\n\n```\n{\u002F* @slide-comment id=\"c-\u003C8hex>\" ts=\"\u003CISO>\" text=\"\u003Cbase64url(JSON)>\" *\u002F}\n```\n\n- Always sits on its own line as the **first child inside** the JSX element it refers to (i.e. between that element's opening `>` and its other children). The marker is dropped *into* its target, not floated above it.\n- `text` is base64url-encoded JSON: `{\"note\": \"...\", \"hint\"?: \"...\"}`.\n- Detection regex (authoritative — use exactly this):\n\n  ```\n  \u002F\\{\\\u002F\\*\\s*@slide-comment\\s+id=\"(c-[a-f0-9]+)\"\\s+ts=\"([^\"]+)\"\\s+text=\"([A-Za-z0-9_\\-]+={0,2})\"\\s*\\*\\\u002F\\}\u002Fg\n  ```\n\n## Procedure\n\n1. **Identify the target slide(s).**\n   - If the user names one (`getting-started`, `q2-roadmap`, etc.), work on that single `slides\u002F\u003CslideId>\u002Findex.tsx`.\n   - If they say \"all\" or don't specify, scan every `slides\u002F*\u002Findex.tsx`. Process each slide one at a time.\n\n2. **Read the file and find all markers.**\n   - Run the regex above against the whole file.\n   - For each match, base64url-decode `text` and `JSON.parse` it to get `{ note, hint? }`.\n   - Record each hit as `{ id, lineIndex (0-based), note, hint }`.\n   - If there are no markers, tell the user and stop.\n\n3. **Understand each comment in context.**\n   - The targeted JSX element is the **enclosing** element of the marker — i.e. read upward from the marker line until you reach the unclosed JSX opening tag whose body the marker lives in. That element is the target. (For self-closing elements like `\u003Cimg \u002F>`, the inspector hoists the marker to the nearest non-self-closing ancestor; in that case the comment usually refers to a child of the enclosing element rather than the enclosing element itself — use the `note` text to disambiguate.)\n   - Read enough surrounding code (parent element, sibling elements, inline styles) to apply the change faithfully. A comment inside a `\u003Cdiv>` with an inline `background` style usually refers to that element's styling, for example.\n   - If the `note` is ambiguous, do the smallest reasonable interpretation and mention the assumption in your summary.\n\n4. **Apply edits in reverse line order.**\n   - Sort markers by descending `lineIndex` and process one at a time, using the `Edit` tool.\n   - Processing top-down would invalidate line numbers for later markers as the file shrinks\u002Fgrows.\n\n5. **Remove each marker after applying its edit.**\n   - Delete the entire marker line including its trailing `\\n`.\n   - Never leave a marker behind for an edit you applied — that signals a failure. Markers deliberately skipped per the edge cases below stay in place.\n\n6. **Verify.**\n   - After all edits, re-read the file and confirm the only remaining markers are ones you reported as skipped.\n   - Confirm the edited JSX is well-formed (balanced tags, no dangling attributes). If the project's `package.json` has typecheck\u002Flint scripts, run them with the project's package manager; scaffolded projects ship neither TypeScript nor a linter — there, rely on the running dev server (or the `build` script) to surface compile errors. Fix any errors you introduced.\n\n7. **Report.**\n   - Summarise: `N applied, M skipped` plus a one-line description of each change (including the slide id).\n\n## base64url decoding helper\n\n```js\nfunction decode(s) {\n  const pad = s.length % 4 === 0 ? '' : '='.repeat(4 - (s.length % 4));\n  return Buffer.from(s.replace(\u002F-\u002Fg, '+').replace(\u002F_\u002Fg, '\u002F') + pad, 'base64').toString('utf8');\n}\n```\n\nYou can run this inline via `node -e '...'` if you need to inspect a payload; otherwise just reason about the decoded string.\n\n## Edge cases\n\n- **Marker with no enclosing JSX element** (shouldn't happen — the inspector won't write one — but if you find one): delete it and note as orphan.\n- **Multiple markers stacked on consecutive lines inside the same element**: they all refer to that enclosing element. Read their notes in source order to understand the combined intent, then apply and delete them bottom-up per step 4.\n- **Comment asks for something outside the target element's scope** (e.g. \"add a new page\"): do the closest-reasonable edit and mention the scope expansion in your summary.\n- **Can't resolve the comment** (e.g. truly ambiguous, or the file changed shape such that the target element doesn't exist): leave the marker in place and report it as skipped. Don't guess.\n\n## Do not\n\n- Do not touch `package.json`, `open-slide.config.ts`, or files outside `slides\u002F`.\n- Do not add dependencies.\n- Do not re-introduce markers or leave `TODO` breadcrumbs — the user already has a record in git.\n","# Apply slide comments\n\nThe open-slide editor has an inspector tool that lets the user click on a rendered page element and attach a textual comment (e.g. *\"make this red\"*, *\"change to 'Open Slide Rocks'\"*). Each comment is persisted as an in-source JSX marker inside `slides\u002F\u003CslideId>\u002Findex.tsx`.\n\nYour job: read those markers, perform the described edits, and delete the markers.\n\n> **Before making any page edit**, consult the **`slide-authoring`** skill — it is the technical reference for how `slides\u002F\u003Cid>\u002Findex.tsx` is structured (canvas, type scale, palette, assets, file contract). A comment like *\"make this bigger\"* or *\"change the accent colour\"* should be applied in a way that stays consistent with those rules.\n\n## Marker format\n\n```\n{\u002F* @slide-comment id=\"c-\u003C8hex>\" ts=\"\u003CISO>\" text=\"\u003Cbase64url(JSON)>\" *\u002F}\n```\n\n- Always sits on its own line as the **first child inside** the JSX element it refers to (i.e. between that element's opening `>` and its other children). The marker is dropped *into* its target, not floated above it.\n- `text` is base64url-encoded JSON: `{\"note\": \"...\", \"hint\"?: \"...\"}`.\n- Detection regex (authoritative — use exactly this):\n\n  ```\n  \u002F\\{\\\u002F\\*\\s*@slide-comment\\s+id=\"(c-[a-f0-9]+)\"\\s+ts=\"([^\"]+)\"\\s+text=\"([A-Za-z0-9_\\-]+={0,2})\"\\s*\\*\\\u002F\\}\u002Fg\n  ```\n\n## Procedure\n\n1. **Identify the target slide(s).**\n   - If the user names one (`getting-started`, `q2-roadmap`, etc.), work on that single `slides\u002F\u003CslideId>\u002Findex.tsx`.\n   - If they say \"all\" or don't specify, scan every `slides\u002F*\u002Findex.tsx`. Process each slide one at a time.\n\n2. **Read the file and find all markers.**\n   - Run the regex above against the whole file.\n   - For each match, base64url-decode `text` and `JSON.parse` it to get `{ note, hint? }`.\n   - Record each hit as `{ id, lineIndex (0-based), note, hint }`.\n   - If there are no markers, tell the user and stop.\n\n3. **Understand each comment in context.**\n   - The targeted JSX element is the **enclosing** element of the marker — i.e. read upward from the marker line until you reach the unclosed JSX opening tag whose body the marker lives in. That element is the target. (For self-closing elements like `\u003Cimg \u002F>`, the inspector hoists the marker to the nearest non-self-closing ancestor; in that case the comment usually refers to a child of the enclosing element rather than the enclosing element itself — use the `note` text to disambiguate.)\n   - Read enough surrounding code (parent element, sibling elements, inline styles) to apply the change faithfully. A comment inside a `\u003Cdiv>` with an inline `background` style usually refers to that element's styling, for example.\n   - If the `note` is ambiguous, do the smallest reasonable interpretation and mention the assumption in your summary.\n\n4. **Apply edits in reverse line order.**\n   - Sort markers by descending `lineIndex` and process one at a time, using the `Edit` tool.\n   - Processing top-down would invalidate line numbers for later markers as the file shrinks\u002Fgrows.\n\n5. **Remove each marker after applying its edit.**\n   - Delete the entire marker line including its trailing `\\n`.\n   - Never leave a marker behind for an edit you applied — that signals a failure. Markers deliberately skipped per the edge cases below stay in place.\n\n6. **Verify.**\n   - After all edits, re-read the file and confirm the only remaining markers are ones you reported as skipped.\n   - Confirm the edited JSX is well-formed (balanced tags, no dangling attributes). If the project's `package.json` has typecheck\u002Flint scripts, run them with the project's package manager; scaffolded projects ship neither TypeScript nor a linter — there, rely on the running dev server (or the `build` script) to surface compile errors. Fix any errors you introduced.\n\n7. **Report.**\n   - Summarise: `N applied, M skipped` plus a one-line description of each change (including the slide id).\n\n## base64url decoding helper\n\n```js\nfunction decode(s) {\n  const pad = s.length % 4 === 0 ? '' : '='.repeat(4 - (s.length % 4));\n  return Buffer.from(s.replace(\u002F-\u002Fg, '+').replace(\u002F_\u002Fg, '\u002F') + pad, 'base64').toString('utf8');\n}\n```\n\nYou can run this inline via `node -e '...'` if you need to inspect a payload; otherwise just reason about the decoded string.\n\n## Edge cases\n\n- **Marker with no enclosing JSX element** (shouldn't happen — the inspector won't write one — but if you find one): delete it and note as orphan.\n- **Multiple markers stacked on consecutive lines inside the same element**: they all refer to that enclosing element. Read their notes in source order to understand the combined intent, then apply and delete them bottom-up per step 4.\n- **Comment asks for something outside the target element's scope** (e.g. \"add a new page\"): do the closest-reasonable edit and mention the scope expansion in your summary.\n- **Can't resolve the comment** (e.g. truly ambiguous, or the file changed shape such that the target element doesn't exist): leave the marker in place and report it as skipped. Don't guess.\n\n## Do not\n\n- Do not touch `package.json`, `open-slide.config.ts`, or files outside `slides\u002F`.\n- Do not add dependencies.\n- Do not re-introduce markers or leave `TODO` breadcrumbs — the user already has a record in git.\n",{"name":5,"description":7},"main","d922e716d0801fbdf6c27f023b245c8da7e4c804","apps\u002Fpresentations\u002F.agents\u002Fskills\u002Fapply-comments",63,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot","https:\u002F\u002Ftobs.app","https:\u002F\u002Fgithub.com\u002FBotHarness","https:\u002F\u002Fdeepseekbot.app\u002F","2026-11-15 06:17:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add BotHarness\u002FDeepSeekBot --skill apply-comments",{"tool":38,"command":39},"bunx","bunx skills add BotHarness\u002FDeepSeekBot --skill apply-comments",{"tool":41,"command":42},"pnpm","pnpm dlx skills add BotHarness\u002FDeepSeekBot --skill apply-comments","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fapply-comments\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M7CY5WHFGASZATK5CQF05G0A","slide-authoring","Technical reference for writing or editing open-slide pages — file contract, 1920×1080 canvas, type scale, layout, palette\u002Fvisual direction, assets, speaker notes, stepped reveals, page transitions, and morph transitions. Consult this whenever you are about to write or modify any file under `slides\u002F\u003Cid>\u002F`, including from inside the `create-slide` or `apply-comments` workflows, or for any ad-hoc slide edit. Triggers on phrases like \"edit slide\", \"tweak this page\", \"fix the layout\", \"change the palette\", \"reveal one by one\", \"add a transition\", \"morph transition\", \"write the speaker notes\", \"generate the script \u002F talk track\", \"investigate the slide framework\", \"how do slides work here\".","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fslide-authoring\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7CY5NMS099ZRH9ECYS47ZKG","current-slide","Resolve which slide, page, and (optionally) selected element the user is currently viewing in the open-slide dev server. Consult this whenever the user references \"this page\", \"this slide\", \"this element\", \"the slide I'm on\", \"the current page\", or any deictic reference to slide content without naming it. Re-read `node_modules\u002F.open-slide\u002Fcurrent.json` at the start of every such turn — the user navigates between turns, so a value you read earlier in the conversation is almost certainly stale.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fcurrent-slide\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7CY5G6XHNY7Y8KVGGKF654E","create-theme","Use this skill when the user wants to create, draft, author, or extract a slide theme in this open-slide repo. Triggers on phrases like \"create a theme\", \"make a theme called X\", \"extract a theme from \u003Cslide>\", \"build a theme from these images\". Produces two paired files under `themes\u002F` — `\u003Cid>.md` (palette, typography, layout, fixed Title\u002FFooter components, motion) and `\u003Cid>.demo.tsx` (a runnable demo slide that the dev-UI Themes panel previews). Do NOT use for editing real slides — only for authoring the theme bundle.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fcreate-theme\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7CY5B0DZNEVRY95X3QEKW3C","create-slide","Use this skill when the user wants to create, draft, author, or generate new slides \u002F a presentation in this open-slide repo. Triggers on phrases like \"make slides about X\", \"make a deck about X\", \"create a presentation\", \"draft slides for\", \"new slide\", \"a deck with speaker notes \u002F a script\", or when the user asks to add content under `slides\u002F`. Do NOT use for editing the framework itself — only for authoring content inside `slides\u002F\u003Cid>\u002F`.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fcreate-slide\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7CY53ZCYB0P3GYM2V3MEN1N","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7CY524E4GQJMY7V5ZNB658W","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fwriting-fragments\u002FSKILL.md",[],[]]