[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CHTX9SCTP67MY2P21BB5D4":3,"skill-same:01M6CHTX9SCTP67MY2P21BB5D4":84},{"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":22,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":63,"install":64,"resources":77},"01M6CHTX9SCTP67MY2P21BB5D4","sero-prototype",null,"Create and review interactive Sero UX prototypes in the styleguide. Use when\nthe user asks for a prototype, mockup, interaction concept, design\nexploration, UX review with a reviewable artifact, or a proposed Sero UI\nbefore production implementation. Trigger for work in\n`apps\u002Fstyleguide\u002Fpublic\u002Fprototypes\u002F` and for requests that say \"prototype\nbefore implementing\", \"show me first\", or \"make this match Sero\".","sero-labs\u002Fsero","sero-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F278893820?v=4","01M6CHSF0GA1ZZSBGVB5ESH37Q","01M6CHSF4WD1EGGY0RNFHQ5R4N",28,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsero-labs\u002Fsero\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsero-prototype\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"prototype","sero prototype","say","when","implementing","mockup","make","interaction","apps","artifact","me","exploration","show","implementation","design exploration","design","use","ux review","interactive","public","work","show me","first","Production","ui","ux","create","review","2026-11-10 10:12:30",false,"---\nname: sero-prototype\ndescription: |\n  Create and review interactive Sero UX prototypes in the styleguide. Use when\n  the user asks for a prototype, mockup, interaction concept, design\n  exploration, UX review with a reviewable artifact, or a proposed Sero UI\n  before production implementation. Trigger for work in\n  `apps\u002Fstyleguide\u002Fpublic\u002Fprototypes\u002F` and for requests that say \"prototype\n  before implementing\", \"show me first\", or \"make this match Sero\".\n---\n\n# Creating Sero prototypes\n\nBuild a reviewable design artifact that matches the current Sero desktop UI.\nDo not treat a prototype as production implementation.\n\n## Non-negotiable rules\n\n- Store every deliverable under `apps\u002Fstyleguide\u002Fpublic\u002Fprototypes\u002F`.\n- Link every interactive prototype from\n  `apps\u002Fstyleguide\u002Fsrc\u002FPrototypeArchive.tsx`.\n- Never deliver a prototype from `\u002Ftmp`, a clipboard path, or another protected\n  directory.\n- Inspect the closest existing prototype before creating a new one. Reuse its\n  useful structure and interaction patterns, but verify them against the current\n  product source because archived prototypes can be outdated.\n- Do not edit production UI while the user is still reviewing the prototype.\n- Show only controls and behavior supported by the proposed design. Do not add\n  decorative controls that imply unsupported functionality.\n- Use ASD-STE100 Simplified Technical English for labels and explanatory copy.\n\n## Workflow\n\n### 1. Define the review question\n\nState what the prototype must help the user decide. Extract these items from\nthe request and screenshots:\n\n- target workflow and entry point\n- behavior that must match an existing Sero surface\n- supported and unsupported actions\n- key states the user must compare\n- unresolved product choices\n\nAsk focused questions before building only when different answers would change\nthe interaction model. If the user asked to discuss before implementation, stop\nafter the prototype and review notes.\n\n### 2. Inspect Sero before drawing\n\nRead the smallest relevant set of sources:\n\n1. The current production components for the feature and the Sero surface it\n   must match.\n2. `packages\u002Fui\u002Fsrc\u002Fstyles\u002Fglobals.css` for current tokens, typography, focus,\n   radii, and status colors.\n3. Related shared components under `packages\u002Fui\u002Fsrc\u002Fcomponents\u002F`.\n4. The closest prototype in `apps\u002Fstyleguide\u002Fpublic\u002Fprototypes\u002F`.\n5. `apps\u002Fstyleguide\u002Fsrc\u002FPrototypeArchive.tsx` to understand current names and\n   avoid duplicate entries.\n\nFor changes to an existing concept, inspect its saved prototype first. Create a\nnew descriptive prototype file unless the user explicitly asks to replace the\nhistorical artifact.\n\n### 3. Choose the artifact\n\nUse an interactive standalone HTML prototype by default. Name it with a short,\nlowercase kebab-case slug:\n\n```text\napps\u002Fstyleguide\u002Fpublic\u002Fprototypes\u002F\u003Cconcept>.html\n```\n\nUse `prototypes\u002F\u003Cconcept>\u002Findex.html` with adjacent CSS, JavaScript, or image\nassets when a single HTML file would become hard to review or exceed the\nrepository file-size rules. Do not depend on a CDN or remote runtime. The\nprototype must work through the styleguide Vite server without network access.\n\nUse static images only when interaction adds no review value. Put persistent\nreview captures in:\n\n```text\napps\u002Fstyleguide\u002Fpublic\u002Fprototypes\u002Fscreenshots\u002F\u003Cconcept>\u002F\n```\n\n### 4. Match the product\n\n- Copy semantic token names and current values from the Sero design system.\n  Do not invent a second palette.\n- Match the current desktop layout, density, spacing, border treatment,\n  typography, active states, and control placement.\n- Use standard Sero font sizes. In React or Tailwind prototypes, use utilities\n  such as `text-xs`, `text-sm`, and `text-base` instead of arbitrary sizes.\n- Use inline Lucide SVG geometry or repository-owned assets. Do not substitute\n  emoji or unrelated Unicode glyphs for product icons.\n- Use realistic, sanitized Sero data. Keep names and copy short.\n- Preserve the hierarchy and interaction language of the product surface being\n  matched. A different runtime or backend must not create a different visual\n  system without a product reason.\n- Use clear focus, hover, selected, disabled, loading, streaming, success, and\n  error states where they affect the proposed workflow.\n- Respect `prefers-reduced-motion`. Avoid animation that does not explain a\n  state change.\n\nIf the prototype explores alternatives, label each option and keep the data and\nviewport consistent so the user can compare the design rather than the content.\n\n### 5. Make the important behavior real\n\nImplement the interactions needed for review, not every product feature. Common\nexamples include:\n\n- opening and closing menus, popovers, and dialogs\n- search and filtering\n- keyboard focus, Enter, arrow keys when applicable, and Escape\n- adding, selecting, renaming, or deleting prototype rows\n- changing empty, loading, connected, disconnected, or streaming states\n- preserving user overrides such as expansion and scroll position\n\nUse semantic HTML. Every icon-only button needs an accessible name. Every field\nneeds a label or accessible name. Keep the DOM state and visible state in sync.\n\n### 6. Add the archive entry\n\nAdd a concise label and prototype path to `interactivePrototypes` in\n`apps\u002Fstyleguide\u002Fsrc\u002FPrototypeArchive.tsx`. Keep the label specific enough to\ndistinguish revisions of the same feature.\n\nThe archive is a design history. Do not describe a prototype as current product\nbehavior or overwrite an older concept without an explicit reason.\n\n### 7. Serve and review it\n\nRun the styleguide from the repository root:\n\n```bash\npnpm styleguide\n```\n\nOpen the prototype through the server, never through a `file:\u002F\u002F` URL:\n\n```text\nhttp:\u002F\u002F127.0.0.1:5176\u002Fprototypes\u002F\u003Cconcept>.html\n```\n\nUse the `agent-browser` skill when browser automation is available. Check:\n\n1. The archive link opens the prototype.\n2. Every review interaction works from the served URL.\n3. Keyboard focus order and Escape behavior are correct.\n4. The design works at the user's screenshot size and at a smaller desktop\n   viewport.\n5. Popovers and menus stay within the viewport.\n6. Text does not clip at normal desktop zoom.\n7. An accessibility audit has no automatic violations. Manually inspect any\n   incomplete contrast results.\n\nCapture the default state and each decision-critical state when screenshots\nmake review easier. Keep those captures in the repository if they are part of\nthe requested deliverable.\n\n### 8. Validate\n\nRun:\n\n```bash\npnpm --filter @sero\u002Fstyleguide build\ngit diff --check\n```\n\nRun root `pnpm typecheck` before a commit, as required by `AGENTS.md`.\n\nDo not run React Doctor for a standalone HTML prototype. Run it when the\nprototype changes React code beyond the archive entry.\n\n## Quality gate\n\nDo not call the prototype ready until all answers are yes:\n\n- Does it answer the user's review question?\n- Does it look like the current Sero surface it must match?\n- Did you inspect and learn from the closest existing prototype?\n- Are unsupported controls absent?\n- Are the important interactions functional with mouse and keyboard?\n- Are default, empty, busy, failure, and confirmation states represented when\n  relevant?\n- Is it reachable from the styleguide archive?\n- Did you test the served URL at two desktop viewport sizes?\n- Did build, diff, and accessibility checks pass?\n\n## Delivery\n\nReport:\n\n- the repository path\n- the styleguide route\n- the states and interactions included\n- the source examples used for consistency\n- validation results\n- any product decision still needed\n\nDo not provide a temporary path as the primary deliverable. Do not implement the\nproduction feature until the user approves the direction.\n","# Creating Sero prototypes\n\nBuild a reviewable design artifact that matches the current Sero desktop UI.\nDo not treat a prototype as production implementation.\n\n## Non-negotiable rules\n\n- Store every deliverable under `apps\u002Fstyleguide\u002Fpublic\u002Fprototypes\u002F`.\n- Link every interactive prototype from\n  `apps\u002Fstyleguide\u002Fsrc\u002FPrototypeArchive.tsx`.\n- Never deliver a prototype from `\u002Ftmp`, a clipboard path, or another protected\n  directory.\n- Inspect the closest existing prototype before creating a new one. Reuse its\n  useful structure and interaction patterns, but verify them against the current\n  product source because archived prototypes can be outdated.\n- Do not edit production UI while the user is still reviewing the prototype.\n- Show only controls and behavior supported by the proposed design. Do not add\n  decorative controls that imply unsupported functionality.\n- Use ASD-STE100 Simplified Technical English for labels and explanatory copy.\n\n## Workflow\n\n### 1. Define the review question\n\nState what the prototype must help the user decide. Extract these items from\nthe request and screenshots:\n\n- target workflow and entry point\n- behavior that must match an existing Sero surface\n- supported and unsupported actions\n- key states the user must compare\n- unresolved product choices\n\nAsk focused questions before building only when different answers would change\nthe interaction model. If the user asked to discuss before implementation, stop\nafter the prototype and review notes.\n\n### 2. Inspect Sero before drawing\n\nRead the smallest relevant set of sources:\n\n1. The current production components for the feature and the Sero surface it\n   must match.\n2. `packages\u002Fui\u002Fsrc\u002Fstyles\u002Fglobals.css` for current tokens, typography, focus,\n   radii, and status colors.\n3. Related shared components under `packages\u002Fui\u002Fsrc\u002Fcomponents\u002F`.\n4. The closest prototype in `apps\u002Fstyleguide\u002Fpublic\u002Fprototypes\u002F`.\n5. `apps\u002Fstyleguide\u002Fsrc\u002FPrototypeArchive.tsx` to understand current names and\n   avoid duplicate entries.\n\nFor changes to an existing concept, inspect its saved prototype first. Create a\nnew descriptive prototype file unless the user explicitly asks to replace the\nhistorical artifact.\n\n### 3. Choose the artifact\n\nUse an interactive standalone HTML prototype by default. Name it with a short,\nlowercase kebab-case slug:\n\n```text\napps\u002Fstyleguide\u002Fpublic\u002Fprototypes\u002F\u003Cconcept>.html\n```\n\nUse `prototypes\u002F\u003Cconcept>\u002Findex.html` with adjacent CSS, JavaScript, or image\nassets when a single HTML file would become hard to review or exceed the\nrepository file-size rules. Do not depend on a CDN or remote runtime. The\nprototype must work through the styleguide Vite server without network access.\n\nUse static images only when interaction adds no review value. Put persistent\nreview captures in:\n\n```text\napps\u002Fstyleguide\u002Fpublic\u002Fprototypes\u002Fscreenshots\u002F\u003Cconcept>\u002F\n```\n\n### 4. Match the product\n\n- Copy semantic token names and current values from the Sero design system.\n  Do not invent a second palette.\n- Match the current desktop layout, density, spacing, border treatment,\n  typography, active states, and control placement.\n- Use standard Sero font sizes. In React or Tailwind prototypes, use utilities\n  such as `text-xs`, `text-sm`, and `text-base` instead of arbitrary sizes.\n- Use inline Lucide SVG geometry or repository-owned assets. Do not substitute\n  emoji or unrelated Unicode glyphs for product icons.\n- Use realistic, sanitized Sero data. Keep names and copy short.\n- Preserve the hierarchy and interaction language of the product surface being\n  matched. A different runtime or backend must not create a different visual\n  system without a product reason.\n- Use clear focus, hover, selected, disabled, loading, streaming, success, and\n  error states where they affect the proposed workflow.\n- Respect `prefers-reduced-motion`. Avoid animation that does not explain a\n  state change.\n\nIf the prototype explores alternatives, label each option and keep the data and\nviewport consistent so the user can compare the design rather than the content.\n\n### 5. Make the important behavior real\n\nImplement the interactions needed for review, not every product feature. Common\nexamples include:\n\n- opening and closing menus, popovers, and dialogs\n- search and filtering\n- keyboard focus, Enter, arrow keys when applicable, and Escape\n- adding, selecting, renaming, or deleting prototype rows\n- changing empty, loading, connected, disconnected, or streaming states\n- preserving user overrides such as expansion and scroll position\n\nUse semantic HTML. Every icon-only button needs an accessible name. Every field\nneeds a label or accessible name. Keep the DOM state and visible state in sync.\n\n### 6. Add the archive entry\n\nAdd a concise label and prototype path to `interactivePrototypes` in\n`apps\u002Fstyleguide\u002Fsrc\u002FPrototypeArchive.tsx`. Keep the label specific enough to\ndistinguish revisions of the same feature.\n\nThe archive is a design history. Do not describe a prototype as current product\nbehavior or overwrite an older concept without an explicit reason.\n\n### 7. Serve and review it\n\nRun the styleguide from the repository root:\n\n```bash\npnpm styleguide\n```\n\nOpen the prototype through the server, never through a `file:\u002F\u002F` URL:\n\n```text\nhttp:\u002F\u002F127.0.0.1:5176\u002Fprototypes\u002F\u003Cconcept>.html\n```\n\nUse the `agent-browser` skill when browser automation is available. Check:\n\n1. The archive link opens the prototype.\n2. Every review interaction works from the served URL.\n3. Keyboard focus order and Escape behavior are correct.\n4. The design works at the user's screenshot size and at a smaller desktop\n   viewport.\n5. Popovers and menus stay within the viewport.\n6. Text does not clip at normal desktop zoom.\n7. An accessibility audit has no automatic violations. Manually inspect any\n   incomplete contrast results.\n\nCapture the default state and each decision-critical state when screenshots\nmake review easier. Keep those captures in the repository if they are part of\nthe requested deliverable.\n\n### 8. Validate\n\nRun:\n\n```bash\npnpm --filter @sero\u002Fstyleguide build\ngit diff --check\n```\n\nRun root `pnpm typecheck` before a commit, as required by `AGENTS.md`.\n\nDo not run React Doctor for a standalone HTML prototype. Run it when the\nprototype changes React code beyond the archive entry.\n\n## Quality gate\n\nDo not call the prototype ready until all answers are yes:\n\n- Does it answer the user's review question?\n- Does it look like the current Sero surface it must match?\n- Did you inspect and learn from the closest existing prototype?\n- Are unsupported controls absent?\n- Are the important interactions functional with mouse and keyboard?\n- Are default, empty, busy, failure, and confirmation states represented when\n  relevant?\n- Is it reachable from the styleguide archive?\n- Did you test the served URL at two desktop viewport sizes?\n- Did build, diff, and accessibility checks pass?\n\n## Delivery\n\nReport:\n\n- the repository path\n- the styleguide route\n- the states and interactions included\n- the source examples used for consistency\n- validation results\n- any product decision still needed\n\nDo not provide a temporary path as the primary deliverable. Do not implement the\nproduction feature until the user approves the direction.\n",{"name":5,"description":7},"main","e91c3c773b84e88a929cae3c36977e892ca4871a",".agents\u002Fskills\u002Fsero-prototype",4,"https:\u002F\u002Fgithub.com\u002Fsero-labs\u002Fsero","https:\u002F\u002Fsero-ai.dev\u002F","https:\u002F\u002Fgithub.com\u002Fsero-labs","2026-11-10 06:55:21",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add sero-labs\u002Fsero --skill sero-prototype",{"tool":70,"command":71},"bunx","bunx skills add sero-labs\u002Fsero --skill sero-prototype",{"tool":73,"command":74},"pnpm","pnpm dlx skills add sero-labs\u002Fsero --skill sero-prototype","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsero-labs\u002Fsero\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsero-prototype\u002FSKILL.md",true,[78],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fbest_practices.md","REFERENCE","参考文档",7560,"https:\u002F\u002Fgithub.com\u002Ftbeack\u002Ffsad_playbook\u002Fblob\u002Fmain\u002Fskills\u002Fprompt-improver\u002Freferences\u002Fbest_practices.md",[85,119,147,184,209,236],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":99,"publishedAt":51},"01M70PSGDVAGMAGE2RFKEQ1EW4","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. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.","https:\u002F\u002Fgithub.com\u002Fsero-labs\u002Fsero\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fagent-browser\u002FSKILL.md",[91,96],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":97,"categoryName":98,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000023","Skill与智能体开发",[100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,87,117,118],"agent browser","browser","testing","browser automation","notion","qa","figma","actions","messages","open","web tools","app","click","bedrock","extracting","conversations","programmatic","slack messages","exploratory testing",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":133,"publishedAt":51},"01M6CHW2A115ZZDEFNXV2Z7A2Z","skill-creator","Guide for writing and improving Sero skills. Use when the user wants to create a new skill, rewrite an existing one, or turn a repeated piece of work into reusable procedural knowledge for the agent.","https:\u002F\u002Fgithub.com\u002Fsero-labs\u002Fsero\u002Fblob\u002Fmain\u002Fpackages\u002Ftemplates\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsero-labs\u002Fsero\u002Fblob\u002Fmain\u002Fpackages\u002Ftemplates\u002Fskills\u002Fskill-creator\u002FSKILL.md",[126,129,130],{"categoryNo":127,"categoryName":128,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":97,"categoryName":98,"taxonomyType":94,"taxonomyTypeDesc":95},{"categoryNo":131,"categoryName":132,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者",[134,135,136,49,137,43,138,139,39,140,141,142,143,144,145,26,146],"skill creator","creator","writing","knowledge","user","guide","reusable","new skill","rewrite","procedural","for","Existing","new",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":151,"sourceHtmlUrl":152,"categories":153,"keywords":161,"publishedAt":51},"01M6CHVJCZS9V3WWFPG47WC4G9","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002Fsero-labs\u002Fsero\u002Fblob\u002Fmain\u002Fpackages\u002Ftemplates\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsero-labs\u002Fsero\u002Fblob\u002Fmain\u002Fpackages\u002Ftemplates\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[154,157,160],{"categoryNo":155,"categoryName":156,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":158,"categoryName":159,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[162,38,163,164,165,166,167,168,169,49,170,171,47,172,173,174,175,176,39,177,178,179,180,181,182,183,26],"frontend","frontend design","css","web","components","react","react components","web components","code","artifacts","examples","applications","dashboards","quality","landing","html","styling","creative","ui design","build","aesthetics","generic",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":194,"publishedAt":51},"01M6CHTP6F4MENDBRDT7QQBKNY","sero-humanize","Use to draft, edit, or audit Sero application content, including UI copy,\ndocumentation, README text, and release notes. Use unslop for regular chat\nand status reports instead. Not for code review or creative and promotional\nwriting.","https:\u002F\u002Fgithub.com\u002Fsero-labs\u002Fsero\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsero-humanize\u002FSKILL.md",[190,193],{"categoryNo":191,"categoryName":192,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":131,"categoryName":132,"taxonomyType":20,"taxonomyTypeDesc":21},[195,196,197,136,50,198,199,200,201,170,202,203,47,204,205,206,207,39,179,208,144],"humanize","sero humanize","code review","status","documentation","notes","release notes","release","audit","unslop","text","README","edit","reports",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":216,"publishedAt":51},"01M6CHVXWDN98CP3MPT2WZ1ABN","sero-plugin","Create Sero plugins — self-contained packages with a Pi extension (agent\ntools\u002Fcommands), an optional React UI loaded via Module Federation, and an\noptional background runtime. Use when the user asks to create a Sero\nplugin\u002Fapp\u002Fextension, add a sidebar panel, dashboard widget, or\nagent-integrated feature, or convert a Pi extension into a Sero plugin.\nTrigger on phrases like \"create a plugin\", \"new Sero app\", \"add a tool\nwith UI\", \"build an extension\", \"convert this Pi extension\", or any\nrequest that touches `plugins\u002Fsero-*-plugin\u002F`.","https:\u002F\u002Fgithub.com\u002Fsero-labs\u002Fsero\u002Fblob\u002Fmain\u002Fpackages\u002Ftemplates\u002Fskills\u002Fsero-plugin\u002FSKILL.md",[215],{"categoryNo":97,"categoryName":98,"taxonomyType":94,"taxonomyTypeDesc":95},[217,218,219,167,220,49,221,47,222,223,224,225,226,138,227,39,181,228,229,230,231,232,111,233,234,235,26,146],"plugin","sero plugin","dashboard","packages","plugins","federation","Tools","react ui","tool","convert","pi","self","commands","runtime","pi extension","feature","add","panel","request",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":249,"publishedAt":51},"01M6CHVTJ5Y9JE6181SVPQXNZY","sero-dashboard-ui","Build, redesign or standardise Sero dashboard widgets and compact plugin\nviews using the shared @sero-ai\u002Fui dashboard components. Use when the user\nasks to create, restyle, clean up or make consistent a dashboard widget or a\ndata-dense plugin view. Trigger on phrases like \"dashboard widget\", \"widget\nfor the dashboard\", \"restyle this widget\", \"make the widget consistent\",\n\"compact plugin view\", or any work under a plugin's `ui\u002Fwidgets\u002F`.","https:\u002F\u002Fgithub.com\u002Fsero-labs\u002Fsero\u002Fblob\u002Fmain\u002Fpackages\u002Ftemplates\u002Fskills\u002Fsero-dashboard-ui\u002FSKILL.md",[242,245,246],{"categoryNo":243,"categoryName":244,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":247,"categoryName":248,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000033","数据分析师",[219,47,250,166,217,49,251,43,252,253,138,39,254,255,181,256,257,258,259,29,144,26],"sero dashboard ui","data","redesign","view","up","clean","compact","shared","widgets","trigger"]