[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77TP7AV68WCQHTKN6707CVV":3,"skill-same:01M77TP7AV68WCQHTKN6707CVV":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},"01M77TP7AV68WCQHTKN6707CVV","migrating-oracle-to-postgres-stored-procedures",null,"Migrates Oracle PL\u002FSQL stored procedures to PostgreSQL PL\u002FpgSQL. Translates Oracle-specific syntax, preserves method signatures and type-anchored parameters, leverages orafce where appropriate, and applies explicit collation mapping (`COLLATE \"C\"` only when appropriate, locale collations when required). Use when converting Oracle stored procedures or functions to PostgreSQL equivalents during a 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-stored-procedures\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Migrates Oracle PL\u002FSQL stored procedures to PostgreSQL PL\u002FpgSQL. Translates Oracle-specific syntax, preserves method signatures and type-anchored parameters, leverages orafce where appropriate, and applies explicit collation mapping (`COLLATE \\\"C\\\"` only when appropriate, locale collations when required). Use when converting Oracle stored procedures or functions to PostgreSQL equivalents during a database migration.\"\n---\n# Migrating Stored Procedures from Oracle to PostgreSQL\n\nTranslate Oracle PL\u002FSQL stored procedures and functions to PostgreSQL PL\u002FpgSQL equivalents.\n\n## Workflow\n\n```\nProgress:\n- [ ] Step 1: Read the Oracle source procedure\n- [ ] Step 2: Translate to PostgreSQL PL\u002FpgSQL\n- [ ] Step 3: Write the migrated procedure to Postgres output directory\n```\n\n**Step 1: Read the Oracle source procedure**\n\nRead the Oracle stored procedure from `.github\u002Foracle-to-postgres-migration\u002FDDL\u002FOracle\u002FProcedures and Functions\u002F`. Consult the Oracle table\u002Fview definitions at `.github\u002Foracle-to-postgres-migration\u002FDDL\u002FOracle\u002FTables and Views\u002F` for type resolution.\n\n**Step 2: Translate to PostgreSQL PL\u002FpgSQL**\n\nApply these translation rules:\n\n- Translate all Oracle-specific syntax to PostgreSQL equivalents.\n- Preserve original functionality and control flow logic.\n- Keep type-anchored input parameters (e.g., `PARAM_NAME IN table_name.column_name%TYPE`).\n- Use explicit types (`NUMERIC`, `VARCHAR`, `INTEGER`) for output parameters passed to other procedures — do not type-anchor these.\n- Do not alter method signatures.\n- Do not prefix object names with schema names unless already present in the Oracle source.\n- Leave exception handling and rollback logic unchanged.\n- Do not generate `COMMENT` or `GRANT` statements.\n- Apply collation intentionally when ordering text:\n  - Use `COLLATE \"C\"` only when Oracle-compatible binary ordering is required and no other sort order is specified.\n  - If Oracle used explicit linguistic sorting (for example `NLS_SORT = French`), map to an explicit PostgreSQL locale collation instead of `\"C\"`.\n  - Use `SELECT collname, collprovider, collcollate, collctype FROM pg_collation ORDER BY collname;` to discover collations in the target environment.\n- Treat `UNION ALL` as a review checkpoint. Validate plan quality per branch and restructure if combined-branch planning causes regressions (for example, unexpected sequential scans on large tables).\n- Leverage the `orafce` extension when it improves clarity or fidelity.\n\nConsult the PostgreSQL table\u002Fview definitions at `.github\u002Foracle-to-postgres-migration\u002FDDL\u002FPostgres\u002F{ProjectName}\u002FTables and Views\u002F` for target schema details.\n\n**Step 3: Write the migrated procedure to Postgres output directory**\n\nPlace each migrated procedure in its own file under `.github\u002Foracle-to-postgres-migration\u002FDDL\u002FPostgres\u002F{ProjectName}\u002FProcedures and Functions\u002F{PACKAGE_NAME_IF_APPLICABLE}\u002F`. One procedure per file.\n\n> `{ProjectName}` is the project's assembly\u002Ffolder name with spaces normalized to `-` (e.g. `MyApp.DataAccess`). This matches the path used by the agent and other migration skills.\n","# Migrating Stored Procedures from Oracle to PostgreSQL\n\nTranslate Oracle PL\u002FSQL stored procedures and functions to PostgreSQL PL\u002FpgSQL equivalents.\n\n## Workflow\n\n```\nProgress:\n- [ ] Step 1: Read the Oracle source procedure\n- [ ] Step 2: Translate to PostgreSQL PL\u002FpgSQL\n- [ ] Step 3: Write the migrated procedure to Postgres output directory\n```\n\n**Step 1: Read the Oracle source procedure**\n\nRead the Oracle stored procedure from `.github\u002Foracle-to-postgres-migration\u002FDDL\u002FOracle\u002FProcedures and Functions\u002F`. Consult the Oracle table\u002Fview definitions at `.github\u002Foracle-to-postgres-migration\u002FDDL\u002FOracle\u002FTables and Views\u002F` for type resolution.\n\n**Step 2: Translate to PostgreSQL PL\u002FpgSQL**\n\nApply these translation rules:\n\n- Translate all Oracle-specific syntax to PostgreSQL equivalents.\n- Preserve original functionality and control flow logic.\n- Keep type-anchored input parameters (e.g., `PARAM_NAME IN table_name.column_name%TYPE`).\n- Use explicit types (`NUMERIC`, `VARCHAR`, `INTEGER`) for output parameters passed to other procedures — do not type-anchor these.\n- Do not alter method signatures.\n- Do not prefix object names with schema names unless already present in the Oracle source.\n- Leave exception handling and rollback logic unchanged.\n- Do not generate `COMMENT` or `GRANT` statements.\n- Apply collation intentionally when ordering text:\n  - Use `COLLATE \"C\"` only when Oracle-compatible binary ordering is required and no other sort order is specified.\n  - If Oracle used explicit linguistic sorting (for example `NLS_SORT = French`), map to an explicit PostgreSQL locale collation instead of `\"C\"`.\n  - Use `SELECT collname, collprovider, collcollate, collctype FROM pg_collation ORDER BY collname;` to discover collations in the target environment.\n- Treat `UNION ALL` as a review checkpoint. Validate plan quality per branch and restructure if combined-branch planning causes regressions (for example, unexpected sequential scans on large tables).\n- Leverage the `orafce` extension when it improves clarity or fidelity.\n\nConsult the PostgreSQL table\u002Fview definitions at `.github\u002Foracle-to-postgres-migration\u002FDDL\u002FPostgres\u002F{ProjectName}\u002FTables and Views\u002F` for target schema details.\n\n**Step 3: Write the migrated procedure to Postgres output directory**\n\nPlace each migrated procedure in its own file under `.github\u002Foracle-to-postgres-migration\u002FDDL\u002FPostgres\u002F{ProjectName}\u002FProcedures and Functions\u002F{PACKAGE_NAME_IF_APPLICABLE}\u002F`. One procedure per file.\n\n> `{ProjectName}` is the project's assembly\u002Ffolder name with spaces normalized to `-` (e.g. `MyApp.DataAccess`). This matches the path used by the agent and other migration skills.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fmigrating-oracle-to-postgres-stored-procedures",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-stored-procedures",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill migrating-oracle-to-postgres-stored-procedures",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill migrating-oracle-to-postgres-stored-procedures","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fmigrating-oracle-to-postgres-stored-procedures\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",[],[]]