[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77NJRATBMTCV3RAY8F18VMC":3,"skill-same:01M77NJRATBMTCV3RAY8F18VMC":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},"01M77NJRATBMTCV3RAY8F18VMC","acreadiness-generate-instructions",null,"Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github\u002Fcopilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running \u002Facreadiness-assess to close gaps in the AI Tooling pillar.","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\u002Fagent\u002Fskills\u002Facreadiness-generate-instructions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github\u002Fcopilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running \u002Facreadiness-assess to close gaps in the AI Tooling pillar.\"\n---\n# \u002Facreadiness-generate-instructions — write AI agent instructions\n\nUse this skill whenever the user wants to **create**, **regenerate**, or **refresh** their custom instructions for AI coding agents (Copilot, Claude, etc.). This is the *Generate* step in AgentRC's **Measure → Generate → Maintain** loop and the single highest-leverage action for the **AI Tooling** pillar.\n\n## Output options\n\nVS Code recognises several instruction file types — AgentRC generates the most common ones:\n\n| File | Scope | When to use |\n|---|---|---|\n| `.github\u002Fcopilot-instructions.md` | Always-on, whole workspace | **Default** — VS Code Copilot's native instruction file |\n| `AGENTS.md` | Always-on, whole workspace | Multi-agent repos (Copilot + Claude + others) |\n| `.github\u002Finstructions\u002F*.instructions.md` | Scoped by `applyTo` glob | Per-area \u002F per-language rules in monorepos |\n| `CLAUDE.md` | Claude-specific | Add via `--claude-md` (nested only) |\n\n## Strategies\n\n- **`flat`** *(default)* — single `.github\u002Fcopilot-instructions.md` at the chosen path. Simple, easy to review.\n- **`nested`** — hub at `.github\u002Fcopilot-instructions.md` + per-topic detail files at `.github\u002Finstructions\u002F\u003Ctopic>.instructions.md`, each with an `applyTo` glob so VS Code only loads the topic when it's relevant. Better for large or multi-stack repos.\n\n> **Why `.github\u002Finstructions\u002F` and not `.agents\u002F`?** AgentRC's default nested layout writes to `.agents\u002F`, which is the right home for *agent-agnostic* repos (Copilot + Claude + Cursor reading `AGENTS.md`). For VS Code Copilot specifically, the native location is `.github\u002Finstructions\u002F` with `applyTo` frontmatter — that's what Copilot auto-discovers. This skill rewrites AgentRC's nested output to the VS Code-native location whenever the main output is `.github\u002Fcopilot-instructions.md`. If you instead chose `--output AGENTS.md`, nested keeps AgentRC's default `.agents\u002F` layout.\n\nFor monorepos, generate **area-scoped** instructions with `--areas`, `--area \u003Cname>`, or `--areas-only`. Areas are defined in `agentrc.config.json`. Per-area output is written as VS Code `.instructions.md` files with an `applyTo` glob (see below).\n\n### Topic vs area `.instructions.md` files\n\nBoth end up in `.github\u002Finstructions\u002F` but they answer different questions:\n\n| Kind | Filename example | `applyTo` example | Where it comes from |\n|---|---|---|---|\n| **Topic** (nested) | `testing.instructions.md` | `**\u002F*.{test,spec}.{ts,tsx,js}` | AgentRC `--strategy nested` topic split |\n| **Area** (monorepo) | `frontend.instructions.md` | `apps\u002Ffrontend\u002F**` | `agentrc.config.json` areas + `--areas` |\n\nYou can have both at once: a nested set of topic files plus per-area files for a monorepo.\n\n## Per-area files with `applyTo`\n\nWhen the user opts into areas, emit one VS Code-native `.instructions.md` file per area at `.github\u002Finstructions\u002F\u003Carea>.instructions.md`. Each file MUST start with frontmatter declaring the glob the rules apply to:\n\n```markdown\n---\napplyTo: \"apps\u002Ffrontend\u002F**\"\n---\n\n# Frontend area instructions\n\n…AgentRC-generated content for this area…\n```\n\nWorkflow:\n\n1. **Read `agentrc.config.json`** to discover declared areas and their `paths` \u002F globs. If `paths` is missing, ask the user for the glob (e.g. `src\u002Fapi\u002F**`).\n2. **Run `agentrc instructions --areas`** (or `--area \u003Cname>`) to produce the per-area body content.\n3. **Wrap each area's content** in `.github\u002Finstructions\u002F\u003Carea>.instructions.md` with the `applyTo` frontmatter taken from the area's `paths`. If the user passed `--apply-to \u003Cglob>` on a single-area call, use that glob verbatim.\n4. **Leave the main file alone** — the root `.github\u002Fcopilot-instructions.md` stays as the always-on instructions; `.instructions.md` files only kick in for matching paths.\n\nNaming: lowercase, kebab-case area name. Examples: `.github\u002Finstructions\u002Ffrontend.instructions.md`, `.github\u002Finstructions\u002Fapi.instructions.md`, `.github\u002Finstructions\u002Finfra.instructions.md`.\n\n## Steps\n\n1. **Pick the target file**. **Default to `.github\u002Fcopilot-instructions.md`.** Switch to `AGENTS.md` only if the user mentions multi-agent \u002F Claude \u002F Cursor support.\n2. **Always ask which strategy to use** — `flat` or `nested` — unless the user already specified one in their message or via `--strategy`. Present the trade-off briefly:\n   - **Flat** *(default)* — one `.github\u002Fcopilot-instructions.md`. Simple, easy to review in a single PR. Best for small\u002Fmedium repos with one stack.\n   - **Nested** — hub `.github\u002Fcopilot-instructions.md` + per-topic `.github\u002Finstructions\u002F\u003Ctopic>.instructions.md` files (each with an `applyTo` glob so VS Code only loads them when relevant). Best for large or multi-stack repos. Add `--claude-md` to also emit `CLAUDE.md`.\n   Recommend `nested` proactively when the repo has > 5 top-level directories, multiple stacks, or already uses a monorepo tool (turbo\u002Fnx\u002Fpnpm workspaces).\n3. **Detect monorepo areas** by reading `agentrc.config.json`. If areas exist, ask the user whether they want **per-area `.instructions.md` files with `applyTo`** in addition to the root file. Default to \"yes\" when `agentrc.config.json` declares areas.\n4. **Run dry-run first** so the user can preview:\n   ```bash\n   npx -y github:microsoft\u002Fagentrc instructions --output \u003Cfile> --strategy \u003Cflat|nested> [--areas|--area \u003Cname>] [--claude-md] --dry-run\n   ```\n5. **Show a short summary** of what would change — files that would be created or overwritten, area count + their `applyTo` globs, model used (default `claude-sonnet-4.6`).\n6. **On confirmation, run the same command without `--dry-run`** (and optionally `--force` if files already exist).\n7. **Post-process layout for Copilot output**:\n   - **If `--output` ends in `copilot-instructions.md` and strategy is `nested`**: move\u002Frewrite AgentRC's `.agents\u002F\u003Ctopic>.md` files to `.github\u002Finstructions\u002F\u003Ctopic>.instructions.md`. Add frontmatter to each file with an appropriate `applyTo` glob (see \"Topic applyTo defaults\" below). Delete the now-empty `.agents\u002F` directory.\n   - **If `--areas` was used**: also write `.github\u002Finstructions\u002F\u003Carea>.instructions.md` for every area, using each area's `paths` from `agentrc.config.json` as the `applyTo` glob (override with `--apply-to` for single-area calls).\n   - **If `--output AGENTS.md`** was chosen: keep AgentRC's native `.agents\u002F` layout for nested — agent-agnostic readers expect it there.\n   Create the `.github\u002Finstructions\u002F` directory if missing.\n\n### Topic `applyTo` defaults\n\nWhen promoting AgentRC's nested topic files to `.instructions.md`, use these defaults unless the user specifies otherwise:\n\n| Topic | Default `applyTo` |\n|---|---|\n| `testing` | `**\u002F*.{test,spec}.{ts,tsx,js,jsx,mjs,cjs}` |\n| `style` \u002F `code-quality` \u002F `formatting` | `**\u002F*.{ts,tsx,js,jsx,mjs,cjs,py,go,rs,java,kt,cs}` |\n| `build` \u002F `ci` | `**\u002F{package.json,turbo.json,nx.json,.github\u002Fworkflows\u002F**}` |\n| `docs` | `**\u002F*.md` |\n| `security` | `**` |\n| anything else \u002F hub-level | `**` |\n8. **Verify** by reading the generated file(s) back and showing the user a 1-paragraph synopsis: stack detected, conventions captured, length, list of `.instructions.md` files with their globs.\n9. **Suggest next steps**:\n   - Re-run the `assess` skill to confirm the AI Tooling pillar score improved.\n   - If the user already has both `copilot-instructions.md` and `AGENTS.md`, recommend consolidating to a single source of truth (AgentRC flags this at maturity Level 2+).\n\n## Notes\n\n- AgentRC reads your **actual code** — no templates. Output reflects detected languages, frameworks, and conventions.\n- `--claude-md` (nested strategy only) also emits `CLAUDE.md`.\n- VS Code applies `.instructions.md` files automatically when the active file matches `applyTo`. The root `.github\u002Fcopilot-instructions.md` always loads.\n- Never run this skill non-interactively in CI; instructions are part of the repo and should land via PR.\n","# \u002Facreadiness-generate-instructions — write AI agent instructions\n\nUse this skill whenever the user wants to **create**, **regenerate**, or **refresh** their custom instructions for AI coding agents (Copilot, Claude, etc.). This is the *Generate* step in AgentRC's **Measure → Generate → Maintain** loop and the single highest-leverage action for the **AI Tooling** pillar.\n\n## Output options\n\nVS Code recognises several instruction file types — AgentRC generates the most common ones:\n\n| File | Scope | When to use |\n|---|---|---|\n| `.github\u002Fcopilot-instructions.md` | Always-on, whole workspace | **Default** — VS Code Copilot's native instruction file |\n| `AGENTS.md` | Always-on, whole workspace | Multi-agent repos (Copilot + Claude + others) |\n| `.github\u002Finstructions\u002F*.instructions.md` | Scoped by `applyTo` glob | Per-area \u002F per-language rules in monorepos |\n| `CLAUDE.md` | Claude-specific | Add via `--claude-md` (nested only) |\n\n## Strategies\n\n- **`flat`** *(default)* — single `.github\u002Fcopilot-instructions.md` at the chosen path. Simple, easy to review.\n- **`nested`** — hub at `.github\u002Fcopilot-instructions.md` + per-topic detail files at `.github\u002Finstructions\u002F\u003Ctopic>.instructions.md`, each with an `applyTo` glob so VS Code only loads the topic when it's relevant. Better for large or multi-stack repos.\n\n> **Why `.github\u002Finstructions\u002F` and not `.agents\u002F`?** AgentRC's default nested layout writes to `.agents\u002F`, which is the right home for *agent-agnostic* repos (Copilot + Claude + Cursor reading `AGENTS.md`). For VS Code Copilot specifically, the native location is `.github\u002Finstructions\u002F` with `applyTo` frontmatter — that's what Copilot auto-discovers. This skill rewrites AgentRC's nested output to the VS Code-native location whenever the main output is `.github\u002Fcopilot-instructions.md`. If you instead chose `--output AGENTS.md`, nested keeps AgentRC's default `.agents\u002F` layout.\n\nFor monorepos, generate **area-scoped** instructions with `--areas`, `--area \u003Cname>`, or `--areas-only`. Areas are defined in `agentrc.config.json`. Per-area output is written as VS Code `.instructions.md` files with an `applyTo` glob (see below).\n\n### Topic vs area `.instructions.md` files\n\nBoth end up in `.github\u002Finstructions\u002F` but they answer different questions:\n\n| Kind | Filename example | `applyTo` example | Where it comes from |\n|---|---|---|---|\n| **Topic** (nested) | `testing.instructions.md` | `**\u002F*.{test,spec}.{ts,tsx,js}` | AgentRC `--strategy nested` topic split |\n| **Area** (monorepo) | `frontend.instructions.md` | `apps\u002Ffrontend\u002F**` | `agentrc.config.json` areas + `--areas` |\n\nYou can have both at once: a nested set of topic files plus per-area files for a monorepo.\n\n## Per-area files with `applyTo`\n\nWhen the user opts into areas, emit one VS Code-native `.instructions.md` file per area at `.github\u002Finstructions\u002F\u003Carea>.instructions.md`. Each file MUST start with frontmatter declaring the glob the rules apply to:\n\n```markdown\n---\napplyTo: \"apps\u002Ffrontend\u002F**\"\n---\n\n# Frontend area instructions\n\n…AgentRC-generated content for this area…\n```\n\nWorkflow:\n\n1. **Read `agentrc.config.json`** to discover declared areas and their `paths` \u002F globs. If `paths` is missing, ask the user for the glob (e.g. `src\u002Fapi\u002F**`).\n2. **Run `agentrc instructions --areas`** (or `--area \u003Cname>`) to produce the per-area body content.\n3. **Wrap each area's content** in `.github\u002Finstructions\u002F\u003Carea>.instructions.md` with the `applyTo` frontmatter taken from the area's `paths`. If the user passed `--apply-to \u003Cglob>` on a single-area call, use that glob verbatim.\n4. **Leave the main file alone** — the root `.github\u002Fcopilot-instructions.md` stays as the always-on instructions; `.instructions.md` files only kick in for matching paths.\n\nNaming: lowercase, kebab-case area name. Examples: `.github\u002Finstructions\u002Ffrontend.instructions.md`, `.github\u002Finstructions\u002Fapi.instructions.md`, `.github\u002Finstructions\u002Finfra.instructions.md`.\n\n## Steps\n\n1. **Pick the target file**. **Default to `.github\u002Fcopilot-instructions.md`.** Switch to `AGENTS.md` only if the user mentions multi-agent \u002F Claude \u002F Cursor support.\n2. **Always ask which strategy to use** — `flat` or `nested` — unless the user already specified one in their message or via `--strategy`. Present the trade-off briefly:\n   - **Flat** *(default)* — one `.github\u002Fcopilot-instructions.md`. Simple, easy to review in a single PR. Best for small\u002Fmedium repos with one stack.\n   - **Nested** — hub `.github\u002Fcopilot-instructions.md` + per-topic `.github\u002Finstructions\u002F\u003Ctopic>.instructions.md` files (each with an `applyTo` glob so VS Code only loads them when relevant). Best for large or multi-stack repos. Add `--claude-md` to also emit `CLAUDE.md`.\n   Recommend `nested` proactively when the repo has > 5 top-level directories, multiple stacks, or already uses a monorepo tool (turbo\u002Fnx\u002Fpnpm workspaces).\n3. **Detect monorepo areas** by reading `agentrc.config.json`. If areas exist, ask the user whether they want **per-area `.instructions.md` files with `applyTo`** in addition to the root file. Default to \"yes\" when `agentrc.config.json` declares areas.\n4. **Run dry-run first** so the user can preview:\n   ```bash\n   npx -y github:microsoft\u002Fagentrc instructions --output \u003Cfile> --strategy \u003Cflat|nested> [--areas|--area \u003Cname>] [--claude-md] --dry-run\n   ```\n5. **Show a short summary** of what would change — files that would be created or overwritten, area count + their `applyTo` globs, model used (default `claude-sonnet-4.6`).\n6. **On confirmation, run the same command without `--dry-run`** (and optionally `--force` if files already exist).\n7. **Post-process layout for Copilot output**:\n   - **If `--output` ends in `copilot-instructions.md` and strategy is `nested`**: move\u002Frewrite AgentRC's `.agents\u002F\u003Ctopic>.md` files to `.github\u002Finstructions\u002F\u003Ctopic>.instructions.md`. Add frontmatter to each file with an appropriate `applyTo` glob (see \"Topic applyTo defaults\" below). Delete the now-empty `.agents\u002F` directory.\n   - **If `--areas` was used**: also write `.github\u002Finstructions\u002F\u003Carea>.instructions.md` for every area, using each area's `paths` from `agentrc.config.json` as the `applyTo` glob (override with `--apply-to` for single-area calls).\n   - **If `--output AGENTS.md`** was chosen: keep AgentRC's native `.agents\u002F` layout for nested — agent-agnostic readers expect it there.\n   Create the `.github\u002Finstructions\u002F` directory if missing.\n\n### Topic `applyTo` defaults\n\nWhen promoting AgentRC's nested topic files to `.instructions.md`, use these defaults unless the user specifies otherwise:\n\n| Topic | Default `applyTo` |\n|---|---|\n| `testing` | `**\u002F*.{test,spec}.{ts,tsx,js,jsx,mjs,cjs}` |\n| `style` \u002F `code-quality` \u002F `formatting` | `**\u002F*.{ts,tsx,js,jsx,mjs,cjs,py,go,rs,java,kt,cs}` |\n| `build` \u002F `ci` | `**\u002F{package.json,turbo.json,nx.json,.github\u002Fworkflows\u002F**}` |\n| `docs` | `**\u002F*.md` |\n| `security` | `**` |\n| anything else \u002F hub-level | `**` |\n8. **Verify** by reading the generated file(s) back and showing the user a 1-paragraph synopsis: stack detected, conventions captured, length, list of `.instructions.md` files with their globs.\n9. **Suggest next steps**:\n   - Re-run the `assess` skill to confirm the AI Tooling pillar score improved.\n   - If the user already has both `copilot-instructions.md` and `AGENTS.md`, recommend consolidating to a single source of truth (AgentRC flags this at maturity Level 2+).\n\n## Notes\n\n- AgentRC reads your **actual code** — no templates. Output reflects detected languages, frameworks, and conventions.\n- `--claude-md` (nested strategy only) also emits `CLAUDE.md`.\n- VS Code applies `.instructions.md` files automatically when the active file matches `applyTo`. The root `.github\u002Fcopilot-instructions.md` always loads.\n- Never run this skill non-interactively in CI; instructions are part of the repo and should land via PR.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Facreadiness-generate-instructions",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 acreadiness-generate-instructions",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill acreadiness-generate-instructions",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill acreadiness-generate-instructions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Facreadiness-generate-instructions\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",[],[]]