[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71EK2GC2KW34483BN59NGD2":3,"skill-same:01M71EK2GC2KW34483BN59NGD2":78},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M71EK2GC2KW34483BN59NGD2","browserbase-cli",null,"Use the Browserbase CLI (`bb`) for Browserbase Functions and platform API workflows. Use when the user asks to run `bb`, deploy or invoke functions, manage sessions, projects, contexts, or extensions, fetch a page through the Browserbase Fetch API, search the web through the Browserbase Search API, or scaffold starter templates. Prefer the Browser skill for interactive browsing; use `bb browse` only when the user explicitly wants the Browserbase CLI path.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_browserbase_browserbase_cli\u002Fskill.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"browserbase","browserbase cli","cli","install","commands","run","browser","publish","api","Bash","browsing","when","workflows","invoke","only","browserbase functions","search","project","fetch","projects","2026-11-10 10:12:30",false,"---\nname: browserbase-cli\ndescription: Use the Browserbase CLI (`bb`) for Browserbase Functions and platform API workflows. Use when the user asks to run `bb`, deploy or invoke functions, manage sessions, projects, contexts, or extensions, fetch a page through the Browserbase Fetch API, search the web through the Browserbase Search API, or scaffold starter templates. Prefer the Browser skill for interactive browsing; use `bb browse` only when the user explicitly wants the Browserbase CLI path.\ncompatibility: \"Requires the Browserbase CLI (`npm install -g @browserbasehq\u002Fcli`). API commands require `BROWSERBASE_API_KEY`. `BROWSERBASE_PROJECT_ID` is only needed for `bb functions dev` and `bb functions publish`. `bb browse` additionally requires `npm install -g @browserbasehq\u002Fbrowse-cli`.\"\nlicense: MIT\nallowed-tools: Bash\n---\n\n# Browserbase CLI\n\nUse the official `bb` CLI for Browserbase platform operations, Functions workflows, and Fetch API calls.\n\n## Setup check\n\nBefore using the CLI, verify it is installed:\n\n```bash\nwhich bb || npm install -g @browserbasehq\u002Fcli\nbb --help\n```\n\nFor authenticated commands, set the API key:\n\n```bash\nexport BROWSERBASE_API_KEY=\"your_api_key\"\n```\n\nIf using `bb functions dev` or `bb functions publish`, also set:\n\n```bash\nexport BROWSERBASE_PROJECT_ID=\"your_project_id\"\n```\n\n## When to use this skill\n\nUse this skill when the user wants to:\n\n- run Browserbase commands through `bb`\n- scaffold, develop, publish, or invoke Browserbase Functions\n- inspect or manage Browserbase sessions, projects, contexts, or extensions\n- fetch a page through Browserbase without opening a browser session\n- search the web through Browserbase without opening a browser session\n- browse or scaffold starter templates with `bb templates`\n\n## When not to use this skill\n\n- For interactive browsing, page inspection, screenshots, clicking, typing, or login flows, prefer the `browser` skill.\n- For simple HTTP content retrieval where the user does not care about using the CLI specifically, the dedicated `fetch` skill is often a better fit.\n- Use `bb browse ...` only when the user explicitly wants the CLI wrapper or is already working in a `bb`-centric workflow.\n\n## Command selection\n\n- `bb functions` for local dev, packaging, publishing, and invocation\n- `bb sessions`, `bb projects`, `bb contexts`, `bb extensions` for Browserbase platform resources\n- `bb fetch \u003Curl>` for Fetch API requests\n- `bb search \"\u003Cquery>\"` for Search API requests\n- `bb templates` to browse and scaffold starter templates\n- `bb browse ...` to forward to the standalone `browse` binary (requires `@browserbasehq\u002Fbrowse-cli`)\n- `bb skills install` to install Browserbase agent skills for Claude Code\n\nFor `bb browse`, the standalone `browse` CLI behavior is the source of truth: `bb browse env local` uses a clean isolated local browser by default, and `bb browse env local --auto-connect` opts into reusing an existing local Chrome session.\n\n## Common workflows\n\n### Functions\n\n```bash\nbb functions init my-function\ncd my-function\nbb functions dev index.ts\nbb functions publish index.ts\nbb functions invoke \u003Cfunction_id> --params '{\"url\":\"https:\u002F\u002Fexample.com\"}'\n```\n\nUse `bb functions invoke --check-status \u003Cinvocation_id>` to poll an existing invocation instead of creating a new one.\n\n### Platform APIs\n\n```bash\nbb projects list\nbb sessions create --proxies --advanced-stealth --region us-east-1\nbb sessions create --solve-captchas --context-id ctx_abc --persist\nbb sessions get \u003Csession_id>\nbb sessions downloads get \u003Csession_id> --output session-artifacts.zip\nbb contexts create --body '{\"region\":\"us-west-2\"}'\nbb extensions upload .\u002Fmy-extension.zip\n```\n\n### Fetch API\n\n```bash\nbb fetch https:\u002F\u002Fexample.com\nbb fetch https:\u002F\u002Fexample.com --allow-redirects --output page.html\n```\n\n### Search API\n\n```bash\nbb search \"browser automation\"\nbb search \"web scraping\" --num-results 5\nbb search \"AI agents\" --output results.json\n```\n\n### Templates\n\n```bash\nbb templates list\nbb templates list --language python\nbb templates clone form-filling --language typescript\nbb templates clone amazon-product-scraping --language python .\u002Fmy-scraper\n```\n\n## Best practices\n\n1. Prefer `bb --help` and subgroup `--help` before guessing flags.\n2. Use dash-case flags exactly as shown in CLI help.\n3. Use `--output \u003Cfile>` on `bb fetch` and `bb search` to save results to a file.\n4. Use environment variables for auth unless the user explicitly wants one-off overrides.\n5. Pass structured request bodies with JSON strings in `--body` or `--params`.\n6. Remember that `bb functions ...` uses `--api-url`, while platform API commands use `--base-url`.\n7. If `bb browse` fails because `browse` is missing, either install `@browserbasehq\u002Fbrowse-cli` or switch to the `browser` skill.\n\n## Troubleshooting\n\n- Missing API key: set `BROWSERBASE_API_KEY` or pass `--api-key`\n- Missing project ID on `bb functions dev` or `bb functions publish`: set `BROWSERBASE_PROJECT_ID` or pass `--project-id`\n- Unknown flag: rerun the relevant command with `--help` and use the exact dash-case form\n- `bb browse` install error: run `npm install -g @browserbasehq\u002Fbrowse-cli`\n\nFor command-by-command reference and more examples, see REFERENCE.md (`REFERENCE.md`).\n","# Browserbase CLI\n\nUse the official `bb` CLI for Browserbase platform operations, Functions workflows, and Fetch API calls.\n\n## Setup check\n\nBefore using the CLI, verify it is installed:\n\n```bash\nwhich bb || npm install -g @browserbasehq\u002Fcli\nbb --help\n```\n\nFor authenticated commands, set the API key:\n\n```bash\nexport BROWSERBASE_API_KEY=\"your_api_key\"\n```\n\nIf using `bb functions dev` or `bb functions publish`, also set:\n\n```bash\nexport BROWSERBASE_PROJECT_ID=\"your_project_id\"\n```\n\n## When to use this skill\n\nUse this skill when the user wants to:\n\n- run Browserbase commands through `bb`\n- scaffold, develop, publish, or invoke Browserbase Functions\n- inspect or manage Browserbase sessions, projects, contexts, or extensions\n- fetch a page through Browserbase without opening a browser session\n- search the web through Browserbase without opening a browser session\n- browse or scaffold starter templates with `bb templates`\n\n## When not to use this skill\n\n- For interactive browsing, page inspection, screenshots, clicking, typing, or login flows, prefer the `browser` skill.\n- For simple HTTP content retrieval where the user does not care about using the CLI specifically, the dedicated `fetch` skill is often a better fit.\n- Use `bb browse ...` only when the user explicitly wants the CLI wrapper or is already working in a `bb`-centric workflow.\n\n## Command selection\n\n- `bb functions` for local dev, packaging, publishing, and invocation\n- `bb sessions`, `bb projects`, `bb contexts`, `bb extensions` for Browserbase platform resources\n- `bb fetch \u003Curl>` for Fetch API requests\n- `bb search \"\u003Cquery>\"` for Search API requests\n- `bb templates` to browse and scaffold starter templates\n- `bb browse ...` to forward to the standalone `browse` binary (requires `@browserbasehq\u002Fbrowse-cli`)\n- `bb skills install` to install Browserbase agent skills for Claude Code\n\nFor `bb browse`, the standalone `browse` CLI behavior is the source of truth: `bb browse env local` uses a clean isolated local browser by default, and `bb browse env local --auto-connect` opts into reusing an existing local Chrome session.\n\n## Common workflows\n\n### Functions\n\n```bash\nbb functions init my-function\ncd my-function\nbb functions dev index.ts\nbb functions publish index.ts\nbb functions invoke \u003Cfunction_id> --params '{\"url\":\"https:\u002F\u002Fexample.com\"}'\n```\n\nUse `bb functions invoke --check-status \u003Cinvocation_id>` to poll an existing invocation instead of creating a new one.\n\n### Platform APIs\n\n```bash\nbb projects list\nbb sessions create --proxies --advanced-stealth --region us-east-1\nbb sessions create --solve-captchas --context-id ctx_abc --persist\nbb sessions get \u003Csession_id>\nbb sessions downloads get \u003Csession_id> --output session-artifacts.zip\nbb contexts create --body '{\"region\":\"us-west-2\"}'\nbb extensions upload .\u002Fmy-extension.zip\n```\n\n### Fetch API\n\n```bash\nbb fetch https:\u002F\u002Fexample.com\nbb fetch https:\u002F\u002Fexample.com --allow-redirects --output page.html\n```\n\n### Search API\n\n```bash\nbb search \"browser automation\"\nbb search \"web scraping\" --num-results 5\nbb search \"AI agents\" --output results.json\n```\n\n### Templates\n\n```bash\nbb templates list\nbb templates list --language python\nbb templates clone form-filling --language typescript\nbb templates clone amazon-product-scraping --language python .\u002Fmy-scraper\n```\n\n## Best practices\n\n1. Prefer `bb --help` and subgroup `--help` before guessing flags.\n2. Use dash-case flags exactly as shown in CLI help.\n3. Use `--output \u003Cfile>` on `bb fetch` and `bb search` to save results to a file.\n4. Use environment variables for auth unless the user explicitly wants one-off overrides.\n5. Pass structured request bodies with JSON strings in `--body` or `--params`.\n6. Remember that `bb functions ...` uses `--api-url`, while platform API commands use `--base-url`.\n7. If `bb browse` fails because `browse` is missing, either install `@browserbasehq\u002Fbrowse-cli` or switch to the `browser` skill.\n\n## Troubleshooting\n\n- Missing API key: set `BROWSERBASE_API_KEY` or pass `--api-key`\n- Missing project ID on `bb functions dev` or `bb functions publish`: set `BROWSERBASE_PROJECT_ID` or pass `--project-id`\n- Unknown flag: rerun the relevant command with `--help` and use the exact dash-case form\n- `bb browse` install error: run `npm install -g @browserbasehq\u002Fbrowse-cli`\n\nFor command-by-command reference and more examples, see REFERENCE.md (`REFERENCE.md`).\n",{"name":5,"license":15,"description":7,"allowed-tools":38,"compatibility":54},"Requires the Browserbase CLI (`npm install -g @browserbasehq\u002Fcli`). API commands require `BROWSERBASE_API_KEY`. `BROWSERBASE_PROJECT_ID` is only needed for `bb functions dev` and `bb functions publish`. `bb browse` additionally requires `npm install -g @browserbasehq\u002Fbrowse-cli`.","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_browserbase_browserbase_cli",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill browserbase-cli",{"tool":70,"command":71},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill browserbase-cli",{"tool":73,"command":74},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill browserbase-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_browserbase_browserbase_cli\u002Fskill.md",true,[],[79,108,131,153,173,194],{"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":88,"publishedAt":107},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[89,90,91,92,93,94,95,96,97,98,99,100,101,102,40,103,37,104,105,106],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","route","create","libraries","2026-11-10 13:02:02",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":107},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[114],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[89,116,117,93,118,119,120,121,102,122,40,123,103,124,125,126,127,128,129,130],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":107},"01M71P8QK4JF5BYRGYDDGPZQG9","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[137],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[89,139,140,93,141,121,142,40,143,123,103,144,145,146,147,148,149,150,151,152],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":107},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[159],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[161,93,162,149,163,164,165,166,152,167,168,169,40,170,123,103,171,172,37,89],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":180,"publishedAt":107},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[179],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[181,182,183,184,141,185,186,187,130,150,121,188,189,142,190,169,191,192,193,40],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"publishedAt":217},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[200],{"categoryNo":86,"categoryName":87,"taxonomyType":21,"taxonomyTypeDesc":22},[202,203,204,205,206,99,207,166,208,102,209,210,40,89,211,212,213,214,215,216],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]