[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77M47RXTJ2M3V0GF81GMCFE":3,"skill-same:01M77M47RXTJ2M3V0GF81GMCFE":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77M47RXTJ2M3V0GF81GMCFE","copilot-spaces",null,"Use Copilot Spaces to provide project-specific context to conversations. Use this skill when users mention a \"Copilot space\", want to load context from a shared knowledge base, discover available spaces, or ask questions grounded in curated project documentation, code, and instructions.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcopilot-spaces\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: copilot-spaces\ndescription: 'Use Copilot Spaces to provide project-specific context to conversations. Use this skill when users mention a \"Copilot space\", want to load context from a shared knowledge base, discover available spaces, or ask questions grounded in curated project documentation, code, and instructions.'\n---\n\n# Copilot Spaces\n\nUse Copilot Spaces to bring curated, project-specific context into conversations. A Space is a shared collection of repositories, files, documentation, and instructions that grounds Copilot responses in your team's actual code and knowledge.\n\n## Available Tools\n\n### MCP Tools (Read-only)\n\n| Tool | Purpose |\n|------|---------|\n| `mcp__github__list_copilot_spaces` | List all spaces accessible to the current user |\n| `mcp__github__get_copilot_space` | Load a space's full context by owner and name |\n\n### REST API via `gh api` (Full CRUD)\n\nThe Spaces REST API supports creating, updating, deleting spaces, and managing collaborators. The MCP server only exposes read operations, so use `gh api` for writes.\n\n**User Spaces:**\n\n| Method | Endpoint | Purpose |\n|--------|----------|---------|\n| `POST` | `\u002Fusers\u002F{username}\u002Fcopilot-spaces` | Create a space |\n| `GET` | `\u002Fusers\u002F{username}\u002Fcopilot-spaces` | List spaces |\n| `GET` | `\u002Fusers\u002F{username}\u002Fcopilot-spaces\u002F{number}` | Get a space |\n| `PUT` | `\u002Fusers\u002F{username}\u002Fcopilot-spaces\u002F{number}` | Update a space |\n| `DELETE` | `\u002Fusers\u002F{username}\u002Fcopilot-spaces\u002F{number}` | Delete a space |\n\n**Organization Spaces:** Same pattern under `\u002Forgs\u002F{org}\u002Fcopilot-spaces\u002F...`\n\n**Collaborators:** Add, list, update, and remove collaborators at `...\u002Fcollaborators`\n\n**Scope requirements:** PAT needs `read:user` for reads, `user` for writes. Add with `gh auth refresh -h github.com -s user`.\n\n**Note:** This API is functional but not yet in the public REST API docs. It may require the `copilot_spaces_api` feature flag.\n\n## When to Use Spaces\n\n- User mentions \"Copilot space\" or asks to \"load a space\"\n- User wants answers grounded in specific project docs, code, or standards\n- User asks \"what spaces are available?\" or \"find a space for X\"\n- User needs onboarding context, architecture docs, or team-specific guidance\n- User wants to follow a structured workflow defined in a Space (templates, checklists, multi-step processes)\n\n## Workflow\n\n### 1. Discover Spaces\n\nWhen a user asks what spaces are available or you need to find the right space:\n\n```\nCall mcp__github__list_copilot_spaces\n```\n\nThis returns all spaces the user can access, each with a `name` and `owner_login`. Present relevant matches to the user.\n\nTo filter for a specific user's spaces, match `owner_login` against the username (e.g., \"show me my spaces\").\n\n### 2. Load a Space\n\nWhen a user names a specific space or you've identified the right one:\n\n```\nCall mcp__github__get_copilot_space with:\n  owner: \"org-or-user\"    (the owner_login from the list)\n  name: \"Space Name\"      (exact space name, case-sensitive)\n```\n\nThis returns the space's full content: attached documentation, code context, custom instructions, and any other curated materials. Use this context to inform your responses.\n\n### 3. Follow the Breadcrumbs\n\nSpace content often references external resources: GitHub issues, dashboards, repos, discussions, or other tools. Proactively fetch these using other MCP tools to gather complete context. For example:\n- A space references an initiative tracking issue. Use `issue_read` to get the latest comments.\n- A space links to a project board. Use project tools to check current status.\n- A space mentions a repo's masterplan. Use `get_file_contents` to read it.\n\n### 4. Answer or Execute\n\nOnce loaded, use the space content based on what it contains:\n\n**If the space contains reference material** (docs, code, standards):\n- Answer questions about the project's architecture, patterns, or standards\n- Generate code that follows the team's conventions\n- Debug issues using project-specific knowledge\n\n**If the space contains workflow instructions** (templates, step-by-step processes):\n- Follow the workflow as defined, step by step\n- Gather data from the sources the workflow specifies\n- Produce output in the format the workflow defines\n- Show progress after each step so the user can steer\n\n### 5. Manage Spaces (via `gh api`)\n\nWhen a user wants to create, update, or delete a space, use `gh api`. First, find the space number from the list endpoint.\n\n**Update a space's instructions:**\n```bash\ngh api users\u002F{username}\u002Fcopilot-spaces\u002F{number} \\\n  -X PUT \\\n  -f general_instructions=\"New instructions here\"\n```\n\n**Update name, description, or instructions together:**\n```bash\ngh api users\u002F{username}\u002Fcopilot-spaces\u002F{number} \\\n  -X PUT \\\n  -f name=\"Updated Name\" \\\n  -f description=\"Updated description\" \\\n  -f general_instructions=\"Updated instructions\"\n```\n\n**Create a new space:**\n```bash\ngh api users\u002F{username}\u002Fcopilot-spaces \\\n  -X POST \\\n  -f name=\"My New Space\" \\\n  -f general_instructions=\"Help me with...\" \\\n  -f visibility=\"private\"\n```\n\n**Attach resources (replaces entire resource list):**\n```json\n{\n  \"resources_attributes\": [\n    { \"resource_type\": \"free_text\", \"metadata\": { \"name\": \"Notes\", \"text\": \"Content here\" } },\n    { \"resource_type\": \"github_issue\", \"metadata\": { \"repository_id\": 12345, \"number\": 42 } },\n    { \"resource_type\": \"github_file\", \"metadata\": { \"repository_id\": 12345, \"file_path\": \"docs\u002Fguide.md\" } }\n  ]\n}\n```\n\n**Delete a space:**\n```bash\ngh api users\u002F{username}\u002Fcopilot-spaces\u002F{number} -X DELETE\n```\n\n**Updatable fields:** `name`, `description`, `general_instructions`, `icon_type`, `icon_color`, `visibility` (\"private\"\u002F\"public\"), `base_role` (\"no_access\"\u002F\"reader\"), `resources_attributes`\n\n## Examples\n\n### Example 1: User Asks for a Space\n\n**User**: \"Load the Accessibility copilot space\"\n\n**Action**:\n1. Call `mcp__github__get_copilot_space` with owner `\"github\"`, name `\"Accessibility\"`\n2. Use the returned context to answer questions about accessibility standards, MAS grades, compliance processes, etc.\n\n### Example 2: User Wants to Find Spaces\n\n**User**: \"What copilot spaces are available for our team?\"\n\n**Action**:\n1. Call `mcp__github__list_copilot_spaces`\n2. Filter\u002Fpresent spaces relevant to the user's org or interests\n3. Offer to load any space they're interested in\n\n### Example 3: Context-Grounded Question\n\n**User**: \"Using the security space, what's our policy on secret scanning?\"\n\n**Action**:\n1. Call `mcp__github__get_copilot_space` with the appropriate owner and name\n2. Find the relevant policy in the space content\n3. Answer based on the actual internal documentation\n\n### Example 4: Space as a Workflow Engine\n\n**User**: \"Write my weekly update using the PM Weekly Updates space\"\n\n**Action**:\n1. Call `mcp__github__get_copilot_space` to load the space. It contains a template format and step-by-step instructions.\n2. Follow the space's workflow: pull data from attached initiative issues, gather metrics, draft each section.\n3. Fetch external resources referenced by the space (tracking issues, dashboards) using other MCP tools.\n4. Show the draft after each section so the user can review and fill in gaps.\n5. Produce the final output in the format the space defines.\n\n### Example 5: Update Space Instructions Programmatically\n\n**User**: \"Update my PM Weekly Updates space to include a new writing guideline\"\n\n**Action**:\n1. Call `mcp__github__list_copilot_spaces` and find the space number (e.g., 19).\n2. Call `mcp__github__get_copilot_space` to read current instructions.\n3. Modify the instructions text as requested.\n4. Push the update:\n```bash\ngh api users\u002Flabudis\u002Fcopilot-spaces\u002F19 -X PUT -f general_instructions=\"updated instructions...\"\n```\n\n## Tips\n\n- Space names are **case-sensitive**. Use the exact name from `list_copilot_spaces`.\n- Spaces can be owned by users or organizations. Always provide both `owner` and `name`.\n- Space content can be large (20KB+). If returned as a temp file, use grep or view_range to find relevant sections rather than reading everything at once.\n- If a space isn't found, suggest listing available spaces to find the right name.\n- Spaces auto-update as underlying repos change, so the context is always current.\n- Some spaces contain custom instructions that should guide your behavior (coding standards, preferred patterns, workflows). Treat these as directives, not suggestions.\n- **Write operations** (`gh api` for create\u002Fupdate\u002Fdelete) require the `user` PAT scope. If you get a 404 on write operations, run `gh auth refresh -h github.com -s user`.\n- Resource updates **replace the entire array**. To add a resource, include all existing resources plus the new one. To remove one, include `{ \"id\": 123, \"_destroy\": true }` in the array.\n","# Copilot Spaces\n\nUse Copilot Spaces to bring curated, project-specific context into conversations. A Space is a shared collection of repositories, files, documentation, and instructions that grounds Copilot responses in your team's actual code and knowledge.\n\n## Available Tools\n\n### MCP Tools (Read-only)\n\n| Tool | Purpose |\n|------|---------|\n| `mcp__github__list_copilot_spaces` | List all spaces accessible to the current user |\n| `mcp__github__get_copilot_space` | Load a space's full context by owner and name |\n\n### REST API via `gh api` (Full CRUD)\n\nThe Spaces REST API supports creating, updating, deleting spaces, and managing collaborators. The MCP server only exposes read operations, so use `gh api` for writes.\n\n**User Spaces:**\n\n| Method | Endpoint | Purpose |\n|--------|----------|---------|\n| `POST` | `\u002Fusers\u002F{username}\u002Fcopilot-spaces` | Create a space |\n| `GET` | `\u002Fusers\u002F{username}\u002Fcopilot-spaces` | List spaces |\n| `GET` | `\u002Fusers\u002F{username}\u002Fcopilot-spaces\u002F{number}` | Get a space |\n| `PUT` | `\u002Fusers\u002F{username}\u002Fcopilot-spaces\u002F{number}` | Update a space |\n| `DELETE` | `\u002Fusers\u002F{username}\u002Fcopilot-spaces\u002F{number}` | Delete a space |\n\n**Organization Spaces:** Same pattern under `\u002Forgs\u002F{org}\u002Fcopilot-spaces\u002F...`\n\n**Collaborators:** Add, list, update, and remove collaborators at `...\u002Fcollaborators`\n\n**Scope requirements:** PAT needs `read:user` for reads, `user` for writes. Add with `gh auth refresh -h github.com -s user`.\n\n**Note:** This API is functional but not yet in the public REST API docs. It may require the `copilot_spaces_api` feature flag.\n\n## When to Use Spaces\n\n- User mentions \"Copilot space\" or asks to \"load a space\"\n- User wants answers grounded in specific project docs, code, or standards\n- User asks \"what spaces are available?\" or \"find a space for X\"\n- User needs onboarding context, architecture docs, or team-specific guidance\n- User wants to follow a structured workflow defined in a Space (templates, checklists, multi-step processes)\n\n## Workflow\n\n### 1. Discover Spaces\n\nWhen a user asks what spaces are available or you need to find the right space:\n\n```\nCall mcp__github__list_copilot_spaces\n```\n\nThis returns all spaces the user can access, each with a `name` and `owner_login`. Present relevant matches to the user.\n\nTo filter for a specific user's spaces, match `owner_login` against the username (e.g., \"show me my spaces\").\n\n### 2. Load a Space\n\nWhen a user names a specific space or you've identified the right one:\n\n```\nCall mcp__github__get_copilot_space with:\n  owner: \"org-or-user\"    (the owner_login from the list)\n  name: \"Space Name\"      (exact space name, case-sensitive)\n```\n\nThis returns the space's full content: attached documentation, code context, custom instructions, and any other curated materials. Use this context to inform your responses.\n\n### 3. Follow the Breadcrumbs\n\nSpace content often references external resources: GitHub issues, dashboards, repos, discussions, or other tools. Proactively fetch these using other MCP tools to gather complete context. For example:\n- A space references an initiative tracking issue. Use `issue_read` to get the latest comments.\n- A space links to a project board. Use project tools to check current status.\n- A space mentions a repo's masterplan. Use `get_file_contents` to read it.\n\n### 4. Answer or Execute\n\nOnce loaded, use the space content based on what it contains:\n\n**If the space contains reference material** (docs, code, standards):\n- Answer questions about the project's architecture, patterns, or standards\n- Generate code that follows the team's conventions\n- Debug issues using project-specific knowledge\n\n**If the space contains workflow instructions** (templates, step-by-step processes):\n- Follow the workflow as defined, step by step\n- Gather data from the sources the workflow specifies\n- Produce output in the format the workflow defines\n- Show progress after each step so the user can steer\n\n### 5. Manage Spaces (via `gh api`)\n\nWhen a user wants to create, update, or delete a space, use `gh api`. First, find the space number from the list endpoint.\n\n**Update a space's instructions:**\n```bash\ngh api users\u002F{username}\u002Fcopilot-spaces\u002F{number} \\\n  -X PUT \\\n  -f general_instructions=\"New instructions here\"\n```\n\n**Update name, description, or instructions together:**\n```bash\ngh api users\u002F{username}\u002Fcopilot-spaces\u002F{number} \\\n  -X PUT \\\n  -f name=\"Updated Name\" \\\n  -f description=\"Updated description\" \\\n  -f general_instructions=\"Updated instructions\"\n```\n\n**Create a new space:**\n```bash\ngh api users\u002F{username}\u002Fcopilot-spaces \\\n  -X POST \\\n  -f name=\"My New Space\" \\\n  -f general_instructions=\"Help me with...\" \\\n  -f visibility=\"private\"\n```\n\n**Attach resources (replaces entire resource list):**\n```json\n{\n  \"resources_attributes\": [\n    { \"resource_type\": \"free_text\", \"metadata\": { \"name\": \"Notes\", \"text\": \"Content here\" } },\n    { \"resource_type\": \"github_issue\", \"metadata\": { \"repository_id\": 12345, \"number\": 42 } },\n    { \"resource_type\": \"github_file\", \"metadata\": { \"repository_id\": 12345, \"file_path\": \"docs\u002Fguide.md\" } }\n  ]\n}\n```\n\n**Delete a space:**\n```bash\ngh api users\u002F{username}\u002Fcopilot-spaces\u002F{number} -X DELETE\n```\n\n**Updatable fields:** `name`, `description`, `general_instructions`, `icon_type`, `icon_color`, `visibility` (\"private\"\u002F\"public\"), `base_role` (\"no_access\"\u002F\"reader\"), `resources_attributes`\n\n## Examples\n\n### Example 1: User Asks for a Space\n\n**User**: \"Load the Accessibility copilot space\"\n\n**Action**:\n1. Call `mcp__github__get_copilot_space` with owner `\"github\"`, name `\"Accessibility\"`\n2. Use the returned context to answer questions about accessibility standards, MAS grades, compliance processes, etc.\n\n### Example 2: User Wants to Find Spaces\n\n**User**: \"What copilot spaces are available for our team?\"\n\n**Action**:\n1. Call `mcp__github__list_copilot_spaces`\n2. Filter\u002Fpresent spaces relevant to the user's org or interests\n3. Offer to load any space they're interested in\n\n### Example 3: Context-Grounded Question\n\n**User**: \"Using the security space, what's our policy on secret scanning?\"\n\n**Action**:\n1. Call `mcp__github__get_copilot_space` with the appropriate owner and name\n2. Find the relevant policy in the space content\n3. Answer based on the actual internal documentation\n\n### Example 4: Space as a Workflow Engine\n\n**User**: \"Write my weekly update using the PM Weekly Updates space\"\n\n**Action**:\n1. Call `mcp__github__get_copilot_space` to load the space. It contains a template format and step-by-step instructions.\n2. Follow the space's workflow: pull data from attached initiative issues, gather metrics, draft each section.\n3. Fetch external resources referenced by the space (tracking issues, dashboards) using other MCP tools.\n4. Show the draft after each section so the user can review and fill in gaps.\n5. Produce the final output in the format the space defines.\n\n### Example 5: Update Space Instructions Programmatically\n\n**User**: \"Update my PM Weekly Updates space to include a new writing guideline\"\n\n**Action**:\n1. Call `mcp__github__list_copilot_spaces` and find the space number (e.g., 19).\n2. Call `mcp__github__get_copilot_space` to read current instructions.\n3. Modify the instructions text as requested.\n4. Push the update:\n```bash\ngh api users\u002Flabudis\u002Fcopilot-spaces\u002F19 -X PUT -f general_instructions=\"updated instructions...\"\n```\n\n## Tips\n\n- Space names are **case-sensitive**. Use the exact name from `list_copilot_spaces`.\n- Spaces can be owned by users or organizations. Always provide both `owner` and `name`.\n- Space content can be large (20KB+). If returned as a temp file, use grep or view_range to find relevant sections rather than reading everything at once.\n- If a space isn't found, suggest listing available spaces to find the right name.\n- Spaces auto-update as underlying repos change, so the context is always current.\n- Some spaces contain custom instructions that should guide your behavior (coding standards, preferred patterns, workflows). Treat these as directives, not suggestions.\n- **Write operations** (`gh api` for create\u002Fupdate\u002Fdelete) require the `user` PAT scope. If you get a 404 on write operations, run `gh auth refresh -h github.com -s user`.\n- Resource updates **replace the entire array**. To add a resource, include all existing resources plus the new one. To remove one, include `{ \"id\": 123, \"_destroy\": true }` in the array.\n",{"name":5,"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92",".agents\u002Fskills\u002Fcopilot-spaces",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill copilot-spaces",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill copilot-spaces",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill copilot-spaces","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcopilot-spaces\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]