[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77V43GPXXQX569MDR7BBV2G":3,"skill-same:01M77V43GPXXQX569MDR7BBV2G":60},{"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},"01M77V43GPXXQX569MDR7BBV2G","pester-migration",null,"Pester migration skill for upgrading PowerShell Pester test suites across major versions — v3→v4, v4→v5, and v5→v6. Covers the Discovery\u002FRun two-phase model, moving setup into BeforeAll, $PSScriptRoot vs $MyInvocation, mock changes (Assert-MockCalled → Should -Invoke, removed fall-through), Invoke-Pester parameters → PesterConfiguration, data-driven -ForEach\u002F-TestCases, and the v6 breaking changes. Use when the user asks to upgrade, migrate, or modernize Pester tests, fix *.Tests.ps1 files that broke after bumping the Pester version, or convert legacy Should \u002F Invoke-Pester syntax.","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-migration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Pester migration skill for upgrading PowerShell Pester test suites across major versions — v3→v4, v4→v5, and v5→v6. Covers the Discovery\u002FRun two-phase model, moving setup into BeforeAll, $PSScriptRoot vs $MyInvocation, mock changes (Assert-MockCalled → Should -Invoke, removed fall-through), Invoke-Pester parameters → PesterConfiguration, data-driven -ForEach\u002F-TestCases, and the v6 breaking changes. Use when the user asks to upgrade, migrate, or modernize Pester tests, fix *.Tests.ps1 files that broke after bumping the Pester version, or convert legacy Should \u002F Invoke-Pester syntax.\"\n---\n# Pester Migration\n\nPester is the test framework for PowerShell. Test files end in `*.Tests.ps1` and use\n`Describe` \u002F `Context` \u002F `It` blocks with `Should` assertions. This skill upgrades an existing\nsuite from one major Pester version to the next and gets it green again.\n\n> **Mental model:** each major jump has a different character. **v3→v4** is mostly a syntax\n> rename. **v4→v5** is a *fundamental runtime change* (the Discovery\u002FRun split) and is the hard\n> one. **v5→v6** is largely backwards-compatible — a handful of previously-deprecated things now\n> throw. Migrate **one major at a time**; never skip a version.\n\nDetailed, symptom-driven guides live in `references\u002F` — load the one(s) for the jump you are doing.\n\n## References\n\n| Reference | When to load |\n|---|---|\n| [v3-to-v4.md](references\u002Fv3-to-v4.md) | `Should Be` → `Should -Be`, `Contain` → `FileContentMatch`, `Assert-VerifiableMocks` → `Assert-VerifiableMock`, array-assertion edge cases. |\n| [v4-to-v5.md](references\u002Fv4-to-v5.md) | The big one. Discovery\u002FRun phases, `BeforeAll` setup, `$PSScriptRoot`, `BeforeDiscovery`, `-ForEach`, mock scoping, `Should -Throw` wildcards, `Invoke-Pester` → `New-PesterConfiguration`. |\n| [v5-to-v6.md](references\u002Fv5-to-v6.md) | PowerShell 5.1\u002F7.4+ only, per-file discovery+run, empty `-ForEach` throws, duplicate setup blocks throw, name `\u003C...>` templates evaluate, `Assert-MockCalled` removed, mocks no longer fall through, code-coverage tracer, legacy `Invoke-Pester` params removed. |\n\nCanonical source: the official migration guides at https:\u002F\u002Fpester.dev\u002Fdocs\u002Fmigrations\u002F — this skill\nmirrors them. When in doubt, prefer the website.\n\n## Step 0 — Detect where you are and where you're going\n\nFind the installed version(s) and the version the **tests** were written for. These can differ.\n\n```powershell\n# Installed Pester version(s) on this machine\nGet-Module Pester -ListAvailable | Select-Object Name, Version, Path\n\n# Version currently imported in the session\n(Get-Module Pester).Version\n```\n\nTell the source version from the **test code** with these heuristics:\n\n| You see in `*.Tests.ps1` \u002F build scripts | Suite was written for |\n|---|---|\n| `Should Be` \u002F `Should Contain` (no dash) | v3 or earlier → start at [v3-to-v4](references\u002Fv3-to-v4.md) |\n| `$MyInvocation.MyCommand.Path` + dot-source at the **top** of the file; arbitrary code directly under `Describe` | v4 → [v4-to-v5](references\u002Fv4-to-v5.md) |\n| `Assert-MockCalled`, `Assert-VerifiableMock`, `Set-ItResult -Pending` | v4 \u002F early-v5 (these are **removed in v6**) |\n| `Invoke-Pester -Script … -OutputFile … -CodeCoverage …` (legacy params) | v4 invocation → map to config |\n| `BeforeAll { . $PSScriptRoot\u002F… }`, `New-PesterConfiguration`, `Should -Invoke` | already v5-style → [v5-to-v6](references\u002Fv5-to-v6.md) |\n\nInstall the target version when ready:\n\n```powershell\n# Latest stable v5 — pin the major to avoid installing Pester 6\nInstall-Module Pester -MaximumVersion 5.99.99 -Force\n\n# Pester 6\nInstall-Module Pester -Force\n```\n\n> On **Windows PowerShell 5.1** the OS ships a Microsoft-signed built-in Pester 3 that PowerShellGet\n> won't overwrite with the differently-signed newer Pester — add `-SkipPublisherCheck` there to\n> install side-by-side. Not needed on PowerShell 7+. See\n> https:\u002F\u002Fpester.dev\u002Fdocs\u002Fintroduction\u002Finstallation.\n\n## Migration workflow\n\nRun this loop for each major jump. **Do not jump two majors at once** — go v4→v5, then v5→v6.\n\n1. **Baseline.** Run the suite on the **current** version first and record pass\u002Ffail. You need a\n   known-good (or known) starting point so you can tell migration regressions apart from\n   pre-existing failures.\n   ```powershell\n   # Bare Invoke-Pester works on every major; exact parameters differ\n   # (v3\u002Fv4: -Script\u002F-OutputFile; v5+\u002Fv6: -Path\u002F-Output).\n   Invoke-Pester\n   ```\n2. **Read the reference** for this jump (table above) so you know the full scope before editing.\n3. **Edit file by file.** Apply the mechanical changes (see per-jump cheat sheets below and in the\n   reference). Keep changes small and reviewable — one file or one concern at a time.\n4. **Switch versions** with `Install-Module` (Step 0), then re-import: `Remove-Module Pester;\n   Import-Module Pester` (or start a fresh session).\n5. **Run and fix.** Re-run with `-Output Detailed`; use `-Output Diagnostic` (v4→v5) or read the\n   explicit v6 error messages to locate problems. Match each failure to the **symptom → fix**\n   tables in the reference.\n6. **Green, diff, commit.** Re-run until the result matches the baseline (or better). Review the\n   diff, then commit. Migrating in small commits makes regressions trivial to bisect.\n\n## What actually changes (scope per jump)\n\n| Jump | Difficulty | Nature |\n|---|---|---|\n| v3 → v4 | Low | Assertion-syntax rename (`Should -Be`). Largely script-automatable. |\n| v4 → v5 | **High** | New two-phase runtime. Test **structure** changes: setup must move into `BeforeAll`, discovery-time code into `BeforeDiscovery`, file location via `$PSScriptRoot`. Not a pure find-replace. |\n| v5 → v6 | Low–Medium | Backwards-compatible runtime; deprecated features now throw. Mostly small, targeted fixes. Your `Should -Be` assertions keep working unchanged. |\n\n## Quick cheat sheets\n\n### v4 → v5 (most common fixes)\n```powershell\n# 1. Move file import into BeforeAll, use $PSScriptRoot (NOT $MyInvocation.MyCommand.Path)\n# BEFORE\n$here = Split-Path -Parent $MyInvocation.MyCommand.Path\n. \"$here\\Get-Thing.ps1\"\n# AFTER\nBeforeAll { . $PSScriptRoot\u002FGet-Thing.ps1 }\n\n# 2. Any code that DISCOVERS\u002Fgenerates tests must be in BeforeDiscovery\nBeforeDiscovery { $cases = Get-Content $PSScriptRoot\u002Fcases.json | ConvertFrom-Json }\n\n# 3. Should -Throw matches with -like wildcards, not .Contains\n{ throw 'a long message' } | Should -Throw '*long*'\n\n# 4. Invoke-Pester legacy params → New-PesterConfiguration (see reference for full map)\n```\nFull details, scoping rules, and the parameter→config table: [references\u002Fv4-to-v5.md](references\u002Fv4-to-v5.md).\n\n### v5 → v6 (most common fixes)\n```powershell\n# 1. Mock assertions: removed verbs — rename (old -> new):\n#    Assert-MockCalled     -> Should -Invoke\n#    Assert-VerifiableMock -> Should -InvokeVerifiable\nShould -Invoke Get-Thing -Times 1 -Exactly\nShould -InvokeVerifiable\n\n# 2. Add a default mock — unmatched calls no longer run the real command\nMock Get-Thing { 'default' }\nMock Get-Thing -ParameterFilter { $Name -eq 'a' } -MockWith { 'a' }\n\n# 3. Empty\u002F$null -ForEach now throws; allow it only where empty is expected\nDescribe 'Optional' -ForEach $cases -AllowNullOrEmptyForEach { }\n\n# 4. Combine duplicate BeforeAll\u002FBeforeEach\u002FAfterAll\u002FAfterEach in the same block into one\n```\nFull breaking-change list with symptoms and fixes: [references\u002Fv5-to-v6.md](references\u002Fv5-to-v6.md).\n\n## Safety rules\n\n- **Tests are the spec.** Migration must not change what a test asserts — only how the suite is\n  structured and invoked. If a test starts passing\u002Ffailing differently for any reason other than a\n  documented breaking change, investigate before accepting it.\n- **Automated migration scripts produce false positives.** The community scripts (linked in the\n  references) help with `Should` syntax and dot-sourcing, but always review the diff and re-run the\n  suite afterward. Never bulk-edit and commit unchecked.\n- **Mind file encoding** when scripting replacements over `*.Tests.ps1` — preserve the original\n  encoding (UTF-8 vs ASCII) so you don't mangle non-ASCII test names.\n- **Work on a branch, commit per file\u002Fconcern.** Small commits keep `git bisect` useful if a\n  migrated test goes red later.\n","# Pester Migration\n\nPester is the test framework for PowerShell. Test files end in `*.Tests.ps1` and use\n`Describe` \u002F `Context` \u002F `It` blocks with `Should` assertions. This skill upgrades an existing\nsuite from one major Pester version to the next and gets it green again.\n\n> **Mental model:** each major jump has a different character. **v3→v4** is mostly a syntax\n> rename. **v4→v5** is a *fundamental runtime change* (the Discovery\u002FRun split) and is the hard\n> one. **v5→v6** is largely backwards-compatible — a handful of previously-deprecated things now\n> throw. Migrate **one major at a time**; never skip a version.\n\nDetailed, symptom-driven guides live in `references\u002F` — load the one(s) for the jump you are doing.\n\n## References\n\n| Reference | When to load |\n|---|---|\n| [v3-to-v4.md](references\u002Fv3-to-v4.md) | `Should Be` → `Should -Be`, `Contain` → `FileContentMatch`, `Assert-VerifiableMocks` → `Assert-VerifiableMock`, array-assertion edge cases. |\n| [v4-to-v5.md](references\u002Fv4-to-v5.md) | The big one. Discovery\u002FRun phases, `BeforeAll` setup, `$PSScriptRoot`, `BeforeDiscovery`, `-ForEach`, mock scoping, `Should -Throw` wildcards, `Invoke-Pester` → `New-PesterConfiguration`. |\n| [v5-to-v6.md](references\u002Fv5-to-v6.md) | PowerShell 5.1\u002F7.4+ only, per-file discovery+run, empty `-ForEach` throws, duplicate setup blocks throw, name `\u003C...>` templates evaluate, `Assert-MockCalled` removed, mocks no longer fall through, code-coverage tracer, legacy `Invoke-Pester` params removed. |\n\nCanonical source: the official migration guides at https:\u002F\u002Fpester.dev\u002Fdocs\u002Fmigrations\u002F — this skill\nmirrors them. When in doubt, prefer the website.\n\n## Step 0 — Detect where you are and where you're going\n\nFind the installed version(s) and the version the **tests** were written for. These can differ.\n\n```powershell\n# Installed Pester version(s) on this machine\nGet-Module Pester -ListAvailable | Select-Object Name, Version, Path\n\n# Version currently imported in the session\n(Get-Module Pester).Version\n```\n\nTell the source version from the **test code** with these heuristics:\n\n| You see in `*.Tests.ps1` \u002F build scripts | Suite was written for |\n|---|---|\n| `Should Be` \u002F `Should Contain` (no dash) | v3 or earlier → start at [v3-to-v4](references\u002Fv3-to-v4.md) |\n| `$MyInvocation.MyCommand.Path` + dot-source at the **top** of the file; arbitrary code directly under `Describe` | v4 → [v4-to-v5](references\u002Fv4-to-v5.md) |\n| `Assert-MockCalled`, `Assert-VerifiableMock`, `Set-ItResult -Pending` | v4 \u002F early-v5 (these are **removed in v6**) |\n| `Invoke-Pester -Script … -OutputFile … -CodeCoverage …` (legacy params) | v4 invocation → map to config |\n| `BeforeAll { . $PSScriptRoot\u002F… }`, `New-PesterConfiguration`, `Should -Invoke` | already v5-style → [v5-to-v6](references\u002Fv5-to-v6.md) |\n\nInstall the target version when ready:\n\n```powershell\n# Latest stable v5 — pin the major to avoid installing Pester 6\nInstall-Module Pester -MaximumVersion 5.99.99 -Force\n\n# Pester 6\nInstall-Module Pester -Force\n```\n\n> On **Windows PowerShell 5.1** the OS ships a Microsoft-signed built-in Pester 3 that PowerShellGet\n> won't overwrite with the differently-signed newer Pester — add `-SkipPublisherCheck` there to\n> install side-by-side. Not needed on PowerShell 7+. See\n> https:\u002F\u002Fpester.dev\u002Fdocs\u002Fintroduction\u002Finstallation.\n\n## Migration workflow\n\nRun this loop for each major jump. **Do not jump two majors at once** — go v4→v5, then v5→v6.\n\n1. **Baseline.** Run the suite on the **current** version first and record pass\u002Ffail. You need a\n   known-good (or known) starting point so you can tell migration regressions apart from\n   pre-existing failures.\n   ```powershell\n   # Bare Invoke-Pester works on every major; exact parameters differ\n   # (v3\u002Fv4: -Script\u002F-OutputFile; v5+\u002Fv6: -Path\u002F-Output).\n   Invoke-Pester\n   ```\n2. **Read the reference** for this jump (table above) so you know the full scope before editing.\n3. **Edit file by file.** Apply the mechanical changes (see per-jump cheat sheets below and in the\n   reference). Keep changes small and reviewable — one file or one concern at a time.\n4. **Switch versions** with `Install-Module` (Step 0), then re-import: `Remove-Module Pester;\n   Import-Module Pester` (or start a fresh session).\n5. **Run and fix.** Re-run with `-Output Detailed`; use `-Output Diagnostic` (v4→v5) or read the\n   explicit v6 error messages to locate problems. Match each failure to the **symptom → fix**\n   tables in the reference.\n6. **Green, diff, commit.** Re-run until the result matches the baseline (or better). Review the\n   diff, then commit. Migrating in small commits makes regressions trivial to bisect.\n\n## What actually changes (scope per jump)\n\n| Jump | Difficulty | Nature |\n|---|---|---|\n| v3 → v4 | Low | Assertion-syntax rename (`Should -Be`). Largely script-automatable. |\n| v4 → v5 | **High** | New two-phase runtime. Test **structure** changes: setup must move into `BeforeAll`, discovery-time code into `BeforeDiscovery`, file location via `$PSScriptRoot`. Not a pure find-replace. |\n| v5 → v6 | Low–Medium | Backwards-compatible runtime; deprecated features now throw. Mostly small, targeted fixes. Your `Should -Be` assertions keep working unchanged. |\n\n## Quick cheat sheets\n\n### v4 → v5 (most common fixes)\n```powershell\n# 1. Move file import into BeforeAll, use $PSScriptRoot (NOT $MyInvocation.MyCommand.Path)\n# BEFORE\n$here = Split-Path -Parent $MyInvocation.MyCommand.Path\n. \"$here\\Get-Thing.ps1\"\n# AFTER\nBeforeAll { . $PSScriptRoot\u002FGet-Thing.ps1 }\n\n# 2. Any code that DISCOVERS\u002Fgenerates tests must be in BeforeDiscovery\nBeforeDiscovery { $cases = Get-Content $PSScriptRoot\u002Fcases.json | ConvertFrom-Json }\n\n# 3. Should -Throw matches with -like wildcards, not .Contains\n{ throw 'a long message' } | Should -Throw '*long*'\n\n# 4. Invoke-Pester legacy params → New-PesterConfiguration (see reference for full map)\n```\nFull details, scoping rules, and the parameter→config table: [references\u002Fv4-to-v5.md](references\u002Fv4-to-v5.md).\n\n### v5 → v6 (most common fixes)\n```powershell\n# 1. Mock assertions: removed verbs — rename (old -> new):\n#    Assert-MockCalled     -> Should -Invoke\n#    Assert-VerifiableMock -> Should -InvokeVerifiable\nShould -Invoke Get-Thing -Times 1 -Exactly\nShould -InvokeVerifiable\n\n# 2. Add a default mock — unmatched calls no longer run the real command\nMock Get-Thing { 'default' }\nMock Get-Thing -ParameterFilter { $Name -eq 'a' } -MockWith { 'a' }\n\n# 3. Empty\u002F$null -ForEach now throws; allow it only where empty is expected\nDescribe 'Optional' -ForEach $cases -AllowNullOrEmptyForEach { }\n\n# 4. Combine duplicate BeforeAll\u002FBeforeEach\u002FAfterAll\u002FAfterEach in the same block into one\n```\nFull breaking-change list with symptoms and fixes: [references\u002Fv5-to-v6.md](references\u002Fv5-to-v6.md).\n\n## Safety rules\n\n- **Tests are the spec.** Migration must not change what a test asserts — only how the suite is\n  structured and invoked. If a test starts passing\u002Ffailing differently for any reason other than a\n  documented breaking change, investigate before accepting it.\n- **Automated migration scripts produce false positives.** The community scripts (linked in the\n  references) help with `Should` syntax and dot-sourcing, but always review the diff and re-run the\n  suite afterward. Never bulk-edit and commit unchecked.\n- **Mind file encoding** when scripting replacements over `*.Tests.ps1` — preserve the original\n  encoding (UTF-8 vs ASCII) so you don't mangle non-ASCII test names.\n- **Work on a branch, commit per file\u002Fconcern.** Small commits keep `git bisect` useful if a\n  migrated test goes red later.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fpester-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-migration",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill pester-migration",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill pester-migration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpester-migration\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fv3-to-v4.md","REFERENCE","参考文档",3766,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpester-migration\u002Freferences\u002Fv3-to-v4.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fv4-to-v5.md",11342,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpester-migration\u002Freferences\u002Fv4-to-v5.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fv5-to-v6.md",10519,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpester-migration\u002Freferences\u002Fv5-to-v6.md",[61,68,75,82,89,96],{"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},"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":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},"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":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},"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":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},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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",[],[]]