[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CXQAFRYM55392V8ABDNFRJ":3,"skill-same:01M7CXQAFRYM55392V8ABDNFRJ":76},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7CXQAFRYM55392V8ABDNFRJ","expo-ui",null,"Build native UI with the @expo\u002Fui package: real SwiftUI on iOS and Jetpack Compose on Android. Default to @expo\u002Fui for sheets (BottomSheet), pickers, sliders, toggles, menus, and grouped-form sections — do NOT reach for Reanimated, @gorhom\u002Fbottom-sheet, or RN built-in Picker\u002FSwitch; use @expo\u002Fui instead. Fall back to RN built-ins only when @expo\u002Fui is missing the component. NOTE: @expo\u002Fui List renders native grouped rows like an iOS Settings screen — it is NOT a virtualized list; use FlatList\u002FFlashList for large datasets. Covers universal components (Host, Column, Row, Button, Text, List, BottomSheet, FieldGroup, Switch, Slider, Picker, Menu), drop-in replacements for RN community libraries, and platform-specific SwiftUI\u002FJetpack Compose trees. Not for Expo Router navigation, Reanimated, or data fetching.","BotHarness\u002FDeepSeekBot","BotHarness","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F330270786?v=4","01M7CX37EXWM53FHAQ28JNKZTZ","01M7CX37FHA8NY5D2KXFZWV63Y",852,"MIT","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: expo-ui\ndescription: \"Build native UI with the @expo\u002Fui package: real SwiftUI on iOS and Jetpack Compose on Android. Default to @expo\u002Fui for sheets (BottomSheet), pickers, sliders, toggles, menus, and grouped-form sections — do NOT reach for Reanimated, @gorhom\u002Fbottom-sheet, or RN built-in Picker\u002FSwitch; use @expo\u002Fui instead. Fall back to RN built-ins only when @expo\u002Fui is missing the component. NOTE: @expo\u002Fui List renders native grouped rows like an iOS Settings screen — it is NOT a virtualized list; use FlatList\u002FFlashList for large datasets. Covers universal components (Host, Column, Row, Button, Text, List, BottomSheet, FieldGroup, Switch, Slider, Picker, Menu), drop-in replacements for RN community libraries, and platform-specific SwiftUI\u002FJetpack Compose trees. Not for Expo Router navigation, Reanimated, or data fetching.\"\nversion: 1.0.0\nlicense: MIT\nallowed-tools: \"Bash(node *expo-ui\u002Fscripts\u002Flist-components.js *)\"\n---\n\n# Expo UI (`@expo\u002Fui`)\n\n`@expo\u002Fui` renders real native UI from React: SwiftUI on iOS, Jetpack Compose on Android. It also ships drop-in replacements for migrating off RN community UI libraries.\n\n> These instructions track the latest Expo SDK. The **universal** layer requires **SDK 56+** and works in Expo Go — no custom build needed. Drop-in replacements and the platform-specific layers also exist on SDK 55. For component details on a specific SDK, refer to the Expo UI docs for that version.\n\n## Installation\n\n```bash\nnpx expo install @expo\u002Fui\n```\n\nEvery `@expo\u002Fui` tree — universal or platform-specific — must be wrapped in `Host`.\n\n## Use @expo\u002Fui by default — don't reach for RN alternatives first\n\n**Before using Reanimated, `@gorhom\u002Fbottom-sheet`, React Native's built-in `Switch`\u002F`Picker`, or any community UI library for the items below, use `@expo\u002Fui` instead.** Only fall back to RN built-ins when `@expo\u002Fui` is missing the component.\n\n| Need | Use |\n|------|-----|\n| Slide-up sheet \u002F bottom sheet | `BottomSheet` from `@expo\u002Fui` — **not** Reanimated or `@gorhom\u002Fbottom-sheet` |\n| Grouped native list rows (settings\u002Fform-style) | `List` + `ListItem` from `@expo\u002Fui` — **not** `FlatList` (see note below) |\n| Toggle | `Switch` from `@expo\u002Fui` |\n| Slider | `Slider` from `@expo\u002Fui` |\n| Date\u002Ftime picker | `@expo\u002Fui\u002Fcommunity\u002Fdatetimepicker` |\n| Menu | `Menu` from `@expo\u002Fui` |\n| Form section with label | `FieldGroup` from `@expo\u002Fui` |\n| Collapsible section | `Collapsible` from `@expo\u002Fui` |\n\n> **`List` is NOT a virtualized scrolling list.** It renders native grouped table rows — the visual look of an iOS Settings screen or a form section, with disclosure indicators and native row styling. Each `ListItem` is a native node on the JS thread; rows are not recycled. For any list with large or unknown-length data (feeds, search results, catalogs), use **`FlatList`** or **`FlashList`** instead. `List` is the right choice for short, fixed-length groups: a settings screen, a detail panel's rows, a fixed menu.\n\n**`BottomSheet` example** (use this for map pin details, action sheets, detail panels — not Reanimated):\n\n```tsx\nimport { Host, BottomSheet, Column, Text } from '@expo\u002Fui';\nimport { useState } from 'react';\n\nexport default function MapScreen() {\n  const [isOpen, setIsOpen] = useState(false);\n\n  return (\n    \u003CView style={{ flex: 1 }}>\n      \u003CMapView onMarkerPress={() => setIsOpen(true)} \u002F>\n      \u003CHost>\n        \u003CBottomSheet\n          isPresented={isOpen}\n          onDismiss={() => setIsOpen(false)}\n          snapPoints={['half', 'full']}\n        >\n          \u003CColumn>\n            \u003CText>Café name\u003C\u002FText>\n            \u003CText>Address\u003C\u002FText>\n          \u003C\u002FColumn>\n        \u003C\u002FBottomSheet>\n      \u003C\u002FHost>\n    \u003C\u002FView>\n  );\n}\n```\n\n`BottomSheet` uses `isPresented`\u002F`onDismiss` — **not** `isOpened`, `isOpen`, `onIsOpenedChange`, or `onChange` (those are `@gorhom\u002Fbottom-sheet` props and will silently do nothing). `snapPoints` accepts `'half'`, `'full'`, `{ fraction: 0.5 }`, or `{ height: 400 }` and is optional (auto-sizes to content when omitted).\n\n## Choosing an approach\n\nWork down this list and stop at the first layer that meets the need:\n\n1. **Universal components — start here.** Import from the `@expo\u002Fui` root. One component tree runs unmodified on iOS, Android, and web from a single source (Compose on Android, SwiftUI on iOS, `react-native-web`\u002F`react-dom` on web). No platform file splits. → `.\u002Freferences\u002Funiversal.md`\n\n2. **Platform-specific (SwiftUI \u002F Jetpack Compose).** Import from `@expo\u002Fui\u002Fswift-ui` or `@expo\u002Fui\u002Fjetpack-compose`. Use **only** when the universal layer is missing a component or modifier you need, or when you need platform-specific behavior or optimization. **Downside:** you write two trees and split them into `.ios.tsx` \u002F `.android.tsx` files (or branch on `Platform.OS`) — more code to maintain.\n\n   > **`@expo\u002Fui\u002Fswift-ui` is iOS-only. `@expo\u002Fui\u002Fjetpack-compose` is Android-only.** Importing either in a file that runs on the other platform will crash at runtime with \"Unable to get view config\" errors. Isolate platform-specific trees in `.ios.tsx` \u002F `.android.tsx` files placed in `components\u002F` (never inside `app\u002F` — Expo Router does not support platform extensions for route files), or guard with `Platform.OS` in a regular route file. `Host` must always be imported from `@expo\u002Fui` (the universal package root), not from the platform-specific sub-packages. → `.\u002Freferences\u002Fswift-ui.md` and `.\u002Freferences\u002Fjetpack-compose.md`\n\n**Already using an RN community UI library?** `@expo\u002Fui` also ships **drop-in replacements** — API-compatible swaps for popular libraries (`@gorhom\u002Fbottom-sheet`, `@react-native-community\u002Fdatetimepicker`, and more), imported from `@expo\u002Fui\u002Fcommunity\u002F\u003Cname>`. This is a migration side-path for replacing an existing dependency, not a step in the universal-vs-platform decision above. → `.\u002Freferences\u002Fdrop-in-replacements.md`\n\n## References\n\nConsult these resources as needed:\n\n```\nreferences\u002F\n  universal.md             Universal @expo\u002Fui components and when to use them (SDK 56+)\n  drop-in-replacements.md  API-compatible replacements for RN community UI libraries\n  swift-ui.md              Platform-specific iOS UI: @expo\u002Fui\u002Fswift-ui components, modifiers, RNHostView, useNativeState\n  jetpack-compose.md       Platform-specific Android UI: @expo\u002Fui\u002Fjetpack-compose components, modifiers, LazyColumn caveat, icons, useNativeState\n```\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes submit-expo-feedback@latest --category skills --subject \"expo-ui\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.\n","# Expo UI (`@expo\u002Fui`)\n\n`@expo\u002Fui` renders real native UI from React: SwiftUI on iOS, Jetpack Compose on Android. It also ships drop-in replacements for migrating off RN community UI libraries.\n\n> These instructions track the latest Expo SDK. The **universal** layer requires **SDK 56+** and works in Expo Go — no custom build needed. Drop-in replacements and the platform-specific layers also exist on SDK 55. For component details on a specific SDK, refer to the Expo UI docs for that version.\n\n## Installation\n\n```bash\nnpx expo install @expo\u002Fui\n```\n\nEvery `@expo\u002Fui` tree — universal or platform-specific — must be wrapped in `Host`.\n\n## Use @expo\u002Fui by default — don't reach for RN alternatives first\n\n**Before using Reanimated, `@gorhom\u002Fbottom-sheet`, React Native's built-in `Switch`\u002F`Picker`, or any community UI library for the items below, use `@expo\u002Fui` instead.** Only fall back to RN built-ins when `@expo\u002Fui` is missing the component.\n\n| Need | Use |\n|------|-----|\n| Slide-up sheet \u002F bottom sheet | `BottomSheet` from `@expo\u002Fui` — **not** Reanimated or `@gorhom\u002Fbottom-sheet` |\n| Grouped native list rows (settings\u002Fform-style) | `List` + `ListItem` from `@expo\u002Fui` — **not** `FlatList` (see note below) |\n| Toggle | `Switch` from `@expo\u002Fui` |\n| Slider | `Slider` from `@expo\u002Fui` |\n| Date\u002Ftime picker | `@expo\u002Fui\u002Fcommunity\u002Fdatetimepicker` |\n| Menu | `Menu` from `@expo\u002Fui` |\n| Form section with label | `FieldGroup` from `@expo\u002Fui` |\n| Collapsible section | `Collapsible` from `@expo\u002Fui` |\n\n> **`List` is NOT a virtualized scrolling list.** It renders native grouped table rows — the visual look of an iOS Settings screen or a form section, with disclosure indicators and native row styling. Each `ListItem` is a native node on the JS thread; rows are not recycled. For any list with large or unknown-length data (feeds, search results, catalogs), use **`FlatList`** or **`FlashList`** instead. `List` is the right choice for short, fixed-length groups: a settings screen, a detail panel's rows, a fixed menu.\n\n**`BottomSheet` example** (use this for map pin details, action sheets, detail panels — not Reanimated):\n\n```tsx\nimport { Host, BottomSheet, Column, Text } from '@expo\u002Fui';\nimport { useState } from 'react';\n\nexport default function MapScreen() {\n  const [isOpen, setIsOpen] = useState(false);\n\n  return (\n    \u003CView style={{ flex: 1 }}>\n      \u003CMapView onMarkerPress={() => setIsOpen(true)} \u002F>\n      \u003CHost>\n        \u003CBottomSheet\n          isPresented={isOpen}\n          onDismiss={() => setIsOpen(false)}\n          snapPoints={['half', 'full']}\n        >\n          \u003CColumn>\n            \u003CText>Café name\u003C\u002FText>\n            \u003CText>Address\u003C\u002FText>\n          \u003C\u002FColumn>\n        \u003C\u002FBottomSheet>\n      \u003C\u002FHost>\n    \u003C\u002FView>\n  );\n}\n```\n\n`BottomSheet` uses `isPresented`\u002F`onDismiss` — **not** `isOpened`, `isOpen`, `onIsOpenedChange`, or `onChange` (those are `@gorhom\u002Fbottom-sheet` props and will silently do nothing). `snapPoints` accepts `'half'`, `'full'`, `{ fraction: 0.5 }`, or `{ height: 400 }` and is optional (auto-sizes to content when omitted).\n\n## Choosing an approach\n\nWork down this list and stop at the first layer that meets the need:\n\n1. **Universal components — start here.** Import from the `@expo\u002Fui` root. One component tree runs unmodified on iOS, Android, and web from a single source (Compose on Android, SwiftUI on iOS, `react-native-web`\u002F`react-dom` on web). No platform file splits. → `.\u002Freferences\u002Funiversal.md`\n\n2. **Platform-specific (SwiftUI \u002F Jetpack Compose).** Import from `@expo\u002Fui\u002Fswift-ui` or `@expo\u002Fui\u002Fjetpack-compose`. Use **only** when the universal layer is missing a component or modifier you need, or when you need platform-specific behavior or optimization. **Downside:** you write two trees and split them into `.ios.tsx` \u002F `.android.tsx` files (or branch on `Platform.OS`) — more code to maintain.\n\n   > **`@expo\u002Fui\u002Fswift-ui` is iOS-only. `@expo\u002Fui\u002Fjetpack-compose` is Android-only.** Importing either in a file that runs on the other platform will crash at runtime with \"Unable to get view config\" errors. Isolate platform-specific trees in `.ios.tsx` \u002F `.android.tsx` files placed in `components\u002F` (never inside `app\u002F` — Expo Router does not support platform extensions for route files), or guard with `Platform.OS` in a regular route file. `Host` must always be imported from `@expo\u002Fui` (the universal package root), not from the platform-specific sub-packages. → `.\u002Freferences\u002Fswift-ui.md` and `.\u002Freferences\u002Fjetpack-compose.md`\n\n**Already using an RN community UI library?** `@expo\u002Fui` also ships **drop-in replacements** — API-compatible swaps for popular libraries (`@gorhom\u002Fbottom-sheet`, `@react-native-community\u002Fdatetimepicker`, and more), imported from `@expo\u002Fui\u002Fcommunity\u002F\u003Cname>`. This is a migration side-path for replacing an existing dependency, not a step in the universal-vs-platform decision above. → `.\u002Freferences\u002Fdrop-in-replacements.md`\n\n## References\n\nConsult these resources as needed:\n\n```\nreferences\u002F\n  universal.md             Universal @expo\u002Fui components and when to use them (SDK 56+)\n  drop-in-replacements.md  API-compatible replacements for RN community UI libraries\n  swift-ui.md              Platform-specific iOS UI: @expo\u002Fui\u002Fswift-ui components, modifiers, RNHostView, useNativeState\n  jetpack-compose.md       Platform-specific Android UI: @expo\u002Fui\u002Fjetpack-compose components, modifiers, LazyColumn caveat, icons, useNativeState\n```\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes submit-expo-feedback@latest --category skills --subject \"expo-ui\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.\n",{"name":5,"license":14,"version":23,"description":7,"allowed-tools":24},"1.0.0","Bash(node *expo-ui\u002Fscripts\u002Flist-components.js *)","main","d922e716d0801fbdf6c27f023b245c8da7e4c804",".agents\u002Fskills\u002Fexpo-ui",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add BotHarness\u002FDeepSeekBot --skill expo-ui",{"tool":40,"command":41},"bunx","bunx skills add BotHarness\u002FDeepSeekBot --skill expo-ui",{"tool":43,"command":44},"pnpm","pnpm dlx skills add BotHarness\u002FDeepSeekBot --skill expo-ui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002FSKILL.md",true,[48,54,58,62,66,70],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",722,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fdrop-in-replacements.md",2085,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002Freferences\u002Fdrop-in-replacements.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fjetpack-compose.md",5517,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002Freferences\u002Fjetpack-compose.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fswift-ui.md",4397,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002Freferences\u002Fswift-ui.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Funiversal.md",4792,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002Freferences\u002Funiversal.md",{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Flist-components.js","SCRIPT","脚本",7343,"https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002Fscripts\u002Flist-components.js",[77,84,91,98,105,112],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M7CY57ED279GA6QC3BFMPXG5","apply-comments","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`.","https:\u002F\u002Fgithub.com\u002FBotHarness\u002FDeepSeekBot\u002Fblob\u002Fmain\u002Fapps\u002Fpresentations\u002F.agents\u002Fskills\u002Fapply-comments\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"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",[],[]]