[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77V47YP1HHBAJXTDK23DY10":3,"skill-same:01M77V47YP1HHBAJXTDK23DY10":52},{"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},"01M77V47YP1HHBAJXTDK23DY10","pester-should-migration",null,"Experimental (preview) Pester skill for migrating classic Should -Be (v5) assertion syntax to the new Should-* (v6) assertions (note the hyphen, no space), e.g. `Should -Be` -> `Should-Be`, `Should -Not -Be` -> `Should-NotBe`. Tracks Pester 6, which is still a release candidate, so this guidance may change; verified against Pester 6.0.0-rc2. Use when converting Pester v5 assertions to Pester v6 Should-* operators, modernizing a Pester test suite, or when a user asks to migrate, convert, or rewrite `Should -...` calls in .Tests.ps1 \u002F PowerShell files.","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\u002Fpester-should-migration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Experimental (preview) Pester skill for migrating classic Should -Be (v5) assertion syntax to the new Should-* (v6) assertions (note the hyphen, no space), e.g. `Should -Be` -> `Should-Be`, `Should -Not -Be` -> `Should-NotBe`. Tracks Pester 6, which is still a release candidate, so this guidance may change; verified against Pester 6.0.0-rc2. Use when converting Pester v5 assertions to Pester v6 Should-* operators, modernizing a Pester test suite, or when a user asks to migrate, convert, or rewrite `Should -...` calls in .Tests.ps1 \u002F PowerShell files.\"\n---\n# Pester `Should -*` → `Should-*` Migration\n\nConvert classic Pester v5 assertions (`Should -Be`, space then parameter) to the\nnew Pester v6 `Should-*` assertions (`Should-Be`, hyphen, no space).\n\n> **Status: experimental \u002F preview.** Verified against Pester 6.0.0-rc2. The classic\n> `Should -Be` style still works in v6, so migrate incrementally and keep the suite green.\n\n> **Companion skill.** This skill covers the *optional* move to the new `Should-*` operators.\n> To upgrade a suite across major Pester versions (v3→v4→v5→v6 — the runtime, mocks, and config),\n> use the separate **pester-migration** skill. In v6 the classic `Should -Be` keeps working, so\n> adopting `Should-*` is independent of any version bump.\n\n## When to Use\n\n- Modernizing a Pester suite to the v6 `Should-*` assertions.\n- A user asks to migrate \u002F convert \u002F rewrite `Should -...` calls.\n- You want clearer, type-aware failure messages from the new assertions.\n\n## Know This First\n\n- **Both syntaxes work side by side in Pester v6.** Migration is optional and can\n  be done one test (or one file) at a time. Nothing breaks if you leave some classic.\n- **Requires Pester v6+.** The `Should-*` commands do not exist in v5.\n- **Negation is a separate command**, not a `-Not` switch: `Should -Not -Be` →\n  `Should-NotBe`. There is no `-Not` parameter on the new assertions.\n- **The actual value still comes from the pipeline** (`$x | Should-Be 1`) or from\n  `-Actual` (`Should-Be -Actual $x -Expected 1`). `-Because` carries over unchanged.\n- **Most renames are mechanical**, but several have behavior changes you must check\n  by hand — see [Gotchas](#step-3--check-the-behavioral-gotchas-do-not-skip).\n\n## Procedure\n\n### Step 1 — Find the classic assertions\n\nSearch the target for the classic space-separated syntax (the tell is `Should -`,\nor `Should` followed by `-Not`):\n\n```\nShould -          # any classic operator\nShould -Not -     # negated classic operator\nAssert-MockCalled # also removed in v6 -> Should-Invoke\n```\n\nLimit the scope to PowerShell test files (`*.Tests.ps1`, `*.ps1`).\n\n### Step 2 — Apply the mapping\n\nMost-used conversions (full list in [references\u002Fassertion-map.md](references\u002Fassertion-map.md)):\n\n| Classic (v5) | New (v6) |\n|---|---|\n| `$x \\| Should -Be 1` | `$x \\| Should-Be 1` |\n| `$x \\| Should -Not -Be 1` | `$x \\| Should-NotBe 1` |\n| `$x \\| Should -BeExactly 'A'` | `$x \\| Should-BeString 'A' -CaseSensitive` |\n| `$x \\| Should -BeGreaterOrEqual 2` | `$x \\| Should-BeGreaterThanOrEqual 2` |\n| `$x \\| Should -BeLessOrEqual 2` | `$x \\| Should-BeLessThanOrEqual 2` |\n| `$x \\| Should -BeLike 'a*'` | `$x \\| Should-BeLikeString 'a*'` |\n| `$x \\| Should -Match 're'` | `$x \\| Should-MatchString 're'` |\n| `$x \\| Should -BeOfType [int]` | `$x \\| Should-HaveType ([int])` |\n| `$x \\| Should -BeNullOrEmpty` | depends — see gotchas (no single equivalent) |\n| `$c \\| Should -HaveCount 3` | `$c \\| Should-BeCollection -Count 3` |\n| `$c \\| Should -Contain 2` | `$c \\| Should-ContainCollection 2` |\n| `{ ... } \\| Should -Throw 'msg'` | `{ ... } \\| Should-Throw -ExceptionMessage 'msg'` |\n| `Should -Invoke Get-Thing` | `Should-Invoke Get-Thing` |\n| `Should -InvokeVerifiable` | `Should-Invoke -Verifiable` |\n\n### Step 3 — Check the behavioral gotchas (do NOT skip)\n\nThese do **not** translate by a plain rename. Read each before converting:\n\n1. **Case sensitivity.** Classic `Should -Be` is case-insensitive on strings; so is\n   `Should-Be`. But classic `Should -BeExactly` (case-sensitive) has **no** plain\n   equivalent — use `Should-BeString -CaseSensitive`. (`Should-Be` is never\n   case-sensitive.) Same pattern for `BeLikeExactly` → `Should-BeLikeString -CaseSensitive`\n   and `MatchExactly` → `Should-MatchString -CaseSensitive`.\n2. **Truthy vs. true.** Classic `Should -BeTrue` \u002F `-BeFalse` accept any *truthy* \u002F\n   *falsy* value (`1`, `'x'`, `0`, `''`, `$null`, `@()`). The new `Should-BeTrue` \u002F\n   `Should-BeFalse` are **strict** (exactly `$true` \u002F `$false`). To preserve the old\n   loose behavior use `Should-BeTruthy` \u002F `Should-BeFalsy`. Only use the strict ones\n   when the value really is a boolean.\n3. **`BeNullOrEmpty` has no single equivalent.** Pick by intent: `$null` →\n   `Should-BeNull`; empty string → `Should-BeEmptyString`; empty collection →\n   `Should-BeCollection -Count 0`; broad \"falsy\" → `Should-BeFalsy`. The negation\n   `Should -Not -BeNullOrEmpty` similarly splits into `Should-NotBeNull` \u002F\n   `Should-NotBeEmptyString` \u002F `Should-NotBeWhiteSpaceString`.\n4. **Collections.** Classic `Should -Be` also compares arrays; the new `Should-Be` is\n   a *value* assertion and **errors** if `-Expected` is a collection (\"You provided a\n   collection to the -Expected parameter\"). Use `Should-BeCollection` to compare arrays.\n   `Should -Contain` (single-item membership) → `Should-ContainCollection`. The new\n   command also takes a **collection** of expected items and checks they are all present,\n   in the right order (`1, 2, 3 | Should-ContainCollection @(1, 2)`). For exact,\n   whole-collection equality use `Should-BeCollection` instead.\n5. **Pipeline unwrapping.** The pipeline unwraps input: a value assertion sees `@(1)`\n   as `1` and `@()` as `$null`, and a typed collection (`[int[]]`) is re-collected as\n   `[object[]]`. When the exact value or concrete collection type matters (e.g.\n   `Should-HaveType`), pass it with `-Actual` instead of piping.\n6. **No `Should-*` equivalent.** `Should -Exist` and the `Should -FileContentMatch*`\n   family have no new counterpart. Either keep the classic assertion, or rewrite with\n   PowerShell: `Test-Path $p | Should-BeTrue`, `(Get-Content $p -Raw) | Should-MatchString 're'`.\n7. **`Should -BeIn` direction.** No `Should-BeIn`. Reverse the operands:\n   `$value | Should -BeIn $collection` → `$collection | Should-ContainCollection $value`\n   (note the actual\u002Fexpected swap), or keep the classic form.\n\n### Step 4 — Verify\n\nRun the suite and confirm it's still green — the new messages differ, but passes\nmust stay passes:\n\n```powershell\nInvoke-Pester -Path .\u002Ftests\n```\n\nIf a converted assertion newly fails, re-check the gotchas above (most often #2\ntruthy\u002Ffalsy, #3 null-or-empty, or #4 collections).\n\n### Step 5 — (Optional) Enforce the new style\n\nOnce a suite is fully migrated, switch off the classic syntax so it can't creep back:\n\n```powershell\n$config = New-PesterConfiguration\n$config.Should.DisableV5 = $true\n```\n\nWith this set, any remaining `Should -Be` throws and points at the `Should-Be` form.\n\n## Output\n\nSummarize what changed: files touched, count of assertions converted, any classic\nassertions intentionally left (e.g. `Should -Exist`), and any conversions that need\na human decision (truthy\u002Ffalsy, null-or-empty, collection semantics).\n\n## Reference\n\n- [references\u002Fassertion-map.md](references\u002Fassertion-map.md) — full operator-by-operator\n  table with before\u002Fafter examples and workarounds.\n- Live command reference: `https:\u002F\u002Fpester.dev\u002Fdocs\u002Fcommands\u002FShould-Be` (swap in any\n  `Should-*` name) for exact parameters and examples.\n- Concepts: `https:\u002F\u002Fpester.dev\u002Fdocs\u002Fassertions\u002Fshould-command` (value vs. collection\n  assertions, pipeline vs. `-Actual`).\n- v5→v6 upgrade guide: `https:\u002F\u002Fpester.dev\u002Fdocs\u002Fmigrations\u002Fv5-to-v6`.\n","# Pester `Should -*` → `Should-*` Migration\n\nConvert classic Pester v5 assertions (`Should -Be`, space then parameter) to the\nnew Pester v6 `Should-*` assertions (`Should-Be`, hyphen, no space).\n\n> **Status: experimental \u002F preview.** Verified against Pester 6.0.0-rc2. The classic\n> `Should -Be` style still works in v6, so migrate incrementally and keep the suite green.\n\n> **Companion skill.** This skill covers the *optional* move to the new `Should-*` operators.\n> To upgrade a suite across major Pester versions (v3→v4→v5→v6 — the runtime, mocks, and config),\n> use the separate **pester-migration** skill. In v6 the classic `Should -Be` keeps working, so\n> adopting `Should-*` is independent of any version bump.\n\n## When to Use\n\n- Modernizing a Pester suite to the v6 `Should-*` assertions.\n- A user asks to migrate \u002F convert \u002F rewrite `Should -...` calls.\n- You want clearer, type-aware failure messages from the new assertions.\n\n## Know This First\n\n- **Both syntaxes work side by side in Pester v6.** Migration is optional and can\n  be done one test (or one file) at a time. Nothing breaks if you leave some classic.\n- **Requires Pester v6+.** The `Should-*` commands do not exist in v5.\n- **Negation is a separate command**, not a `-Not` switch: `Should -Not -Be` →\n  `Should-NotBe`. There is no `-Not` parameter on the new assertions.\n- **The actual value still comes from the pipeline** (`$x | Should-Be 1`) or from\n  `-Actual` (`Should-Be -Actual $x -Expected 1`). `-Because` carries over unchanged.\n- **Most renames are mechanical**, but several have behavior changes you must check\n  by hand — see [Gotchas](#step-3--check-the-behavioral-gotchas-do-not-skip).\n\n## Procedure\n\n### Step 1 — Find the classic assertions\n\nSearch the target for the classic space-separated syntax (the tell is `Should -`,\nor `Should` followed by `-Not`):\n\n```\nShould -          # any classic operator\nShould -Not -     # negated classic operator\nAssert-MockCalled # also removed in v6 -> Should-Invoke\n```\n\nLimit the scope to PowerShell test files (`*.Tests.ps1`, `*.ps1`).\n\n### Step 2 — Apply the mapping\n\nMost-used conversions (full list in [references\u002Fassertion-map.md](references\u002Fassertion-map.md)):\n\n| Classic (v5) | New (v6) |\n|---|---|\n| `$x \\| Should -Be 1` | `$x \\| Should-Be 1` |\n| `$x \\| Should -Not -Be 1` | `$x \\| Should-NotBe 1` |\n| `$x \\| Should -BeExactly 'A'` | `$x \\| Should-BeString 'A' -CaseSensitive` |\n| `$x \\| Should -BeGreaterOrEqual 2` | `$x \\| Should-BeGreaterThanOrEqual 2` |\n| `$x \\| Should -BeLessOrEqual 2` | `$x \\| Should-BeLessThanOrEqual 2` |\n| `$x \\| Should -BeLike 'a*'` | `$x \\| Should-BeLikeString 'a*'` |\n| `$x \\| Should -Match 're'` | `$x \\| Should-MatchString 're'` |\n| `$x \\| Should -BeOfType [int]` | `$x \\| Should-HaveType ([int])` |\n| `$x \\| Should -BeNullOrEmpty` | depends — see gotchas (no single equivalent) |\n| `$c \\| Should -HaveCount 3` | `$c \\| Should-BeCollection -Count 3` |\n| `$c \\| Should -Contain 2` | `$c \\| Should-ContainCollection 2` |\n| `{ ... } \\| Should -Throw 'msg'` | `{ ... } \\| Should-Throw -ExceptionMessage 'msg'` |\n| `Should -Invoke Get-Thing` | `Should-Invoke Get-Thing` |\n| `Should -InvokeVerifiable` | `Should-Invoke -Verifiable` |\n\n### Step 3 — Check the behavioral gotchas (do NOT skip)\n\nThese do **not** translate by a plain rename. Read each before converting:\n\n1. **Case sensitivity.** Classic `Should -Be` is case-insensitive on strings; so is\n   `Should-Be`. But classic `Should -BeExactly` (case-sensitive) has **no** plain\n   equivalent — use `Should-BeString -CaseSensitive`. (`Should-Be` is never\n   case-sensitive.) Same pattern for `BeLikeExactly` → `Should-BeLikeString -CaseSensitive`\n   and `MatchExactly` → `Should-MatchString -CaseSensitive`.\n2. **Truthy vs. true.** Classic `Should -BeTrue` \u002F `-BeFalse` accept any *truthy* \u002F\n   *falsy* value (`1`, `'x'`, `0`, `''`, `$null`, `@()`). The new `Should-BeTrue` \u002F\n   `Should-BeFalse` are **strict** (exactly `$true` \u002F `$false`). To preserve the old\n   loose behavior use `Should-BeTruthy` \u002F `Should-BeFalsy`. Only use the strict ones\n   when the value really is a boolean.\n3. **`BeNullOrEmpty` has no single equivalent.** Pick by intent: `$null` →\n   `Should-BeNull`; empty string → `Should-BeEmptyString`; empty collection →\n   `Should-BeCollection -Count 0`; broad \"falsy\" → `Should-BeFalsy`. The negation\n   `Should -Not -BeNullOrEmpty` similarly splits into `Should-NotBeNull` \u002F\n   `Should-NotBeEmptyString` \u002F `Should-NotBeWhiteSpaceString`.\n4. **Collections.** Classic `Should -Be` also compares arrays; the new `Should-Be` is\n   a *value* assertion and **errors** if `-Expected` is a collection (\"You provided a\n   collection to the -Expected parameter\"). Use `Should-BeCollection` to compare arrays.\n   `Should -Contain` (single-item membership) → `Should-ContainCollection`. The new\n   command also takes a **collection** of expected items and checks they are all present,\n   in the right order (`1, 2, 3 | Should-ContainCollection @(1, 2)`). For exact,\n   whole-collection equality use `Should-BeCollection` instead.\n5. **Pipeline unwrapping.** The pipeline unwraps input: a value assertion sees `@(1)`\n   as `1` and `@()` as `$null`, and a typed collection (`[int[]]`) is re-collected as\n   `[object[]]`. When the exact value or concrete collection type matters (e.g.\n   `Should-HaveType`), pass it with `-Actual` instead of piping.\n6. **No `Should-*` equivalent.** `Should -Exist` and the `Should -FileContentMatch*`\n   family have no new counterpart. Either keep the classic assertion, or rewrite with\n   PowerShell: `Test-Path $p | Should-BeTrue`, `(Get-Content $p -Raw) | Should-MatchString 're'`.\n7. **`Should -BeIn` direction.** No `Should-BeIn`. Reverse the operands:\n   `$value | Should -BeIn $collection` → `$collection | Should-ContainCollection $value`\n   (note the actual\u002Fexpected swap), or keep the classic form.\n\n### Step 4 — Verify\n\nRun the suite and confirm it's still green — the new messages differ, but passes\nmust stay passes:\n\n```powershell\nInvoke-Pester -Path .\u002Ftests\n```\n\nIf a converted assertion newly fails, re-check the gotchas above (most often #2\ntruthy\u002Ffalsy, #3 null-or-empty, or #4 collections).\n\n### Step 5 — (Optional) Enforce the new style\n\nOnce a suite is fully migrated, switch off the classic syntax so it can't creep back:\n\n```powershell\n$config = New-PesterConfiguration\n$config.Should.DisableV5 = $true\n```\n\nWith this set, any remaining `Should -Be` throws and points at the `Should-Be` form.\n\n## Output\n\nSummarize what changed: files touched, count of assertions converted, any classic\nassertions intentionally left (e.g. `Should -Exist`), and any conversions that need\na human decision (truthy\u002Ffalsy, null-or-empty, collection semantics).\n\n## Reference\n\n- [references\u002Fassertion-map.md](references\u002Fassertion-map.md) — full operator-by-operator\n  table with before\u002Fafter examples and workarounds.\n- Live command reference: `https:\u002F\u002Fpester.dev\u002Fdocs\u002Fcommands\u002FShould-Be` (swap in any\n  `Should-*` name) for exact parameters and examples.\n- Concepts: `https:\u002F\u002Fpester.dev\u002Fdocs\u002Fassertions\u002Fshould-command` (value vs. collection\n  assertions, pipeline vs. `-Actual`).\n- v5→v6 upgrade guide: `https:\u002F\u002Fpester.dev\u002Fdocs\u002Fmigrations\u002Fv5-to-v6`.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fpester-should-migration",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 pester-should-migration",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill pester-should-migration",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill pester-should-migration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpester-should-migration\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fassertion-map.md","REFERENCE","参考文档",9561,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpester-should-migration\u002Freferences\u002Fassertion-map.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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",[],[]]