[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BS8PZEC26MXCGXBAYMB77R":3,"skill-same:01M7BS8PZEC26MXCGXBAYMB77R":74},{"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":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7BS8PZEC26MXCGXBAYMB77R","orbit-github",null,"Open Orbit briefing skill — selected by the Orbit pipeline when\nGitHub is the user's only connected connector, or when the user\nexplicitly scopes their daily digest to GitHub. Pulls the past 24\nhours of PRs, review requests, issues, CI runs, and merges from the\nuser's authenticated GitHub connection and renders them in a layout\nthat mirrors GitHub's native Notifications + PR-diff visual language.\nThis skill should not be triggered manually — it is invoked by\nOrbit's daily-digest scheduler against live GitHub data.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Design-设计资源\u002FYYC3-Design-设计资源-open-design\u002Fplugins\u002F_official\u002Fexamples\u002Forbit-github\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: orbit-github\ndescription: |\n  Open Orbit briefing skill — selected by the Orbit pipeline when\n  GitHub is the user's only connected connector, or when the user\n  explicitly scopes their daily digest to GitHub. Pulls the past 24\n  hours of PRs, review requests, issues, CI runs, and merges from the\n  user's authenticated GitHub connection and renders them in a layout\n  that mirrors GitHub's native Notifications + PR-diff visual language.\n  This skill should not be triggered manually — it is invoked by\n  Orbit's daily-digest scheduler against live GitHub data.\ntriggers:\n  - \"github briefing\"\n  - \"github digest\"\n  - \"pr digest\"\n  - \"github 简报\"\n  - \"代码活动汇总\"\nod:\n  mode: prototype\n  platform: desktop\n  scenario: orbit\n  featured: 2\n  preview:\n    type: html\n    entry: index.html\n  design_system:\n    requires: false\n  example_prompt: \"Generate today's Open Orbit GitHub briefing. GitHub is my only connected connector — pull yesterday's PRs, review requests, issues, CI runs, and merges and render them as a GitHub Notifications + PR-diff page.\"\n---\n\n# Orbit · GitHub Briefing\n\nSingle-connector Orbit template scoped to GitHub.\n\n## ⚠️ Source-of-truth protocol (read this first)\n\n**Step 1.** Open and read the shipped `example.html` in this folder\nbefore writing any output. That file is the canonical design — your\njob is to **reproduce it**, not reinterpret it.\n\n**Step 2.** Mirror the example's structure 1:1:\n- Same DOM hierarchy and class names\n- Same nav-bar items (and only those)\n- Same left-rail filter list (and only those)\n- Same event groups in the same order, with the same row count\n- Same diff-preview placement, same CI-fail block, same attention block\n- Same `\u003Cscript>` block at the end (filter \u002F hover \u002F link injection)\n\n**Step 3.** You may refresh mock values (PR numbers, titles, times,\nCI commit messages) so they read as \"today\", but you must **not**\ninvent extra UI: no extra rail entries, no extra notifications,\nno extra event types, no extra badges, no extra chrome ornaments. If\nsomething is not already present in `example.html`, it does not\nbelong in your output.\n\nThe sections below are a **reference for tokens and visual language** —\nnot a license to extend the page.\n\n## ⚠️ Design system policy\n\nThis skill ships with its **own** complete visual language baked into\n`example.html` (GitHub's Primer chrome). The user must **not** be\nasked to pick or attach a design system, and you must **not** inject\nany external DESIGN.md tokens into the output.\n\n- If the active project has a design system attached, **ignore it**.\n- If the user supplies brand tokens or a Figma file, **ignore them**.\n- Use exclusively the colors \u002F fonts \u002F radii defined in `example.html`.\n\nThis is a hard constraint: the briefing must read as a real GitHub\npage, not as the user's brand.\n\n## Canvas tokens (use these exact values)\n\n```\npage bg:           #f6f8fa\ncard bg:           #ffffff\nnav bar:           #24292f  \u002F* GitHub black header *\u002F\nnav text:          #ffffff\nink:               #1f2328\nmuted:             #59636e\nborder:            #d0d7de\nhairline:          rgba(208,215,222,0.32)\n\nstate · open:      #1a7f37\nstate · merged:    #8250df\nstate · closed:    #cf222e\nstate · draft:     #6e7781\n\nattention bg:      #fff8c5  \u002F* yellow review-request block *\u002F\nattention border:  #d4a72c\nci-fail bg:        #ffebe9\nci-fail border:    #cf222e\n```\n\nType stack:\n- `-apple-system, BlinkMacSystemFont, \"Segoe UI\", \"Noto Sans\", Helvetica, Arial, sans-serif`\n- Sizes: nav 14px, headings 16\u002F20px, body 14px, meta 12px\n\n## Page sections\n\n1. **Top nav bar** — full-width, dark (`#24292f`), 60px tall.\n   Left: octocat SVG logo (white, 32px) + search input\n   (`rgba(255,255,255,0.08)` background, white placeholder ghosted).\n   Right: `+` plus dropdown, notifications bell with red dot if\n   unread > 0, round avatar.\n\n2. **Header row** — light bar under the nav, 56px.\n   Left: page breadcrumb `Inbox · Daily Digest · May 6`.\n   Right: filter dropdown chips (`Type ▾  Date ▾  Status ▾`).\n\n3. **Two-pane main**:\n   - **Left rail** (240px): vertical filter list. Items:\n     `Inbox · Saved · Done · All` then divider then\n     `Participating · Mentions · Review requests · Assigned · Comments`.\n     Active item: light gray pill background.\n   - **Main pane** (flex 1): event stream grouped by category.\n\n4. **Category groups in main pane** (in this order):\n   - **Review requests waiting on you** — yellow attention block\n     (bg `#fff8c5`, 1px border `#d4a72c`). Each row: avatar + repo\n     path + PR title + reviewer-state row of small dots\n     (✓ green \u002F ⏳ yellow \u002F ○ gray) + \"X of Y reviewers\" + age.\n   - **CI \u002F Checks** — each failed run is a red-bordered card\n     (border-color `#cf222e`, bg `#ffebe9`) with a `✗` red glyph,\n     run name, branch name (mono), commit message, age.\n   - **Issues assigned to you** — plain rows, status circle (open\n     green \u002F closed red), title, repo path, age, label pills.\n   - **Activity** — quieter rows for merges\u002Fcloses; muted text,\n     small `merged` purple pill or `closed` red pill.\n\n5. **Optional PR-diff preview** — inline under one PR row, show\n   2–3 lines of mock code in a 12px monospace block with red `−` \u002F\n   green `+` prefixed lines and `#ffebe9` \u002F `#dafbe1` row tints.\n\n6. **Footer** — single line, 12px muted:\n   `Open Orbit · auto-generated 06:42 · GitHub only`.\n\n## Pill \u002F chip rules\n\n- State pills: pill shape (border-radius 2em), 12px medium, 4×8 padding.\n  Foreground white, background by state color above.\n- Labels (`bug`, `p1`, `frontend` …): GitHub label rounded pill, each\n  with its own arbitrary color. Use varied real-world label hues.\n- Reviewer dots: 8px filled circles, 2px gap, with `✓ ⏳ ○` glyphs only\n  if you can keep them visually subtle.\n\n## Implementation constraints (paired do \u002F don't)\n\n| Don't | Do |\n|---|---|\n| Mix light and dark themes | Stay on the light Primer theme (`#f6f8fa` page bg, `#ffffff` cards) |\n| Use non-GitHub typography | Use `-apple-system, BlinkMacSystemFont, \"Segoe UI\", \"Noto Sans\", Helvetica, Arial, sans-serif` exclusively |\n| Render avatars as squares or rounded squares | Always circles, with overlap `≤ 6px` for reviewer stacks |\n| Use shadows \u002F gradients \u002F glows on chrome | Flat surfaces; differentiate with `#d0d7de` 1px borders |\n| Use lorem ipsum | Write real-shaped GitHub copy: PR titles like `feat: orbit briefing card`, branches like `chore\u002Fupgrade-deps`, commit subjects under 72 chars |\n| Render a CI failure as a normal row | Wrap in a red-bordered card (`#cf222e` border, `#ffebe9` bg) with a red `✗` glyph and run name |\n| Render a review request as a normal row | Sit it in the yellow attention block (`#fff8c5` bg, `#d4a72c` border) with reviewer status dots row |\n| Use placeholder repo names like `org\u002Frepo` | Use `nexu-io\u002Fopen-design` (this org's actual primary repo) |\n| Pluck arbitrary label colors | Use realistic dev-team hues — `bug` red, `enhancement` blue, `documentation` light blue, `frontend` purple |\n","# Orbit · GitHub Briefing\n\nSingle-connector Orbit template scoped to GitHub.\n\n## ⚠️ Source-of-truth protocol (read this first)\n\n**Step 1.** Open and read the shipped `example.html` in this folder\nbefore writing any output. That file is the canonical design — your\njob is to **reproduce it**, not reinterpret it.\n\n**Step 2.** Mirror the example's structure 1:1:\n- Same DOM hierarchy and class names\n- Same nav-bar items (and only those)\n- Same left-rail filter list (and only those)\n- Same event groups in the same order, with the same row count\n- Same diff-preview placement, same CI-fail block, same attention block\n- Same `\u003Cscript>` block at the end (filter \u002F hover \u002F link injection)\n\n**Step 3.** You may refresh mock values (PR numbers, titles, times,\nCI commit messages) so they read as \"today\", but you must **not**\ninvent extra UI: no extra rail entries, no extra notifications,\nno extra event types, no extra badges, no extra chrome ornaments. If\nsomething is not already present in `example.html`, it does not\nbelong in your output.\n\nThe sections below are a **reference for tokens and visual language** —\nnot a license to extend the page.\n\n## ⚠️ Design system policy\n\nThis skill ships with its **own** complete visual language baked into\n`example.html` (GitHub's Primer chrome). The user must **not** be\nasked to pick or attach a design system, and you must **not** inject\nany external DESIGN.md tokens into the output.\n\n- If the active project has a design system attached, **ignore it**.\n- If the user supplies brand tokens or a Figma file, **ignore them**.\n- Use exclusively the colors \u002F fonts \u002F radii defined in `example.html`.\n\nThis is a hard constraint: the briefing must read as a real GitHub\npage, not as the user's brand.\n\n## Canvas tokens (use these exact values)\n\n```\npage bg:           #f6f8fa\ncard bg:           #ffffff\nnav bar:           #24292f  \u002F* GitHub black header *\u002F\nnav text:          #ffffff\nink:               #1f2328\nmuted:             #59636e\nborder:            #d0d7de\nhairline:          rgba(208,215,222,0.32)\n\nstate · open:      #1a7f37\nstate · merged:    #8250df\nstate · closed:    #cf222e\nstate · draft:     #6e7781\n\nattention bg:      #fff8c5  \u002F* yellow review-request block *\u002F\nattention border:  #d4a72c\nci-fail bg:        #ffebe9\nci-fail border:    #cf222e\n```\n\nType stack:\n- `-apple-system, BlinkMacSystemFont, \"Segoe UI\", \"Noto Sans\", Helvetica, Arial, sans-serif`\n- Sizes: nav 14px, headings 16\u002F20px, body 14px, meta 12px\n\n## Page sections\n\n1. **Top nav bar** — full-width, dark (`#24292f`), 60px tall.\n   Left: octocat SVG logo (white, 32px) + search input\n   (`rgba(255,255,255,0.08)` background, white placeholder ghosted).\n   Right: `+` plus dropdown, notifications bell with red dot if\n   unread > 0, round avatar.\n\n2. **Header row** — light bar under the nav, 56px.\n   Left: page breadcrumb `Inbox · Daily Digest · May 6`.\n   Right: filter dropdown chips (`Type ▾  Date ▾  Status ▾`).\n\n3. **Two-pane main**:\n   - **Left rail** (240px): vertical filter list. Items:\n     `Inbox · Saved · Done · All` then divider then\n     `Participating · Mentions · Review requests · Assigned · Comments`.\n     Active item: light gray pill background.\n   - **Main pane** (flex 1): event stream grouped by category.\n\n4. **Category groups in main pane** (in this order):\n   - **Review requests waiting on you** — yellow attention block\n     (bg `#fff8c5`, 1px border `#d4a72c`). Each row: avatar + repo\n     path + PR title + reviewer-state row of small dots\n     (✓ green \u002F ⏳ yellow \u002F ○ gray) + \"X of Y reviewers\" + age.\n   - **CI \u002F Checks** — each failed run is a red-bordered card\n     (border-color `#cf222e`, bg `#ffebe9`) with a `✗` red glyph,\n     run name, branch name (mono), commit message, age.\n   - **Issues assigned to you** — plain rows, status circle (open\n     green \u002F closed red), title, repo path, age, label pills.\n   - **Activity** — quieter rows for merges\u002Fcloses; muted text,\n     small `merged` purple pill or `closed` red pill.\n\n5. **Optional PR-diff preview** — inline under one PR row, show\n   2–3 lines of mock code in a 12px monospace block with red `−` \u002F\n   green `+` prefixed lines and `#ffebe9` \u002F `#dafbe1` row tints.\n\n6. **Footer** — single line, 12px muted:\n   `Open Orbit · auto-generated 06:42 · GitHub only`.\n\n## Pill \u002F chip rules\n\n- State pills: pill shape (border-radius 2em), 12px medium, 4×8 padding.\n  Foreground white, background by state color above.\n- Labels (`bug`, `p1`, `frontend` …): GitHub label rounded pill, each\n  with its own arbitrary color. Use varied real-world label hues.\n- Reviewer dots: 8px filled circles, 2px gap, with `✓ ⏳ ○` glyphs only\n  if you can keep them visually subtle.\n\n## Implementation constraints (paired do \u002F don't)\n\n| Don't | Do |\n|---|---|\n| Mix light and dark themes | Stay on the light Primer theme (`#f6f8fa` page bg, `#ffffff` cards) |\n| Use non-GitHub typography | Use `-apple-system, BlinkMacSystemFont, \"Segoe UI\", \"Noto Sans\", Helvetica, Arial, sans-serif` exclusively |\n| Render avatars as squares or rounded squares | Always circles, with overlap `≤ 6px` for reviewer stacks |\n| Use shadows \u002F gradients \u002F glows on chrome | Flat surfaces; differentiate with `#d0d7de` 1px borders |\n| Use lorem ipsum | Write real-shaped GitHub copy: PR titles like `feat: orbit briefing card`, branches like `chore\u002Fupgrade-deps`, commit subjects under 72 chars |\n| Render a CI failure as a normal row | Wrap in a red-bordered card (`#cf222e` border, `#ffebe9` bg) with a red `✗` glyph and run name |\n| Render a review request as a normal row | Sit it in the yellow attention block (`#fff8c5` bg, `#d4a72c` border) with reviewer status dots row |\n| Use placeholder repo names like `org\u002Frepo` | Use `nexu-io\u002Fopen-design` (this org's actual primary repo) |\n| Pluck arbitrary label colors | Use realistic dev-team hues — `bug` red, `enhancement` blue, `documentation` light blue, `frontend` purple |\n",{"od":24,"name":5,"triggers":34,"description":40},{"mode":25,"preview":26,"featured":29,"platform":30,"scenario":31,"design_system":32,"example_prompt":33},"prototype",{"type":27,"entry":28},"html","index.html",2,"desktop","orbit",{"requires":20},"Generate today's Open Orbit GitHub briefing. GitHub is my only connected connector — pull yesterday's PRs, review requests, issues, CI runs, and merges and render them as a GitHub Notifications + PR-diff page.",[35,36,37,38,39],"github briefing","github digest","pr digest","github 简报","代码活动汇总","Open Orbit briefing skill — selected by the Orbit pipeline when\nGitHub is the user's only connected connector, or when the user\nexplicitly scopes their daily digest to GitHub. Pulls the past 24\nhours of PRs, review requests, issues, CI runs, and merges from the\nuser's authenticated GitHub connection and renders them in a layout\nthat mirrors GitHub's native Notifications + PR-diff visual language.\nThis skill should not be triggered manually — it is invoked by\nOrbit's daily-digest scheduler against live GitHub data.\n","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Design-设计资源\u002FYYC3-Design-设计资源-open-design\u002Fplugins\u002F_official\u002Fexamples\u002Forbit-github",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill orbit-github",{"tool":56,"command":57},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill orbit-github",{"tool":59,"command":60},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill orbit-github","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Design-设计资源\u002FYYC3-Design-设计资源-open-design\u002Fplugins\u002F_official\u002Fexamples\u002Forbit-github\u002FSKILL.md",true,[64,70],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"example.html","REFERENCE","参考文档",30537,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Design-设计资源\u002FYYC3-Design-设计资源-open-design\u002Fplugins\u002F_official\u002Fexamples\u002Forbit-github\u002Fexample.html",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"open-design.json",9731,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Design-设计资源\u002FYYC3-Design-设计资源-open-design\u002Fplugins\u002F_official\u002Fexamples\u002Forbit-github\u002Fopen-design.json",[75,82,89,96,103,110],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]