[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77V0XARBB20X17XJTPK7C69":3,"skill-same:01M77V0XARBB20X17XJTPK7C69":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},"01M77V0XARBB20X17XJTPK7C69","orca-per-workspace-env",null,"Set up, review, debug, or validate Orca per-workspace environment recipes — on-demand, disposable runtimes (cloud sandboxes, VMs, or local) created fresh for each workspace. Covers first-time setup (provider prerequisites, the reusable base snapshot, the coding-agent auth snapshot, credentials, and state), not just the per-workspace lifecycle scripts. Use to stand up per-workspace environments, fix an `environmentRecipes` entry in `orca.yaml`, scaffold provider lifecycle scripts, or resolve an `orca vm recipe doctor` failure.","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\u002Forca-per-workspace-env\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Set up, review, debug, or validate Orca per-workspace environment recipes — on-demand, disposable runtimes (cloud sandboxes, VMs, or local) created fresh for each workspace. Covers first-time setup (provider prerequisites, the reusable base snapshot, the coding-agent auth snapshot, credentials, and state), not just the per-workspace lifecycle scripts. Use to stand up per-workspace environments, fix an `environmentRecipes` entry in `orca.yaml`, scaffold provider lifecycle scripts, or resolve an `orca vm recipe doctor` failure.\"\n---\n# Per-Workspace Environments\n\nThis file is a discovery stub, not the usage guide. The full, version-matched per-workspace\nenvironment reference is served by the `orca` binary itself — kept out of this file on\npurpose so it can never drift from the binary that will actually run your commands.\n\nEngage Orca whenever you set up, review, debug, or validate a per-workspace environment\nrecipe — the on-demand, disposable runtimes (cloud sandboxes, VMs, or local) created fresh\nfor each workspace. This covers first-time setup (provider prerequisites, the reusable base\nsnapshot, the coding-agent auth snapshot, credentials, and state), not just the\nper-workspace lifecycle scripts. Use it to stand up per-workspace environments, fix an\n`environmentRecipes` entry in `orca.yaml`, scaffold provider lifecycle scripts, or resolve\nan `orca vm recipe doctor` failure. Orca is a thin wrapper: you guide, detect, and scaffold;\nyou never own the user's cloud account, billing, images, or credentials, and never spend\nmoney without an explicit user OK.\n\n## Resolve the CLI for this session\n\nChoose the executable once and reuse it for every later command:\n\n- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this\n  for managed WSL sessions.\n- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`.\n- Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare\n  `orca` there — outside Orca's terminals it normally resolves to the\n  GNOME Orca screen reader (`\u002Fusr\u002Fbin\u002Forca`) and starts speech on the user's machine.\n- Otherwise, use `orca`.\n\nBelow, `ORCA` is a placeholder for the executable you resolved. Substitute it before\nrunning anything; do not create a shell variable or run `ORCA` literally. This works the\nsame way in POSIX shells, PowerShell, and cmd.exe.\n\nIf the selected executable cannot run, report its exact error and stop. Do not fall through\nto another executable, which could silently target a different Orca build.\n\n## Load the full guide before running Orca commands\n\n```text\nORCA skills get orca-per-workspace-env\n```\n\nThat prints the complete, version-matched guide for the exact binary that will handle your\nnext commands — provider setup, base and auth snapshots, `environmentRecipes` in\n`orca.yaml`, lifecycle scripts, and `orca vm recipe doctor`. Read it first, then run the\nspecific command you need.\n\nDon't guess subcommands or flags from memory or from a cached copy of this stub. They\nchange between Orca releases, and this file deliberately no longer lists them. Confirm the\napp is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and\nprefer `--json` for agent-driven calls.\n\n## If an older Orca does not recognize `skills get`\n\nUse this fallback only when the selected binary explicitly reports that `skills get` is an\nunknown command. Another failure is not proof of an older binary; report it rather than\nguessing or changing executables. For a confirmed pre-guide binary, use only this bounded,\nread-only bootstrap to orient. Do not dead-end and do not invent commands:\n\n```text\nORCA status --json\nORCA vm recipe doctor \u003Crecipe-id> --repo-path \u003Crepo> --json\n```\n\nThe doctor command above is the free static check. Never add `--provision` without the\nuser's explicit approval because it creates provider resources and may spend money.\n\nThen tell the user that updating Orca restores the full, version-matched guide via\n`ORCA skills get orca-per-workspace-env`. Beyond these commands, ask the user rather than\nguessing a command surface this older binary may not support.\n","# Per-Workspace Environments\n\nThis file is a discovery stub, not the usage guide. The full, version-matched per-workspace\nenvironment reference is served by the `orca` binary itself — kept out of this file on\npurpose so it can never drift from the binary that will actually run your commands.\n\nEngage Orca whenever you set up, review, debug, or validate a per-workspace environment\nrecipe — the on-demand, disposable runtimes (cloud sandboxes, VMs, or local) created fresh\nfor each workspace. This covers first-time setup (provider prerequisites, the reusable base\nsnapshot, the coding-agent auth snapshot, credentials, and state), not just the\nper-workspace lifecycle scripts. Use it to stand up per-workspace environments, fix an\n`environmentRecipes` entry in `orca.yaml`, scaffold provider lifecycle scripts, or resolve\nan `orca vm recipe doctor` failure. Orca is a thin wrapper: you guide, detect, and scaffold;\nyou never own the user's cloud account, billing, images, or credentials, and never spend\nmoney without an explicit user OK.\n\n## Resolve the CLI for this session\n\nChoose the executable once and reuse it for every later command:\n\n- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this\n  for managed WSL sessions.\n- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`.\n- Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare\n  `orca` there — outside Orca's terminals it normally resolves to the\n  GNOME Orca screen reader (`\u002Fusr\u002Fbin\u002Forca`) and starts speech on the user's machine.\n- Otherwise, use `orca`.\n\nBelow, `ORCA` is a placeholder for the executable you resolved. Substitute it before\nrunning anything; do not create a shell variable or run `ORCA` literally. This works the\nsame way in POSIX shells, PowerShell, and cmd.exe.\n\nIf the selected executable cannot run, report its exact error and stop. Do not fall through\nto another executable, which could silently target a different Orca build.\n\n## Load the full guide before running Orca commands\n\n```text\nORCA skills get orca-per-workspace-env\n```\n\nThat prints the complete, version-matched guide for the exact binary that will handle your\nnext commands — provider setup, base and auth snapshots, `environmentRecipes` in\n`orca.yaml`, lifecycle scripts, and `orca vm recipe doctor`. Read it first, then run the\nspecific command you need.\n\nDon't guess subcommands or flags from memory or from a cached copy of this stub. They\nchange between Orca releases, and this file deliberately no longer lists them. Confirm the\napp is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and\nprefer `--json` for agent-driven calls.\n\n## If an older Orca does not recognize `skills get`\n\nUse this fallback only when the selected binary explicitly reports that `skills get` is an\nunknown command. Another failure is not proof of an older binary; report it rather than\nguessing or changing executables. For a confirmed pre-guide binary, use only this bounded,\nread-only bootstrap to orient. Do not dead-end and do not invent commands:\n\n```text\nORCA status --json\nORCA vm recipe doctor \u003Crecipe-id> --repo-path \u003Crepo> --json\n```\n\nThe doctor command above is the free static check. Never add `--provision` without the\nuser's explicit approval because it creates provider resources and may spend money.\n\nThen tell the user that updating Orca restores the full, version-matched guide via\n`ORCA skills get orca-per-workspace-env`. Beyond these commands, ask the user rather than\nguessing a command surface this older binary may not support.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Forca-per-workspace-env",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 orca-per-workspace-env",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill orca-per-workspace-env",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill orca-per-workspace-env","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Forca-per-workspace-env\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",[],[]]