[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MN7BAHT3YRQ56YSZDZ0VQ3":3,"skill-same:01M6MN7BAHT3YRQ56YSZDZ0VQ3":70},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6MN7BAHT3YRQ56YSZDZ0VQ3","create-theme",null,"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 a single markdown file under `themes\u002F\u003Cid>.md` describing palette, typography, layout, fixed Title\u002FFooter components, and motion philosophy. Do NOT use for editing slides themselves — only for authoring `themes\u002F\u003Cid>.md`.","arkhe-genesis\u002FArkhe-OS","arkhe-genesis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272629719?v=4","01M6KJDTSTJD2AD5RFPVZNGYCP","Rafael Oliveira","01M6KJDTXSTA997KDK184EA55A",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fcreate-theme\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"create","create theme","theme","do","components","author","open-slide","for","file","themes","triggers","draft","open","motion","images","only","use","repo","editing","slides","2026-11-10 10:12:30",false,"---\nname: create-theme\ndescription: 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 a single markdown file under `themes\u002F\u003Cid>.md` describing palette, typography, layout, fixed Title\u002FFooter components, and motion philosophy. Do NOT use for editing slides themselves — only for authoring `themes\u002F\u003Cid>.md`.\n---\n\n# Create a slide theme\n\nThis skill produces one markdown file under `themes\u002F\u003Cid>.md` that describes a reusable visual identity for slides — palette, typography, layout, fixed Title\u002FFooter\u002FEyebrow components, motion. Themes are agent-facing documentation, not executable runtime: a slide author reads the theme markdown and applies it when writing `slides\u002F\u003Cid>\u002Findex.tsx`.\n\nA theme is **distinct from a slide's `design` const**. The theme markdown is authoring-time aesthetic direction (read by `create-slide`, copied into slide source). A per-slide `const design: DesignSystem = { … }` (declared at the top of `slides\u002F\u003Cid>\u002Findex.tsx`) is the runtime tokens object the user can tweak from the Design panel in the dev UI. Both can coexist: the markdown theme commits the *direction*, the per-slide `design` const makes the slide *tweakable*. This skill only writes the markdown.\n\nYou only write a single file under `themes\u002F`. Never modify slides or other configuration. The canvas \u002F type-scale defaults that themes can override live in the **`slide-authoring`** skill — read it before writing the theme so your overrides are stated explicitly.\n\n## Step 1 — Identify the input source\n\nA theme can be derived from any combination of three input shapes:\n\n- **Image references** — paths or URLs to slide screenshots, mood-board images, brand assets.\n- **Free-text description** — prose describing the desired palette, fonts, feel.\n- **An existing slide** — `slides\u002F\u003Cid>\u002Findex.tsx` whose visual identity should be lifted out into a reusable theme.\n\nIf the user's original message already specifies the inputs unambiguously, skip the question and proceed. Otherwise call `AskUserQuestion` (multi-select) so they can pick one or more sources, and ask follow-ups (paths, slide id, prose) only as needed.\n\n## Step 2 — Gather raw inputs\n\n- **Images**: read each path with the `Read` tool (it accepts images). Note dominant colors as hex, type weight\u002Fstyle, layout rhythm, decorative motifs, and any recurring chrome (header bar, footer line, page numbers).\n- **Text**: extract explicit tokens (hex codes, font names, motion verbs) and implicit tone words (\"editorial\", \"playful\", \"brutalist\"). Resolve vague language into concrete decisions before writing.\n- **Existing slide**: read `slides\u002F\u003Cid>\u002Findex.tsx` and pull:\n  - The `palette` object → Palette section.\n  - Font constants and any `font-size` patterns → Typography section.\n  - Padding \u002F alignment patterns → Layout section.\n  - Recurring components (TrafficLights, Eyebrow, Footer-style helpers, WindowShell, …) → Fixed components section.\n  - `@keyframes` blocks and the shared `styles` string → Motion section.\n  - The aesthetic feel implied by the design → Aesthetic paragraph.\n\nWhen inputs disagree (e.g. images use blue but the description says green), ask the user which to honor.\n\n## Step 3 — Pick a theme id\n\nUse **kebab-case**, short, descriptive. Examples: `editorial-noir`, `brutalist-mono`, `pastel-soft`, `dev-terminal`. Check `themes\u002F` to avoid collisions.\n\n## Step 4 — Write `themes\u002F\u003Cid>.md`\n\nProduce a file with this exact section order. Section bodies adapt to the theme; the headings stay consistent across all themes.\n\n````markdown\n---\nname: \u003CHuman title, e.g. \"Editorial Noir\">\ndescription: \u003Cone-line elevator pitch>\nmode: light | dark | system\n---\n\n# \u003CTheme name>\n\n## Palette\n\n| Role   | Value     | Notes                          |\n| ------ | --------- | ------------------------------ |\n| bg     | `#0f172a` | page background                |\n| text   | `#f8fafc` | primary copy                   |\n| accent | `#fbbf24` | callouts, eyebrow, key numbers |\n| muted  | `#94a3b8` | secondary copy, dividers       |\n| ...    | ...       | extend as the theme requires   |\n\n## Typography\n\n- Display font: `\u003Cstack>` — weight 800–900 for headlines.\n- Body font: `\u003Cstack>` — weight 400–500.\n- Type-scale overrides (only list what differs from `slide-authoring` defaults):\n  - Hero title: 180 px (default 140–200 ✓)\n  - Body text: 36 px\n\n## Layout\n\n- Content padding: 120 px from canvas edges (1920 × 1080).\n- Alignment: left-aligned, single column.\n- Grid notes: optional 12-column overlay at 80 px gutter for content pages.\n\n## Fixed components\n\nThese are paste-ready. Copy them verbatim into a slide that uses this theme.\n\n### Title\n\n```tsx\nconst Title = ({ children }: { children: React.ReactNode }) => (\n  \u003Ch1\n    style={{\n      fontSize: 140,\n      fontWeight: 900,\n      lineHeight: 1.05,\n      letterSpacing: '-0.02em',\n      margin: 0,\n      color: '#f8fafc',\n    }}\n  >\n    {children}\n  \u003C\u002Fh1>\n);\n```\n\n### Footer\n\n```tsx\nconst Footer = ({ pageNum, total }: { pageNum: number; total: number }) => (\n  \u003Cdiv\n    style={{\n      position: 'absolute',\n      left: 120,\n      right: 120,\n      bottom: 60,\n      display: 'flex',\n      justifyContent: 'space-between',\n      fontSize: 24,\n      color: '#94a3b8',\n    }}\n  >\n    \u003Cspan>EDITORIAL NOIR · 2026\u003C\u002Fspan>\n    \u003Cspan>{pageNum} \u002F {total}\u003C\u002Fspan>\n  \u003C\u002Fdiv>\n);\n```\n\n### Eyebrow \u002F accents (optional)\n\n```tsx\nconst Eyebrow = ({ children }: { children: React.ReactNode }) => (\n  \u003Cdiv style={{ fontSize: 26, letterSpacing: '0.2em', color: '#fbbf24' }}>\n    {children}\n  \u003C\u002Fdiv>\n);\n```\n\n## Motion\n\n- Philosophy: static \u002F subtle \u002F rich — pick one and explain in one sentence.\n- Reusable keyframes (paste-ready, only if the philosophy is subtle or rich):\n\n```css\n@keyframes fadeUp {\n  from { opacity: 0; transform: translateY(24px); }\n  to   { opacity: 1; transform: translateY(0); }\n}\n```\n\n## Aesthetic\n\nOne paragraph. What it feels like, the references it draws on, what to avoid (e.g. \"no rounded corners; no gradients; no decorative emoji\"). Commit to a single direction — minimal, maximalist, editorial, retro, brutalist, soft\u002Fpastel, neon, paper\u002Fprint.\n\n## Example usage\n\n```tsx\nconst Cover: Page = () => (\n  \u003Cdiv style={{ width: '100%', height: '100%', background: '#0f172a', color: '#f8fafc', padding: 120, display: 'flex', flexDirection: 'column', justifyContent: 'center' }}>\n    \u003CEyebrow>CHAPTER 01\u003C\u002FEyebrow>\n    \u003CTitle>The Big Idea\u003C\u002FTitle>\n    \u003Cp style={{ fontSize: 36, color: '#94a3b8', maxWidth: 1200, marginTop: 32 }}>\n      A short subtitle that explains what this slide is about.\n    \u003C\u002Fp>\n    \u003CFooter pageNum={1} total={5} \u002F>\n  \u003C\u002Fdiv>\n);\n```\n````\n\n## Step 5 — Self-review\n\nRun this checklist before finishing:\n\n- [ ] Palette covers `bg` \u002F `text` \u002F `accent` \u002F `muted` at minimum, all as hex.\n- [ ] Type scale specifies hero, heading, body, caption sizes (or explicitly defers to `slide-authoring` defaults).\n- [ ] At least Title and Footer are defined as paste-ready React with concrete inline styles.\n- [ ] Motion section commits to one of static \u002F subtle \u002F rich.\n- [ ] Aesthetic paragraph names a single coherent direction.\n- [ ] File lives at `themes\u002F\u003Cid>.md` and only that file was created — no slide changes, no config changes.\n- [ ] Frontmatter `mode` is one of `light`, `dark`, `system`.\n\n## Step 6 — Hand off\n\nTell the user:\n\n- The theme id and file path.\n- That `\u002Fcreate-slide` will list it as a picker option on its next run.\n- A one-line summary of the look (palette + aesthetic).\n\nDo not run the dev server. Do not modify slides — even to demonstrate the theme; that is the user's next move.\n\n## Anti-patterns\n\n- ❌ Writing executable code in `themes\u002F\u003Cid>.md` outside the labeled component snippets — the file is documentation.\n- ❌ Producing more than one file. One theme = one `themes\u002F\u003Cid>.md`.\n- ❌ Inventing palette \u002F fonts when the user supplied images or an existing slide. Extract, don't fabricate.\n- ❌ Editing `slides\u002F`, `packages\u002F`, `package.json`, or `open-slide.config.ts`.\n- ❌ Skipping the Fixed components section. Title and Footer are the most common reuse target — they must be paste-ready.\n","# Create a slide theme\n\nThis skill produces one markdown file under `themes\u002F\u003Cid>.md` that describes a reusable visual identity for slides — palette, typography, layout, fixed Title\u002FFooter\u002FEyebrow components, motion. Themes are agent-facing documentation, not executable runtime: a slide author reads the theme markdown and applies it when writing `slides\u002F\u003Cid>\u002Findex.tsx`.\n\nA theme is **distinct from a slide's `design` const**. The theme markdown is authoring-time aesthetic direction (read by `create-slide`, copied into slide source). A per-slide `const design: DesignSystem = { … }` (declared at the top of `slides\u002F\u003Cid>\u002Findex.tsx`) is the runtime tokens object the user can tweak from the Design panel in the dev UI. Both can coexist: the markdown theme commits the *direction*, the per-slide `design` const makes the slide *tweakable*. This skill only writes the markdown.\n\nYou only write a single file under `themes\u002F`. Never modify slides or other configuration. The canvas \u002F type-scale defaults that themes can override live in the **`slide-authoring`** skill — read it before writing the theme so your overrides are stated explicitly.\n\n## Step 1 — Identify the input source\n\nA theme can be derived from any combination of three input shapes:\n\n- **Image references** — paths or URLs to slide screenshots, mood-board images, brand assets.\n- **Free-text description** — prose describing the desired palette, fonts, feel.\n- **An existing slide** — `slides\u002F\u003Cid>\u002Findex.tsx` whose visual identity should be lifted out into a reusable theme.\n\nIf the user's original message already specifies the inputs unambiguously, skip the question and proceed. Otherwise call `AskUserQuestion` (multi-select) so they can pick one or more sources, and ask follow-ups (paths, slide id, prose) only as needed.\n\n## Step 2 — Gather raw inputs\n\n- **Images**: read each path with the `Read` tool (it accepts images). Note dominant colors as hex, type weight\u002Fstyle, layout rhythm, decorative motifs, and any recurring chrome (header bar, footer line, page numbers).\n- **Text**: extract explicit tokens (hex codes, font names, motion verbs) and implicit tone words (\"editorial\", \"playful\", \"brutalist\"). Resolve vague language into concrete decisions before writing.\n- **Existing slide**: read `slides\u002F\u003Cid>\u002Findex.tsx` and pull:\n  - The `palette` object → Palette section.\n  - Font constants and any `font-size` patterns → Typography section.\n  - Padding \u002F alignment patterns → Layout section.\n  - Recurring components (TrafficLights, Eyebrow, Footer-style helpers, WindowShell, …) → Fixed components section.\n  - `@keyframes` blocks and the shared `styles` string → Motion section.\n  - The aesthetic feel implied by the design → Aesthetic paragraph.\n\nWhen inputs disagree (e.g. images use blue but the description says green), ask the user which to honor.\n\n## Step 3 — Pick a theme id\n\nUse **kebab-case**, short, descriptive. Examples: `editorial-noir`, `brutalist-mono`, `pastel-soft`, `dev-terminal`. Check `themes\u002F` to avoid collisions.\n\n## Step 4 — Write `themes\u002F\u003Cid>.md`\n\nProduce a file with this exact section order. Section bodies adapt to the theme; the headings stay consistent across all themes.\n\n````markdown\n---\nname: \u003CHuman title, e.g. \"Editorial Noir\">\ndescription: \u003Cone-line elevator pitch>\nmode: light | dark | system\n---\n\n# \u003CTheme name>\n\n## Palette\n\n| Role   | Value     | Notes                          |\n| ------ | --------- | ------------------------------ |\n| bg     | `#0f172a` | page background                |\n| text   | `#f8fafc` | primary copy                   |\n| accent | `#fbbf24` | callouts, eyebrow, key numbers |\n| muted  | `#94a3b8` | secondary copy, dividers       |\n| ...    | ...       | extend as the theme requires   |\n\n## Typography\n\n- Display font: `\u003Cstack>` — weight 800–900 for headlines.\n- Body font: `\u003Cstack>` — weight 400–500.\n- Type-scale overrides (only list what differs from `slide-authoring` defaults):\n  - Hero title: 180 px (default 140–200 ✓)\n  - Body text: 36 px\n\n## Layout\n\n- Content padding: 120 px from canvas edges (1920 × 1080).\n- Alignment: left-aligned, single column.\n- Grid notes: optional 12-column overlay at 80 px gutter for content pages.\n\n## Fixed components\n\nThese are paste-ready. Copy them verbatim into a slide that uses this theme.\n\n### Title\n\n```tsx\nconst Title = ({ children }: { children: React.ReactNode }) => (\n  \u003Ch1\n    style={{\n      fontSize: 140,\n      fontWeight: 900,\n      lineHeight: 1.05,\n      letterSpacing: '-0.02em',\n      margin: 0,\n      color: '#f8fafc',\n    }}\n  >\n    {children}\n  \u003C\u002Fh1>\n);\n```\n\n### Footer\n\n```tsx\nconst Footer = ({ pageNum, total }: { pageNum: number; total: number }) => (\n  \u003Cdiv\n    style={{\n      position: 'absolute',\n      left: 120,\n      right: 120,\n      bottom: 60,\n      display: 'flex',\n      justifyContent: 'space-between',\n      fontSize: 24,\n      color: '#94a3b8',\n    }}\n  >\n    \u003Cspan>EDITORIAL NOIR · 2026\u003C\u002Fspan>\n    \u003Cspan>{pageNum} \u002F {total}\u003C\u002Fspan>\n  \u003C\u002Fdiv>\n);\n```\n\n### Eyebrow \u002F accents (optional)\n\n```tsx\nconst Eyebrow = ({ children }: { children: React.ReactNode }) => (\n  \u003Cdiv style={{ fontSize: 26, letterSpacing: '0.2em', color: '#fbbf24' }}>\n    {children}\n  \u003C\u002Fdiv>\n);\n```\n\n## Motion\n\n- Philosophy: static \u002F subtle \u002F rich — pick one and explain in one sentence.\n- Reusable keyframes (paste-ready, only if the philosophy is subtle or rich):\n\n```css\n@keyframes fadeUp {\n  from { opacity: 0; transform: translateY(24px); }\n  to   { opacity: 1; transform: translateY(0); }\n}\n```\n\n## Aesthetic\n\nOne paragraph. What it feels like, the references it draws on, what to avoid (e.g. \"no rounded corners; no gradients; no decorative emoji\"). Commit to a single direction — minimal, maximalist, editorial, retro, brutalist, soft\u002Fpastel, neon, paper\u002Fprint.\n\n## Example usage\n\n```tsx\nconst Cover: Page = () => (\n  \u003Cdiv style={{ width: '100%', height: '100%', background: '#0f172a', color: '#f8fafc', padding: 120, display: 'flex', flexDirection: 'column', justifyContent: 'center' }}>\n    \u003CEyebrow>CHAPTER 01\u003C\u002FEyebrow>\n    \u003CTitle>The Big Idea\u003C\u002FTitle>\n    \u003Cp style={{ fontSize: 36, color: '#94a3b8', maxWidth: 1200, marginTop: 32 }}>\n      A short subtitle that explains what this slide is about.\n    \u003C\u002Fp>\n    \u003CFooter pageNum={1} total={5} \u002F>\n  \u003C\u002Fdiv>\n);\n```\n````\n\n## Step 5 — Self-review\n\nRun this checklist before finishing:\n\n- [ ] Palette covers `bg` \u002F `text` \u002F `accent` \u002F `muted` at minimum, all as hex.\n- [ ] Type scale specifies hero, heading, body, caption sizes (or explicitly defers to `slide-authoring` defaults).\n- [ ] At least Title and Footer are defined as paste-ready React with concrete inline styles.\n- [ ] Motion section commits to one of static \u002F subtle \u002F rich.\n- [ ] Aesthetic paragraph names a single coherent direction.\n- [ ] File lives at `themes\u002F\u003Cid>.md` and only that file was created — no slide changes, no config changes.\n- [ ] Frontmatter `mode` is one of `light`, `dark`, `system`.\n\n## Step 6 — Hand off\n\nTell the user:\n\n- The theme id and file path.\n- That `\u002Fcreate-slide` will list it as a picker option on its next run.\n- A one-line summary of the look (palette + aesthetic).\n\nDo not run the dev server. Do not modify slides — even to demonstrate the theme; that is the user's next move.\n\n## Anti-patterns\n\n- ❌ Writing executable code in `themes\u002F\u003Cid>.md` outside the labeled component snippets — the file is documentation.\n- ❌ Producing more than one file. One theme = one `themes\u002F\u003Cid>.md`.\n- ❌ Inventing palette \u002F fonts when the user supplied images or an existing slide. Extract, don't fabricate.\n- ❌ Editing `slides\u002F`, `packages\u002F`, `package.json`, or `open-slide.config.ts`.\n- ❌ Skipping the Fixed components section. Title and Footer are the most common reuse target — they must be paste-ready.\n",{"name":5,"description":7},"main","74cd3c4137064fdcde71ed9fe5c4bff58921d899","tools\u002F.agents\u002Fskills\u002Fcreate-theme",0,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS","https:\u002F\u002Fgithub.com\u002Farkhe-genesis","2026-11-08 09:08:55",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add arkhe-genesis\u002FArkhe-OS --skill create-theme",{"tool":62,"command":63},"bunx","bunx skills add arkhe-genesis\u002FArkhe-OS --skill create-theme",{"tool":65,"command":66},"pnpm","pnpm dlx skills add arkhe-genesis\u002FArkhe-OS --skill create-theme","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fcreate-theme\u002FSKILL.md",true,[],[71,94,112,131,155,174],{"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":44},"01M6MN97RPP1Q9BG489WHW70R8","career-ops","AI job search command center -- evaluate offers, generate CVs, scan portals, track applications","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.ai-integrations\u002Fvscode\u002F.claude\u002Fskills\u002Fcareer-ops\u002FSKILL.md",[],[78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93],"ops","career","career ops","track","applications","evaluate","mode","true","command center","cvs","scan","command","offers","Job Search","search","generate",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":44},"01M6MN93GFX8W9J1PCKDKZVD3N","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[101,102,40,103,104,105,106,107,85,108,109,110,111],"zoom out","zoom","how","context","code","it","perspective","re","you","with","understand",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":121,"publishedAt":44},"01M6MN8Y2ETBC91BGREF4D39JH","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[122,123,124,110,125,126,127,128,129,40,130,24],"write","write a skill","progressive disclosure","resources","new agent","structure","new skill","build","user",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":44},"01M6MN8RWE2V2PPFVPD0G8FHKF","triage","Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[137],{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},[133,139,140,24,141,142,143,144,145,146,147,40,148,149,31,150,151,152,153,154],"bugs","state machine","requests","machine","feature","roles","issue workflow","manage","issue","issues","state","feature requests","prepare","triage issues","workflow","review",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":166,"publishedAt":44},"01M6MN8KVDBD28672WMER7HPXM","to-prd","Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fto-prd\u002FSKILL.md",[161],{"categoryNo":162,"categoryName":163,"taxonomyType":164,"taxonomyTypeDesc":165},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[167,168,40,130,104,169,24,147,170,106,171,172,173],"to prd","prd","publish","issue tracker","project","conversation","tracker",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":44},"01M6MN8E9CGYVWVDDR0NJEFDBB","to-issues","Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fto-issues\u002FSKILL.md",[],[148,181,182,171,183,184,170,185,186,173,147,187,40,130,188,189,190,168,24],"to issues","spec","down","break","break down","tickets","implementation","work","convert","plan"]