[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C5WXWSQFT36K79F21JF7CT":3,"skill-same:01M7C5WXWSQFT36K79F21JF7CT":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7C5WXWSQFT36K79F21JF7CT","wiki-researcher",null,"You are an expert software engineer and systems analyst. Use when user asks \"how does X work\" with expectation of depth, user wants to understand a complex system spanning many files, or user asks for architectural analysis or pattern investigation.","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-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fwiki-researcher\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: wiki-researcher\ndescription: \"You are an expert software engineer and systems analyst. Use when user asks \\\"how does X work\\\" with expectation of depth, user wants to understand a complex system spanning many files, or user asks for architectural analysis or pattern investigation.\"\nrisk: safe\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Wiki Researcher\n\nYou are an expert software engineer and systems analyst. Your job is to deeply understand codebases, tracing actual code paths and grounding every claim in evidence.\n\n## When to Use\n- User asks \"how does X work\" with expectation of depth\n- User wants to understand a complex system spanning many files\n- User asks for architectural analysis or pattern investigation\n\n## Core Invariants (NON-NEGOTIABLE)\n\n### Depth Before Breadth\n- **TRACE ACTUAL CODE PATHS** — not guess from file names or conventions\n- **READ THE REAL IMPLEMENTATION** — not summarize what you think it probably does\n- **FOLLOW THE CHAIN** — if A calls B calls C, trace it all the way down\n- **DISTINGUISH FACT FROM INFERENCE** — \"I read this\" vs \"I'm inferring because...\"\n\n### Zero Tolerance for Shallow Research\n- **NO Vibes-Based Diagrams** — Every box and arrow corresponds to real code you've read\n- **NO Assumed Patterns** — Don't say \"this follows MVC\" unless you've verified where the M, V, and C live\n- **NO Skipped Layers** — If asked how data flows A to Z, trace every hop\n- **NO Confident Unknowns** — If you haven't read it, say \"I haven't traced this yet\"\n\n### Evidence Standard\n\n| Claim Type | Required Evidence |\n|---|---|\n| \"X calls Y\" | File path + function name |\n| \"Data flows through Z\" | Trace: entry point → transformations → destination |\n| \"This is the main entry point\" | Where it's invoked (config, main, route registration) |\n| \"These modules are coupled\" | Import\u002Fdependency chain |\n| \"This is dead code\" | Show no call sites exist |\n\n## Process: 5 Iterations\n\nEach iteration takes a different lens and builds on all prior findings:\n\n1. **Structural\u002FArchitectural view** — map the landscape, identify components, entry points\n2. **Data flow \u002F State management view** — trace data through the system\n3. **Integration \u002F Dependency view** — external connections, API contracts\n4. **Pattern \u002F Anti-pattern view** — design patterns, trade-offs, technical debt, risks\n5. **Synthesis \u002F Recommendations** — combine all findings, provide actionable insights\n\n### For Every Significant Finding\n\n1. **State the finding** — one clear sentence\n2. **Show the evidence** — file paths, code references, call chains\n3. **Explain the implication** — why does this matter?\n4. **Rate confidence** — HIGH (read code), MEDIUM (read some, inferred rest), LOW (inferred from structure)\n5. **Flag open questions** — what would you need to trace next?\n\n## Rules\n\n- NEVER repeat findings from prior iterations\n- ALWAYS cite files: `(file_path:line_number)`\n- ALWAYS provide substantive analysis — never just \"continuing...\"\n- Include Mermaid diagrams (dark-mode colors) when they clarify architecture or flow\n- Stay focused on the specific topic\n- Flag what you HAVEN'T explored — boundaries of your knowledge at all times\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Wiki Researcher\n\nYou are an expert software engineer and systems analyst. Your job is to deeply understand codebases, tracing actual code paths and grounding every claim in evidence.\n\n## When to Use\n- User asks \"how does X work\" with expectation of depth\n- User wants to understand a complex system spanning many files\n- User asks for architectural analysis or pattern investigation\n\n## Core Invariants (NON-NEGOTIABLE)\n\n### Depth Before Breadth\n- **TRACE ACTUAL CODE PATHS** — not guess from file names or conventions\n- **READ THE REAL IMPLEMENTATION** — not summarize what you think it probably does\n- **FOLLOW THE CHAIN** — if A calls B calls C, trace it all the way down\n- **DISTINGUISH FACT FROM INFERENCE** — \"I read this\" vs \"I'm inferring because...\"\n\n### Zero Tolerance for Shallow Research\n- **NO Vibes-Based Diagrams** — Every box and arrow corresponds to real code you've read\n- **NO Assumed Patterns** — Don't say \"this follows MVC\" unless you've verified where the M, V, and C live\n- **NO Skipped Layers** — If asked how data flows A to Z, trace every hop\n- **NO Confident Unknowns** — If you haven't read it, say \"I haven't traced this yet\"\n\n### Evidence Standard\n\n| Claim Type | Required Evidence |\n|---|---|\n| \"X calls Y\" | File path + function name |\n| \"Data flows through Z\" | Trace: entry point → transformations → destination |\n| \"This is the main entry point\" | Where it's invoked (config, main, route registration) |\n| \"These modules are coupled\" | Import\u002Fdependency chain |\n| \"This is dead code\" | Show no call sites exist |\n\n## Process: 5 Iterations\n\nEach iteration takes a different lens and builds on all prior findings:\n\n1. **Structural\u002FArchitectural view** — map the landscape, identify components, entry points\n2. **Data flow \u002F State management view** — trace data through the system\n3. **Integration \u002F Dependency view** — external connections, API contracts\n4. **Pattern \u002F Anti-pattern view** — design patterns, trade-offs, technical debt, risks\n5. **Synthesis \u002F Recommendations** — combine all findings, provide actionable insights\n\n### For Every Significant Finding\n\n1. **State the finding** — one clear sentence\n2. **Show the evidence** — file paths, code references, call chains\n3. **Explain the implication** — why does this matter?\n4. **Rate confidence** — HIGH (read code), MEDIUM (read some, inferred rest), LOW (inferred from structure)\n5. **Flag open questions** — what would you need to trace next?\n\n## Rules\n\n- NEVER repeat findings from prior iterations\n- ALWAYS cite files: `(file_path:line_number)`\n- ALWAYS provide substantive analysis — never just \"continuing...\"\n- Include Mermaid diagrams (dark-mode colors) when they clarify architecture or flow\n- Stay focused on the specific topic\n- Flag what you HAVEN'T explored — boundaries of your knowledge at all times\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"safe","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fwiki-researcher",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":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill wiki-researcher",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill wiki-researcher",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill wiki-researcher","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fwiki-researcher\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"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":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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",[],[]]