[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72AQQ99RTSTN7DCYNM690RB":3,"skill-same:01M72AQQ99RTSTN7DCYNM690RB":45},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M72AQQ99RTSTN7DCYNM690RB","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.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fvexor-cli\u002FSKILL.md",[],[],"2026-11-10 18:39:20",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":23,"source":24,"description":7},"unknown","community","main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fantigravity\u002Fvexor-cli","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Sansar35\u002Fclaude-agent --skill vexor-cli",{"tool":37,"command":38},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill vexor-cli",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill vexor-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fvexor-cli\u002FSKILL.md",true,[],[46,53,60,67,74,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]