[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77TP3EPK4SZXWW7CWVFQD2F":3,"skill-same:01M77TP3EPK4SZXWW7CWVFQD2F":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},"01M77TP3EPK4SZXWW7CWVFQD2F","migrating-oracle-to-postgres-data-access-code",null,"Migrates .NET\u002FC# data access code from Oracle to PostgreSQL (Npgsql). Replaces Oracle NuGet packages, rewrites OracleConnection\u002FOracleCommand\u002FOracleDataReader usage, fixes DbType mappings, updates stored procedure invocation patterns, and adapts connection string configuration. Use when migrating the application code layer of a .NET project during an Oracle-to-PostgreSQL database migration.","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\u002Fmigrating-oracle-to-postgres-data-access-code\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Migrates .NET\u002FC# data access code from Oracle to PostgreSQL (Npgsql). Replaces Oracle NuGet packages, rewrites OracleConnection\u002FOracleCommand\u002FOracleDataReader usage, fixes DbType mappings, updates stored procedure invocation patterns, and adapts connection string configuration. Use when migrating the application code layer of a .NET project during an Oracle-to-PostgreSQL database migration.\"\n---\n# Migrating .NET Data Access Code from Oracle to PostgreSQL\n\nMigrate the C# data access layer of a single `.Postgres`-copy project from Oracle (Oracle.ManagedDataAccess) to PostgreSQL (Npgsql). Work item by item through `Reports\u002F{ProjectName}\u002FMigrationChecklist.md`.\n\n## Prerequisites\n\n- The `.Postgres` project copy exists (created in Phase 5 setup).\n- `Reports\u002F{ProjectName}\u002FMigrationChecklist.md` exists and is the source of truth for what to change.\n- `Reports\u002F{ProjectName}\u002FOracleRiskAnalysis.md` exists for cross-referencing behavioral differences.\n\n## Workflow\n\n```\nProgress:\n- [ ] Step 1: Replace NuGet packages\n- [ ] Step 2: Update connection string configuration\n- [ ] Step 3: Rewrite ADO.NET type references\n- [ ] Step 4: Fix DbType mappings\n- [ ] Step 5: Migrate stored procedure invocation\n- [ ] Step 6: Address Oracle-specific SQL and syntax\n- [ ] Step 7: Build and verify\n```\n\n**Step 1: Replace NuGet packages**\n\nIn the `.csproj` of the `.Postgres` project:\n\n- Remove: `Oracle.ManagedDataAccess.Core`, `Oracle.EntityFrameworkCore` (and any other `Oracle.*` packages)\n- Add: `Npgsql` (for ADO.NET) and\u002For `Npgsql.EntityFrameworkCore.PostgreSQL` (for EF Core)\n- Keep version pinning consistent with the target .NET version; do not introduce newer package versions than what the solution already uses for similar packages.\n- If `System.Data` abstractions (`IDbConnection`, `IDbCommand`) are used project-wide, the surface-level code may need fewer changes — identify them first.\n\n**Step 2: Update connection string configuration**\n\n- Locate the Oracle connection string in `appsettings.json`, `appsettings.{env}.json`, `web.config`, `app.config`, or environment variable configuration.\n- Replace with a Npgsql-compatible connection string: `Host=localhost;Port=5432;Database=mydb;Username=myuser;Password=mypassword`\n- Do not hardcode credentials — use the same configuration mechanism already in use (e.g., environment variables, secrets manager, `IConfiguration`).\n- Update any named connection string keys only if they were Oracle-specific (e.g., `OracleConnection`). Prefer keeping the same key name to minimize application config changes.\n\n**Step 3: Rewrite ADO.NET type references**\n\nReplace Oracle-specific ADO.NET types with Npgsql equivalents:\n\n| Oracle type | Npgsql replacement |\n|---|---|\n| `OracleConnection` | `NpgsqlConnection` |\n| `OracleCommand` | `NpgsqlCommand` |\n| `OracleDataReader` | `NpgsqlDataReader` |\n| `OracleDataAdapter` | `NpgsqlDataAdapter` |\n| `OracleParameter` | `NpgsqlParameter` |\n| `OracleTransaction` | `NpgsqlTransaction` |\n| `OracleException` | `NpgsqlException` |\n| `OracleDbType` | `NpgsqlDbType` (from `NpgsqlTypes` namespace) |\n\nUpdate `using` directives accordingly (`using Oracle.ManagedDataAccess.Client` → `using Npgsql`).\n\nIf the codebase uses `IDbConnection`\u002F`IDbCommand` abstractions registered via DI, update only the DI registration and connection string — the consuming code may not need changes.\n\n**Step 4: Fix DbType and NpgsqlDbType mappings**\n\nOracle parameter types do not map 1:1 to Npgsql. Review every `OracleParameter` (now `NpgsqlParameter`) that sets an explicit type:\n\n| Oracle type | Notes |\n|---|---|\n| `OracleDbType.Varchar2` | Use `NpgsqlDbType.Varchar` or omit (Npgsql infers from value) |\n| `OracleDbType.Clob` | Use `NpgsqlDbType.Text` |\n| `OracleDbType.Number` | Use `NpgsqlDbType.Numeric` or `NpgsqlDbType.Integer` depending on precision |\n| `OracleDbType.Date` | Use `NpgsqlDbType.Date` (date only) or `NpgsqlDbType.Timestamp` (if time component used) |\n| `OracleDbType.TimeStamp` | Use `NpgsqlDbType.Timestamp` |\n| `OracleDbType.RefCursor` | Use `NpgsqlDbType.Refcursor` — see Step 5 |\n| `OracleDbType.Char` | Use `NpgsqlDbType.Char` |\n\nFor parameters where Oracle inferred the type from the value, Npgsql also infers — explicit type setting is often unnecessary and can be removed.\n\n**Step 5: Migrate stored procedure invocation**\n\nOracle and PostgreSQL stored procedure invocation differ significantly:\n\n- **Command type**: Retain `CommandType.StoredProcedure` for function calls. For procedures that use `OUT` parameters, PostgreSQL requires `CommandType.Text` with `CALL proc_name(...)` syntax in some versions of Npgsql — verify against the target Npgsql version.\n- **RefCursor handling**: Oracle returns ref cursors as output parameters; PostgreSQL returns them differently:\n  - For `RETURNS TABLE` \u002F `RETURNS SETOF`, use `ExecuteReader()` directly — no cursor parameter needed.\n  - For `RETURNS refcursor`, call within a transaction, read the cursor name from the output parameter, then issue `FETCH ALL IN \"\u003Ccursor_name>\"`.\n  - Remove any Oracle-specific cursor-wrapping code (e.g., `OracleRefCursor`).\n- **OUT parameters**: PostgreSQL stored procedures use `INOUT` or function return values. Verify parameter direction matches the migrated procedure signature.\n- **Sequence `NEXTVAL`**: Replace `SELECT {SEQUENCE}.NEXTVAL FROM DUAL` with `SELECT nextval('{sequence_name}')`.\n- **Named parameters**: Npgsql uses `@param_name`; Oracle used `:param_name`. Update all parameter name prefixes.\n\n**Step 6: Address Oracle-specific SQL and C# patterns**\n\nReview inline SQL strings and query builders for Oracle-specific constructs and replace:\n\n| Oracle construct | PostgreSQL replacement |\n|---|---|\n| `ROWNUM \u003C= n` | `LIMIT n` |\n| `ROWNUM = 1` | `LIMIT 1` |\n| `NVL(x, y)` | `COALESCE(x, y)` |\n| `DECODE(expr, v1, r1, ...)` | `CASE WHEN expr = v1 THEN r1 ... END` |\n| `SYSDATE` \u002F `SYSTIMESTAMP` | `NOW()` or `CURRENT_TIMESTAMP` |\n| `TO_CHAR(date, fmt)` | `TO_CHAR(date, fmt)` (mostly compatible; verify format strings) |\n| `TO_DATE(str, fmt)` | `TO_DATE(str, fmt)` (verify format strings) |\n| `TO_NUMBER(str)` | `CAST(str AS NUMERIC)` or `str::NUMERIC` |\n| `||` string concat | `||` (compatible) |\n| `DUAL` table | Remove `FROM DUAL`; PostgreSQL evaluates `SELECT expr` without a table |\n| `CONNECT BY` hierarchy | Rewrite using recursive CTEs (`WITH RECURSIVE`) |\n| `MERGE INTO` | Rewrite as `INSERT ... ON CONFLICT DO UPDATE` |\n| Empty string `''` as NULL | Oracle treats `''` as NULL; PostgreSQL does not — check comparisons and `IS NULL` guards |\n| `VARCHAR2` | `VARCHAR` or `TEXT` |\n\n**Step 7: Build and verify**\n\nAfter addressing all checklist items:\n\n1. Run `dotnet build` on the `.Postgres` project. Fix any remaining compilation errors.\n2. Verify no Oracle-specific namespaces remain: search for `Oracle.ManagedDataAccess`, `OracleConnection`, `OracleCommand`, `:param` patterns.\n3. Mark completed items in `Reports\u002F{ProjectName}\u002FMigrationChecklist.md`.\n\n## EF Core projects\n\nIf the project uses `Oracle.EntityFrameworkCore`:\n\n- Replace the provider registration in `DbContext` configuration: `.UseOracle(...)` → `.UseNpgsql(...)`\n- Replace `OracleDbContextOptionsBuilder` references.\n- Review `OnModelCreating` for Oracle-specific configurations (e.g., `HasColumnType(\"NUMBER\")` → `HasColumnType(\"numeric\")`).\n- Sequence configuration: `modelBuilder.HasSequence\u003Cint>(\"seq_name\").StartsAt(1).IncrementsBy(1)` syntax is compatible; verify column defaults referencing sequences.\n- Do not run EF Core migrations — schema is managed externally via DDL scripts (Phase 4).\n\n## Key Constraints\n\n- Work only within the `.Postgres` copy — never modify the original Oracle-targeting project.\n- Keep to existing .NET and C# versions; do not introduce newer language or runtime features.\n- Preserve comments and application logic; change only what is necessary for PostgreSQL compatibility.\n- Oracle is the source of truth — behavioral differences must be documented as bug reports, not silently altered.\n","# Migrating .NET Data Access Code from Oracle to PostgreSQL\n\nMigrate the C# data access layer of a single `.Postgres`-copy project from Oracle (Oracle.ManagedDataAccess) to PostgreSQL (Npgsql). Work item by item through `Reports\u002F{ProjectName}\u002FMigrationChecklist.md`.\n\n## Prerequisites\n\n- The `.Postgres` project copy exists (created in Phase 5 setup).\n- `Reports\u002F{ProjectName}\u002FMigrationChecklist.md` exists and is the source of truth for what to change.\n- `Reports\u002F{ProjectName}\u002FOracleRiskAnalysis.md` exists for cross-referencing behavioral differences.\n\n## Workflow\n\n```\nProgress:\n- [ ] Step 1: Replace NuGet packages\n- [ ] Step 2: Update connection string configuration\n- [ ] Step 3: Rewrite ADO.NET type references\n- [ ] Step 4: Fix DbType mappings\n- [ ] Step 5: Migrate stored procedure invocation\n- [ ] Step 6: Address Oracle-specific SQL and syntax\n- [ ] Step 7: Build and verify\n```\n\n**Step 1: Replace NuGet packages**\n\nIn the `.csproj` of the `.Postgres` project:\n\n- Remove: `Oracle.ManagedDataAccess.Core`, `Oracle.EntityFrameworkCore` (and any other `Oracle.*` packages)\n- Add: `Npgsql` (for ADO.NET) and\u002For `Npgsql.EntityFrameworkCore.PostgreSQL` (for EF Core)\n- Keep version pinning consistent with the target .NET version; do not introduce newer package versions than what the solution already uses for similar packages.\n- If `System.Data` abstractions (`IDbConnection`, `IDbCommand`) are used project-wide, the surface-level code may need fewer changes — identify them first.\n\n**Step 2: Update connection string configuration**\n\n- Locate the Oracle connection string in `appsettings.json`, `appsettings.{env}.json`, `web.config`, `app.config`, or environment variable configuration.\n- Replace with a Npgsql-compatible connection string: `Host=localhost;Port=5432;Database=mydb;Username=myuser;Password=mypassword`\n- Do not hardcode credentials — use the same configuration mechanism already in use (e.g., environment variables, secrets manager, `IConfiguration`).\n- Update any named connection string keys only if they were Oracle-specific (e.g., `OracleConnection`). Prefer keeping the same key name to minimize application config changes.\n\n**Step 3: Rewrite ADO.NET type references**\n\nReplace Oracle-specific ADO.NET types with Npgsql equivalents:\n\n| Oracle type | Npgsql replacement |\n|---|---|\n| `OracleConnection` | `NpgsqlConnection` |\n| `OracleCommand` | `NpgsqlCommand` |\n| `OracleDataReader` | `NpgsqlDataReader` |\n| `OracleDataAdapter` | `NpgsqlDataAdapter` |\n| `OracleParameter` | `NpgsqlParameter` |\n| `OracleTransaction` | `NpgsqlTransaction` |\n| `OracleException` | `NpgsqlException` |\n| `OracleDbType` | `NpgsqlDbType` (from `NpgsqlTypes` namespace) |\n\nUpdate `using` directives accordingly (`using Oracle.ManagedDataAccess.Client` → `using Npgsql`).\n\nIf the codebase uses `IDbConnection`\u002F`IDbCommand` abstractions registered via DI, update only the DI registration and connection string — the consuming code may not need changes.\n\n**Step 4: Fix DbType and NpgsqlDbType mappings**\n\nOracle parameter types do not map 1:1 to Npgsql. Review every `OracleParameter` (now `NpgsqlParameter`) that sets an explicit type:\n\n| Oracle type | Notes |\n|---|---|\n| `OracleDbType.Varchar2` | Use `NpgsqlDbType.Varchar` or omit (Npgsql infers from value) |\n| `OracleDbType.Clob` | Use `NpgsqlDbType.Text` |\n| `OracleDbType.Number` | Use `NpgsqlDbType.Numeric` or `NpgsqlDbType.Integer` depending on precision |\n| `OracleDbType.Date` | Use `NpgsqlDbType.Date` (date only) or `NpgsqlDbType.Timestamp` (if time component used) |\n| `OracleDbType.TimeStamp` | Use `NpgsqlDbType.Timestamp` |\n| `OracleDbType.RefCursor` | Use `NpgsqlDbType.Refcursor` — see Step 5 |\n| `OracleDbType.Char` | Use `NpgsqlDbType.Char` |\n\nFor parameters where Oracle inferred the type from the value, Npgsql also infers — explicit type setting is often unnecessary and can be removed.\n\n**Step 5: Migrate stored procedure invocation**\n\nOracle and PostgreSQL stored procedure invocation differ significantly:\n\n- **Command type**: Retain `CommandType.StoredProcedure` for function calls. For procedures that use `OUT` parameters, PostgreSQL requires `CommandType.Text` with `CALL proc_name(...)` syntax in some versions of Npgsql — verify against the target Npgsql version.\n- **RefCursor handling**: Oracle returns ref cursors as output parameters; PostgreSQL returns them differently:\n  - For `RETURNS TABLE` \u002F `RETURNS SETOF`, use `ExecuteReader()` directly — no cursor parameter needed.\n  - For `RETURNS refcursor`, call within a transaction, read the cursor name from the output parameter, then issue `FETCH ALL IN \"\u003Ccursor_name>\"`.\n  - Remove any Oracle-specific cursor-wrapping code (e.g., `OracleRefCursor`).\n- **OUT parameters**: PostgreSQL stored procedures use `INOUT` or function return values. Verify parameter direction matches the migrated procedure signature.\n- **Sequence `NEXTVAL`**: Replace `SELECT {SEQUENCE}.NEXTVAL FROM DUAL` with `SELECT nextval('{sequence_name}')`.\n- **Named parameters**: Npgsql uses `@param_name`; Oracle used `:param_name`. Update all parameter name prefixes.\n\n**Step 6: Address Oracle-specific SQL and C# patterns**\n\nReview inline SQL strings and query builders for Oracle-specific constructs and replace:\n\n| Oracle construct | PostgreSQL replacement |\n|---|---|\n| `ROWNUM \u003C= n` | `LIMIT n` |\n| `ROWNUM = 1` | `LIMIT 1` |\n| `NVL(x, y)` | `COALESCE(x, y)` |\n| `DECODE(expr, v1, r1, ...)` | `CASE WHEN expr = v1 THEN r1 ... END` |\n| `SYSDATE` \u002F `SYSTIMESTAMP` | `NOW()` or `CURRENT_TIMESTAMP` |\n| `TO_CHAR(date, fmt)` | `TO_CHAR(date, fmt)` (mostly compatible; verify format strings) |\n| `TO_DATE(str, fmt)` | `TO_DATE(str, fmt)` (verify format strings) |\n| `TO_NUMBER(str)` | `CAST(str AS NUMERIC)` or `str::NUMERIC` |\n| `||` string concat | `||` (compatible) |\n| `DUAL` table | Remove `FROM DUAL`; PostgreSQL evaluates `SELECT expr` without a table |\n| `CONNECT BY` hierarchy | Rewrite using recursive CTEs (`WITH RECURSIVE`) |\n| `MERGE INTO` | Rewrite as `INSERT ... ON CONFLICT DO UPDATE` |\n| Empty string `''` as NULL | Oracle treats `''` as NULL; PostgreSQL does not — check comparisons and `IS NULL` guards |\n| `VARCHAR2` | `VARCHAR` or `TEXT` |\n\n**Step 7: Build and verify**\n\nAfter addressing all checklist items:\n\n1. Run `dotnet build` on the `.Postgres` project. Fix any remaining compilation errors.\n2. Verify no Oracle-specific namespaces remain: search for `Oracle.ManagedDataAccess`, `OracleConnection`, `OracleCommand`, `:param` patterns.\n3. Mark completed items in `Reports\u002F{ProjectName}\u002FMigrationChecklist.md`.\n\n## EF Core projects\n\nIf the project uses `Oracle.EntityFrameworkCore`:\n\n- Replace the provider registration in `DbContext` configuration: `.UseOracle(...)` → `.UseNpgsql(...)`\n- Replace `OracleDbContextOptionsBuilder` references.\n- Review `OnModelCreating` for Oracle-specific configurations (e.g., `HasColumnType(\"NUMBER\")` → `HasColumnType(\"numeric\")`).\n- Sequence configuration: `modelBuilder.HasSequence\u003Cint>(\"seq_name\").StartsAt(1).IncrementsBy(1)` syntax is compatible; verify column defaults referencing sequences.\n- Do not run EF Core migrations — schema is managed externally via DDL scripts (Phase 4).\n\n## Key Constraints\n\n- Work only within the `.Postgres` copy — never modify the original Oracle-targeting project.\n- Keep to existing .NET and C# versions; do not introduce newer language or runtime features.\n- Preserve comments and application logic; change only what is necessary for PostgreSQL compatibility.\n- Oracle is the source of truth — behavioral differences must be documented as bug reports, not silently altered.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fmigrating-oracle-to-postgres-data-access-code",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 migrating-oracle-to-postgres-data-access-code",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill migrating-oracle-to-postgres-data-access-code",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill migrating-oracle-to-postgres-data-access-code","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fmigrating-oracle-to-postgres-data-access-code\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",[],[]]