[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CPEWBW305E0E1HT40FVMVG":3,"skill-same:01M7CPEWBW305E0E1HT40FVMVG":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CPEWBW305E0E1HT40FVMVG","vexor-cli",null,"Semantic file discovery via `vexor`. Use whenever locating where something is implemented\u002Floaded\u002Fdefined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing.","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\u002Fskills\u002Fvexor-cli\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vexor-cli\ndescription: Semantic file discovery via `vexor`. Use whenever locating where something is implemented\u002Floaded\u002Fdefined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing.\nrisk: unknown\nsource: community\n---\n\n# Vexor CLI Skill\n\n## When to Use\n- You need to locate files by intent rather than exact filename or text match.\n- The repository is large enough that manual browsing or naive grep is too slow or ambiguous.\n- You want semantic discovery of where something is implemented, loaded, defined, or documented.\n\n## Goal\n\nFind files by intent (what they do), not exact text.\n\n## Use It Like This\n\n- Use `vexor` first for intent-based file discovery.\n- If `vexor` is missing, follow references\u002Finstall-vexor.md.\n\n## Command\n\n```bash\nvexor \"\u003CQUERY>\" [--path \u003CROOT>] [--mode \u003CMODE>] [--ext .py,.md] [--exclude-pattern \u003CPATTERN>] [--top 5] [--format rich|porcelain|porcelain-z]\n```\n\n## Common Flags\n\n- `--path\u002F-p`: root directory (default: current dir)\n- `--mode\u002F-m`: indexing\u002Fsearch strategy\n- `--ext\u002F-e`: limit file extensions (e.g., `.py,.md`)\n- `--exclude-pattern`: exclude paths by gitignore-style pattern (repeatable; `.js` → `**\u002F*.js`)\n- `--top\u002F-k`: number of results\n- `--include-hidden`: include dotfiles\n- `--no-respect-gitignore`: include ignored files\n- `--no-recursive`: only the top directory\n- `--format`: `rich` (default) or `porcelain`\u002F`porcelain-z` for scripts\n- `--no-cache`: in-memory only, do not read\u002Fwrite index cache\n\n## Modes (pick the cheapest that works)\n\n- `auto`: routes by file type (default)\n- `name`: filename-only (fastest)\n- `head`: first lines only (fast)\n- `brief`: keyword summary (good for PRDs)\n- `code`: code-aware chunking for `.py\u002F.js\u002F.ts` (best default for codebases)\n- `outline`: Markdown headings\u002Fsections (best for docs)\n- `full`: chunk full file contents (slowest, highest recall)\n\n## Troubleshooting\n\n- Need ignored or hidden files: add `--include-hidden` and\u002For `--no-respect-gitignore`.\n- Scriptable output: use `--format porcelain` (TSV) or `--format porcelain-z` (NUL-delimited).\n- Get detailed help: `vexor search --help`.\n- Config issues: `vexor doctor` or `vexor config --show` diagnoses API, cache, and connectivity (tell the user to set up).\n\n## Examples\n\n```bash\n# Find CLI entrypoints \u002F commands\nvexor search \"typer app commands\" --top 5\n```\n\n```bash\n# Search docs by headings\u002Fsections\nvexor search \"user authentication flow\" --path docs --mode outline --ext .md --format porcelain\n```\n\n```bash\n# Locate config loading\u002Fvalidation logic\nvexor search \"config loader\" --path . --mode code --ext .py\n```\n\n```bash\n# Exclude tests and JavaScript files\nvexor search \"config loader\" --path . --exclude-pattern tests\u002F** --exclude-pattern .js\n```\n\n## Tips\n\n- First time search will index files (may take a minute). Subsequent searches are fast. Use longer timeouts if needed.\n- Results return similarity ranking, exact file location, line numbers, and matching snippet preview.\n- Combine `--ext` with `--exclude-pattern` to focus on a subset (exclude rules apply on top).\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","# Vexor CLI Skill\n\n## When to Use\n- You need to locate files by intent rather than exact filename or text match.\n- The repository is large enough that manual browsing or naive grep is too slow or ambiguous.\n- You want semantic discovery of where something is implemented, loaded, defined, or documented.\n\n## Goal\n\nFind files by intent (what they do), not exact text.\n\n## Use It Like This\n\n- Use `vexor` first for intent-based file discovery.\n- If `vexor` is missing, follow references\u002Finstall-vexor.md.\n\n## Command\n\n```bash\nvexor \"\u003CQUERY>\" [--path \u003CROOT>] [--mode \u003CMODE>] [--ext .py,.md] [--exclude-pattern \u003CPATTERN>] [--top 5] [--format rich|porcelain|porcelain-z]\n```\n\n## Common Flags\n\n- `--path\u002F-p`: root directory (default: current dir)\n- `--mode\u002F-m`: indexing\u002Fsearch strategy\n- `--ext\u002F-e`: limit file extensions (e.g., `.py,.md`)\n- `--exclude-pattern`: exclude paths by gitignore-style pattern (repeatable; `.js` → `**\u002F*.js`)\n- `--top\u002F-k`: number of results\n- `--include-hidden`: include dotfiles\n- `--no-respect-gitignore`: include ignored files\n- `--no-recursive`: only the top directory\n- `--format`: `rich` (default) or `porcelain`\u002F`porcelain-z` for scripts\n- `--no-cache`: in-memory only, do not read\u002Fwrite index cache\n\n## Modes (pick the cheapest that works)\n\n- `auto`: routes by file type (default)\n- `name`: filename-only (fastest)\n- `head`: first lines only (fast)\n- `brief`: keyword summary (good for PRDs)\n- `code`: code-aware chunking for `.py\u002F.js\u002F.ts` (best default for codebases)\n- `outline`: Markdown headings\u002Fsections (best for docs)\n- `full`: chunk full file contents (slowest, highest recall)\n\n## Troubleshooting\n\n- Need ignored or hidden files: add `--include-hidden` and\u002For `--no-respect-gitignore`.\n- Scriptable output: use `--format porcelain` (TSV) or `--format porcelain-z` (NUL-delimited).\n- Get detailed help: `vexor search --help`.\n- Config issues: `vexor doctor` or `vexor config --show` diagnoses API, cache, and connectivity (tell the user to set up).\n\n## Examples\n\n```bash\n# Find CLI entrypoints \u002F commands\nvexor search \"typer app commands\" --top 5\n```\n\n```bash\n# Search docs by headings\u002Fsections\nvexor search \"user authentication flow\" --path docs --mode outline --ext .md --format porcelain\n```\n\n```bash\n# Locate config loading\u002Fvalidation logic\nvexor search \"config loader\" --path . --mode code --ext .py\n```\n\n```bash\n# Exclude tests and JavaScript files\nvexor search \"config loader\" --path . --exclude-pattern tests\u002F** --exclude-pattern .js\n```\n\n## Tips\n\n- First time search will index files (may take a minute). Subsequent searches are fast. Use longer timeouts if needed.\n- Results return similarity ranking, exact file location, line numbers, and matching snippet preview.\n- Combine `--ext` with `--exclude-pattern` to focus on a subset (exclude rules apply on top).\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,"description":7},"unknown","community","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fvexor-cli",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill vexor-cli",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill vexor-cli",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill vexor-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fvexor-cli\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"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":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":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":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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]