[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77N0NN6SSWYXAM54ASBQMVR":3,"skill-same:01M77N0NN6SSWYXAM54ASBQMVR":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77N0NN6SSWYXAM54ASBQMVR","neon-postgres",null,"Guides and best practices for working with Lakebase Postgres, the database behind Neon. Covers setup, connection methods and drivers, pooled vs direct connections, branching, schema migrations, autoscaling, scale-to-zero, instant restore, read replicas, connection pooling, IP allow lists, and logical replication. Use when users ask about \"Lakebase Postgres\", \"Neon setup\", \"connect to Neon\", \"Neon project\", \"DATABASE_URL\", \"serverless Postgres\", \"Neon CLI\", \"neon\", \"Neon MCP\", \"Neon Auth\", \"@neondatabase\u002Fserverless\", \"@neondatabase\u002Fneon-js\", \"scale to zero\", \"Neon autoscaling\", \"Neon read replica\", \"Neon connection pooling\", or \"schema migrations\".","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\u002F.agents\u002Fskills\u002Fneon-postgres\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: neon-postgres\ndescription: >-\n  Guides and best practices for working with Lakebase Postgres, the database\n  behind Neon. Covers setup, connection methods and drivers, pooled vs direct\n  connections, branching, schema migrations, autoscaling, scale-to-zero, instant\n  restore, read replicas, connection pooling, IP allow lists, and logical\n  replication.\n  Use when users ask about \"Lakebase Postgres\", \"Neon setup\", \"connect to Neon\",\n  \"Neon project\", \"DATABASE_URL\", \"serverless Postgres\", \"Neon CLI\", \"neon\", \"Neon MCP\",\n  \"Neon Auth\", \"@neondatabase\u002Fserverless\", \"@neondatabase\u002Fneon-js\",\n  \"scale to zero\", \"Neon autoscaling\", \"Neon read replica\",\n  \"Neon connection pooling\", or \"schema migrations\".\nmetadata:\n  parent: neon\n  source: https:\u002F\u002Fgithub.com\u002Fneondatabase\u002Fagent-skills\u002Ftree\u002Fmain\u002Fskills\u002Fneon-postgres\n---\n\n**FIRST**: Use the parent `neon` skill for a Neon overview, getting started with Neon, Neon development best practices, and more.\n\nIf the `neon` skill is not installed, fetch it from https:\u002F\u002Fneon.com\u002Fdocs\u002Fai\u002Fskills\u002Fneon\u002FSKILL.md or install it with:\n\n```bash\nnpx skills add neondatabase\u002Fagent-skills --skill neon\n```\n\n# Lakebase Postgres\n\nLakebase Postgres is the database at the core of Neon. It runs on the lakebase architecture — OLTP built directly on cloud object storage — which decouples storage from compute to offer autoscaling, branching, instant restore, and scale-to-zero. It's fully compatible with Postgres and works with any language, framework, or ORM that supports Postgres.\n\nIt is the same database whether you reach it through Neon or through Databricks; this skill covers the Neon access path.\n\n## Setup Flow\n\n### 1. Select the organization and project\n\nUse the CLI (default) or MCP server to list organizations and projects. Let the user select an existing project or create a new one. Check the `.neon` file for an existing linked project or branch.\n\n### 2. Get the connection string\n\nUse the CLI (default), `neon env pull`, or the MCP server to get the connection string. Store it in `.env` as `DATABASE_URL`. Read the file first before modifying it, to avoid overwriting existing values.\n\n#### When to use pooled vs direct connections\n\n| Use case                                 | Connection type  |\n| ---------------------------------------- | ---------------- |\n| Web applications, serverless functions   | Pooled (-pooler) |\n| Schema migrations                        | Direct           |\n| pg_dump \u002F pg_restore                     | Direct           |\n| Logical replication                      | Direct           |\n| Long-running analytics with temp tables  | Direct           |\n| Admin tasks needing SET or session state | Direct           |\n| LISTEN \u002F NOTIFY                          | Direct           |\n\n### 3. Pick the connection method and driver\n\nAlways pair Neon with an ORM such as **Drizzle** for easy schema management and migrations. Refer to the connection methods guide to pick the correct driver based on how the runtime treats your code: https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fchoose-connection.md.\n\nRecommendations:\n\n- Drizzle as ORM (see https:\u002F\u002Fneon.com\u002Fdocs\u002Fguides\u002Fdrizzle.md)\n- On Vercel, use `node-postgres` (`npm install pg`) with Vercel Fluid compute and `import { attachDatabasePool } from \"@vercel\u002Ffunctions\";`\n- On Cloudflare, use `node-postgres` with Cloudflare Hyperdrive\n- On Neon Functions, use `node-postgres`, as the functions are long-running and reuse the pool across requests.\n- Use the `@neondatabase\u002Fserverless` driver for serverless and edge environments (for example, when using Netlify) — HTTP transport for one-shot queries, WebSocket for transaction support. Link: https:\u002F\u002Fneon.com\u002Fdocs\u002Fserverless\u002Fserverless-driver.md\n\n### 4. Set up the schema\n\nManage schemas and migrations as code. Avoid running ad hoc schema migrations against your database, since they're hard to manage.\n\nIf you're using an ORM, follow your ORM's best practices to manage schemas and migrations. For example, if using Drizzle, only use Drizzle for schema and migration management unless instructed otherwise.\n\n## Branching\n\nUse this when the user is planning isolated environments, schema migration testing, preview deployments, or branch lifecycle automation.\n\nKey points:\n\n- Branches are instant, copy-on-write clones (no full data copy).\n- Each branch has its own compute endpoint.\n- Use the neon CLI or MCP server to create, inspect, and compare branches.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranching.md\n\nFor detailed branch creation workflows (normal vs schema-only branches, reset-from-parent, CLI\u002FMCP selection), use the `neon-postgres-branches` skill. If it isn't installed, fetch it from https:\u002F\u002Fneon.com\u002Fdocs\u002Fai\u002Fskills\u002Fneon-postgres-branches\u002FSKILL.md or install it with:\n\n```bash\nnpx skills add neondatabase\u002Fagent-skills --skill neon-postgres-branches\n```\n\n## Migrations\n\nTest a migration on a branch of production, against production-like data, before applying it to production.\n\nUse a **direct (non-pooled)** connection string when you run the migration, not a pooled one. `neon connection-string` returns the direct string by default; make sure the hostname does not include the `-pooler` suffix.\n\n## Autoscaling\n\nUse this when the user needs compute to scale automatically with workload and wants guidance on CU sizing and runtime behavior.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fautoscaling.md\n\n## Scale to Zero\n\nUse this when optimizing idle costs and discussing suspend\u002Fresume behavior, including cold-start trade-offs.\n\nKey points:\n\n- Idle computes suspend automatically after a default of 5 minutes; the timeout is configurable, and suspension can only be disabled on the Launch and Scale plans.\n- First query after suspend typically has a cold-start penalty (around hundreds of ms)\n- Storage remains active while compute is suspended.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fscale-to-zero.md\n\n## Instant Restore\n\nUse this when the user needs point-in-time recovery or wants to restore data state without traditional backup restore workflows.\n\nKey points:\n\n- History windows for instant restore depend on plan limits.\n- Users can create branches from historical points-in-time.\n- Time Travel queries can be used for historical inspection workflows.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranch-restore.md\n\n## Read Replicas\n\nUse this for read-heavy workloads where the user needs dedicated read-only compute without duplicating storage.\n\nKey points:\n\n- Replicas are read-only compute endpoints sharing the same storage.\n- Creation is fast and scaling is independent from primary compute.\n- Typical use cases: analytics, reporting, and read-heavy APIs.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fread-replicas.md\n\n## Connection Pooling\n\nUse this when the user is in serverless or high-concurrency environments and needs safe, scalable Postgres connection management.\n\nKey points:\n\n- Neon pooling uses PgBouncer.\n- Add `-pooler` to endpoint hostnames to use pooled connections.\n- Pooling is especially important in serverless runtimes with bursty concurrency.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fconnection-pooling.md\n\n## IP Allow Lists\n\nUse this when the user needs to restrict database access by trusted networks, IPs, or CIDR ranges.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fip-allow.md\n\n## Logical Replication\n\nUse this when integrating CDC pipelines, external Postgres sync, or replication-based data movement.\n\nKey points:\n\n- Neon supports native logical replication workflows.\n- Useful for replicating to\u002Ffrom external Postgres systems.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fguides\u002Flogical-replication-guide.md\n\n## Gotchas\n\n### Pooled vs direct connections: use the direct URL for migrations, dumps, and replication\n\nNeon gives you two connection strings for the same database: a **pooled** one (hostname with the `-pooler` suffix) and a **direct\u002Funpooled** one (no `-pooler` suffix). `neon env pull` writes them as `DATABASE_URL` and `DATABASE_URL_UNPOOLED`. The pooled connection routes through PgBouncer in transaction mode, which doesn't support session-level operations. Choose the right one:\n\n- **Pooled (`DATABASE_URL`)** — your application's normal query traffic, especially serverless and connection-per-request workloads.\n- **Direct (`DATABASE_URL_UNPOOLED`)** — schema migrations (Prisma Migrate, Drizzle Kit, Alembic, and others), `pg_dump` \u002F `pg_restore`, logical replication, `LISTEN`\u002F`NOTIFY`, and anything relying on `SET` or other session state.\n\nRunning migrations, dumps, or replication over the pooled connection can fail, and never in a way that names pooling: `prepared statement \"s0\" already exists` from Prisma Migrate, a `SET search_path` that doesn't persist past its own transaction so the next query reports `relation \"mytable\" does not exist`, or a write intermittently hitting a read-only transaction (`SQLSTATE 25006`) that a pooled backend inherited from an earlier client. Migration tools generally take both strings at once — Prisma's `directUrl` alongside `url` — so point that at the direct one rather than swapping `DATABASE_URL` and losing pooling for the application. See https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fconnection-pooling.md.\n","**FIRST**: Use the parent `neon` skill for a Neon overview, getting started with Neon, Neon development best practices, and more.\n\nIf the `neon` skill is not installed, fetch it from https:\u002F\u002Fneon.com\u002Fdocs\u002Fai\u002Fskills\u002Fneon\u002FSKILL.md or install it with:\n\n```bash\nnpx skills add neondatabase\u002Fagent-skills --skill neon\n```\n\n# Lakebase Postgres\n\nLakebase Postgres is the database at the core of Neon. It runs on the lakebase architecture — OLTP built directly on cloud object storage — which decouples storage from compute to offer autoscaling, branching, instant restore, and scale-to-zero. It's fully compatible with Postgres and works with any language, framework, or ORM that supports Postgres.\n\nIt is the same database whether you reach it through Neon or through Databricks; this skill covers the Neon access path.\n\n## Setup Flow\n\n### 1. Select the organization and project\n\nUse the CLI (default) or MCP server to list organizations and projects. Let the user select an existing project or create a new one. Check the `.neon` file for an existing linked project or branch.\n\n### 2. Get the connection string\n\nUse the CLI (default), `neon env pull`, or the MCP server to get the connection string. Store it in `.env` as `DATABASE_URL`. Read the file first before modifying it, to avoid overwriting existing values.\n\n#### When to use pooled vs direct connections\n\n| Use case                                 | Connection type  |\n| ---------------------------------------- | ---------------- |\n| Web applications, serverless functions   | Pooled (-pooler) |\n| Schema migrations                        | Direct           |\n| pg_dump \u002F pg_restore                     | Direct           |\n| Logical replication                      | Direct           |\n| Long-running analytics with temp tables  | Direct           |\n| Admin tasks needing SET or session state | Direct           |\n| LISTEN \u002F NOTIFY                          | Direct           |\n\n### 3. Pick the connection method and driver\n\nAlways pair Neon with an ORM such as **Drizzle** for easy schema management and migrations. Refer to the connection methods guide to pick the correct driver based on how the runtime treats your code: https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fchoose-connection.md.\n\nRecommendations:\n\n- Drizzle as ORM (see https:\u002F\u002Fneon.com\u002Fdocs\u002Fguides\u002Fdrizzle.md)\n- On Vercel, use `node-postgres` (`npm install pg`) with Vercel Fluid compute and `import { attachDatabasePool } from \"@vercel\u002Ffunctions\";`\n- On Cloudflare, use `node-postgres` with Cloudflare Hyperdrive\n- On Neon Functions, use `node-postgres`, as the functions are long-running and reuse the pool across requests.\n- Use the `@neondatabase\u002Fserverless` driver for serverless and edge environments (for example, when using Netlify) — HTTP transport for one-shot queries, WebSocket for transaction support. Link: https:\u002F\u002Fneon.com\u002Fdocs\u002Fserverless\u002Fserverless-driver.md\n\n### 4. Set up the schema\n\nManage schemas and migrations as code. Avoid running ad hoc schema migrations against your database, since they're hard to manage.\n\nIf you're using an ORM, follow your ORM's best practices to manage schemas and migrations. For example, if using Drizzle, only use Drizzle for schema and migration management unless instructed otherwise.\n\n## Branching\n\nUse this when the user is planning isolated environments, schema migration testing, preview deployments, or branch lifecycle automation.\n\nKey points:\n\n- Branches are instant, copy-on-write clones (no full data copy).\n- Each branch has its own compute endpoint.\n- Use the neon CLI or MCP server to create, inspect, and compare branches.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranching.md\n\nFor detailed branch creation workflows (normal vs schema-only branches, reset-from-parent, CLI\u002FMCP selection), use the `neon-postgres-branches` skill. If it isn't installed, fetch it from https:\u002F\u002Fneon.com\u002Fdocs\u002Fai\u002Fskills\u002Fneon-postgres-branches\u002FSKILL.md or install it with:\n\n```bash\nnpx skills add neondatabase\u002Fagent-skills --skill neon-postgres-branches\n```\n\n## Migrations\n\nTest a migration on a branch of production, against production-like data, before applying it to production.\n\nUse a **direct (non-pooled)** connection string when you run the migration, not a pooled one. `neon connection-string` returns the direct string by default; make sure the hostname does not include the `-pooler` suffix.\n\n## Autoscaling\n\nUse this when the user needs compute to scale automatically with workload and wants guidance on CU sizing and runtime behavior.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fautoscaling.md\n\n## Scale to Zero\n\nUse this when optimizing idle costs and discussing suspend\u002Fresume behavior, including cold-start trade-offs.\n\nKey points:\n\n- Idle computes suspend automatically after a default of 5 minutes; the timeout is configurable, and suspension can only be disabled on the Launch and Scale plans.\n- First query after suspend typically has a cold-start penalty (around hundreds of ms)\n- Storage remains active while compute is suspended.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fscale-to-zero.md\n\n## Instant Restore\n\nUse this when the user needs point-in-time recovery or wants to restore data state without traditional backup restore workflows.\n\nKey points:\n\n- History windows for instant restore depend on plan limits.\n- Users can create branches from historical points-in-time.\n- Time Travel queries can be used for historical inspection workflows.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranch-restore.md\n\n## Read Replicas\n\nUse this for read-heavy workloads where the user needs dedicated read-only compute without duplicating storage.\n\nKey points:\n\n- Replicas are read-only compute endpoints sharing the same storage.\n- Creation is fast and scaling is independent from primary compute.\n- Typical use cases: analytics, reporting, and read-heavy APIs.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fread-replicas.md\n\n## Connection Pooling\n\nUse this when the user is in serverless or high-concurrency environments and needs safe, scalable Postgres connection management.\n\nKey points:\n\n- Neon pooling uses PgBouncer.\n- Add `-pooler` to endpoint hostnames to use pooled connections.\n- Pooling is especially important in serverless runtimes with bursty concurrency.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fconnection-pooling.md\n\n## IP Allow Lists\n\nUse this when the user needs to restrict database access by trusted networks, IPs, or CIDR ranges.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fip-allow.md\n\n## Logical Replication\n\nUse this when integrating CDC pipelines, external Postgres sync, or replication-based data movement.\n\nKey points:\n\n- Neon supports native logical replication workflows.\n- Useful for replicating to\u002Ffrom external Postgres systems.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fguides\u002Flogical-replication-guide.md\n\n## Gotchas\n\n### Pooled vs direct connections: use the direct URL for migrations, dumps, and replication\n\nNeon gives you two connection strings for the same database: a **pooled** one (hostname with the `-pooler` suffix) and a **direct\u002Funpooled** one (no `-pooler` suffix). `neon env pull` writes them as `DATABASE_URL` and `DATABASE_URL_UNPOOLED`. The pooled connection routes through PgBouncer in transaction mode, which doesn't support session-level operations. Choose the right one:\n\n- **Pooled (`DATABASE_URL`)** — your application's normal query traffic, especially serverless and connection-per-request workloads.\n- **Direct (`DATABASE_URL_UNPOOLED`)** — schema migrations (Prisma Migrate, Drizzle Kit, Alembic, and others), `pg_dump` \u002F `pg_restore`, logical replication, `LISTEN`\u002F`NOTIFY`, and anything relying on `SET` or other session state.\n\nRunning migrations, dumps, or replication over the pooled connection can fail, and never in a way that names pooling: `prepared statement \"s0\" already exists` from Prisma Migrate, a `SET search_path` that doesn't persist past its own transaction so the next query reports `relation \"mytable\" does not exist`, or a write intermittently hitting a read-only transaction (`SQLSTATE 25006`) that a pooled backend inherited from an earlier client. Migration tools generally take both strings at once — Prisma's `directUrl` alongside `url` — so point that at the direct one rather than swapping `DATABASE_URL` and losing pooling for the application. See https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fconnection-pooling.md.\n",{"name":5,"metadata":24,"description":7},{"parent":25,"source":26},"neon","https:\u002F\u002Fgithub.com\u002Fneondatabase\u002Fagent-skills\u002Ftree\u002Fmain\u002Fskills\u002Fneon-postgres","main","58843b159d7a4050d6b785a98b908cce505c0b92",".agents\u002Fskills\u002Fneon-postgres",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill neon-postgres",{"tool":41,"command":42},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill neon-postgres",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill neon-postgres","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fneon-postgres\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"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":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]