[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MGVQ7SHNXMTPKSKM18D092":3,"skill-same:01M6MGVQ7SHNXMTPKSKM18D092":69},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6MGVQ7SHNXMTPKSKM18D092","standalone",null,"Make a studio's game into an app of its own, a desktop app for macOS, Windows and Linux (the kind of build Steam accepts for upload) and a phone app for iOS and Android (the files the App Store and Google Play accept for upload; each store's review, fees and rules are its own). It is the same web build of the game in a thin shell (Electron on computers, Capacitor on phones) that still finds its rooms on the studio's own deployed site and plays offline with its bots when it cannot. Use when someone asks for a Steam build, a desktop app, a download, an installer, an iPhone, iPad or Android app, a store release, or \"a standalone version\" of a game.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fhomie-rocks\u002Fhomie\u002Fskills\u002Fstandalone\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"steam","when","app store","studio","app","xcode","ipad","iphone","bots","desktop app","google","later","files","node","game","offline","release","run","workflow","review","2026-11-10 10:12:30",false,"---\nname: standalone\ndescription: Make a studio's game into an app of its own, a desktop app for macOS, Windows and Linux (the kind of build Steam accepts for upload) and a phone app for iOS and Android (the files the App Store and Google Play accept for upload; each store's review, fees and rules are its own). It is the same web build of the game in a thin shell (Electron on computers, Capacitor on phones) that still finds its rooms on the studio's own deployed site and plays offline with its bots when it cannot. Use when someone asks for a Steam build, a desktop app, a download, an installer, an iPhone, iPad or Android app, a store release, or \"a standalone version\" of a game.\ncompatibility: Node 22 and a studio on @homie-rocks\u002Fstudio 0.32.0 or later (0.32.1 for a run on a real iPhone). A Mac for the macOS and iOS builds (Xcode for iOS). The Android SDK and JDK 21 for Android. Nothing is installed for the person; a target whose tool is missing is skipped, and a GitHub workflow can build it instead.\n---\n\n**Apps:** For a business, venue, cause or customer app, follow the `app` skill: `apps\u002F\u003Cid>\u002Fapp.json`, one morphing screen, roles and parts. Reuse these engines and workflows; do not impose game rounds, scores, bots, a game demo or page navigation. The app check proves shared actions and reconnect; app stores use the same standalone command.\n\n\n# A game as an app of its own\n\nA studio is the folder with `studio.json`. `homie-studio standalone` wraps a game the studio already has. It does\nnot port it, rewrite it or change how it plays: the app shows the same files `homie-studio build` makes.\n`node_modules\u002F@homie-rocks\u002Fstudio\u002Fstandalone\u002FSTANDALONE.md` is the full guide; read it before a release, and\nread its \"What has been run and what has not\" to the person before they count on anything it lists as never\nrun.\n\nWith no terminal, the `game_standalone` tool does the same (with `plan: true` first). Its build is a background\njob that takes minutes: `studio_job` gives the result in words when it is done, and those words, with the list\nof what the standalone game does not have, are for the person.\n\n## 1. Plan first, and say what is missing\n\n```sh\nnpx --no-install homie-studio standalone plan \u003Cid>\n```\n\nIt changes nothing and installs nothing. Tell the person, in your own short words, all of this:\n\n- **Which targets this computer can build**, and for each one it cannot, why and the fix it printed. Install the prerequisites for the requested target yourself. The person only handles OS or store authorization prompts. A computer\n  that cannot make a target can still get it from GitHub (section 5).\n- **The address built into every copy.** A shipped copy keeps it for good. If it is a workers.dev address,\n  say so and recommend the studio's own domain before shipping. With no address the copy plays offline only.\n- **Every warning it printed**, as it is.\n- **What the standalone game does not have (v1)**, as the plan lists it. Say it before they ship anything, not\n  after: no player accounts or sign-in, no cloud saves (saves stay on the device and are lost when the app is\n  uninstalled), no shop, no room chat, no watching or big screen, only the public server through an open door,\n  no automatic updates, Steam's overlay and achievements never run, an unsigned Windows build, and nothing is\n  uploaded to a store for them. Do not soften it and do not leave a line out. If one of these matters to them,\n  the honest answer today is that the web game has it and the app does not.\n- **What a store is.** A build is the kind of file a store accepts for upload, never a promise that the store\n  takes the game. Before they pay anything, tell them what STANDALONE.md's \"Before you spend money\" says (Apple's\n  yearly membership and its review, which can reject a web game in a wrapper; Google Play's fee and its closed\n  test for new personal accounts; Steam Direct's fee for each app and its waiting periods), and that those facts\n  have a date on them: they check each store's own page.\n\nTwo things must be true before **Quick play** finds a room in a copy: the studio is on `@homie-rocks\u002Fstudio`\n0.32.0 or later (the `studio-setup` skill's upgrade), **and it has been deployed since** (the `publish` skill).\nThe plan cannot see which version the live site runs; ask, or deploy. A room made or joined by its code works\nwith an older site too (seen against 0.31.0, not promised for every older version): say both halves, and never\n\"it needs 0.32.0 to play online\".\n\nFor an older browser-hosted game, before anything ships name its revision: `\"netplay\": { \"version\": \"1\" }` in its `game.json`.\nAn older copy then keeps playing with other copies of its revision, and says \"Update \u003CName> to play online\nwith everyone.\" when it meets a newer one. Raise the number with every change an older copy cannot play with.\n\nFor a rules game, `room.offline` defaults to true: the app includes its guarded rules, host runtime and all\ntunables, and plays that build locally with bots. Say that those rules and tunables reach the device. With\n`room.offline: false` and `host: server`, the app needs a connection and carries no private rules. A server\nroom accepts the live build only: an older app is told to update and can play offline if enabled. With\n`host: browser`, older copies can still meet copies of the same build; every copy includes the rules.\n\n## 2. Build\n\n```sh\nnpx --no-install homie-studio standalone build \u003Cid>                    # every target this computer can make\nnpx --no-install homie-studio standalone build \u003Cid> --for mac,windows  # only these\n```\n\nIt builds the game for the web first, installs the wrapper tools into `.studio\u002Fstandalone\u002F\u003Cid>\u002F` the first time\n(a few hundred MB, once; say so before you start), and takes minutes: run it as a background task and tell the\nperson what is happening. Everything it makes is in `.studio\u002Fstandalone\u002F\u003Cid>\u002Fout\u002F\u003Ctarget>\u002F`. That folder is\ngit-ignored: never commit it, never edit it.\n\nRead the result and say it truthfully. A target is **built**, **skipped** (a tool is missing: say the fix) or\n**failed** (say why, in its words); a release that could not be signed is **UNSIGNED**, and the command does not\nreport success. \"Skipped\" is not \"built\", and built is not \"works\": the result says, for the one desktop build\nthis computer can run, \"started here and loaded the game: yes\" or \"NO\", and for every other target \"built, not\nstarted on this computer\". Pass that on as it is. The Windows and Linux builds have never been started by the\npeople who made this, on any computer: say so when you hand one over.\n\nEach kind has its own folder (`out\u002F\u003Ctarget>\u002Fdebug\u002F`, `out\u002F\u003Ctarget>\u002Frelease\u002F`): a build to try never replaces a\nrelease.\n\n## 3. Try it\n\n```sh\nnpx --no-install homie-studio standalone run \u003Cid>            # this computer's desktop build\nnpx --no-install homie-studio standalone run \u003Cid> --for ios  # or android: Capacitor asks which simulator or phone\n```\n\nPlay it with the person. Check that it finds a room when the studio is online (the room button says \"Room 3\")\nand plays with its bots when it is not (\"Playing offline · Try again\"). For a private server game with offline\nplay disabled, check that it says \"Connection needed\" instead. Test with networking actually unavailable,\nso a missing rules file cannot be hidden by a successful download.\n\n### On their own iPhone or iPad\n\n```sh\nnpx --no-install homie-studio standalone run \u003Cid> --for ios --device\n```\n\nbuilds the game for the one phone plugged in to the Mac, signs it for their Apple team, installs it over the\ncable, starts it, and looks for it among the phone's running programs. **Ask before you run it, in these\nwords: this adds the phone to your Apple team's device list** (a team may register a limited number a year, and\na device stays until the membership year renews), and Xcode makes a development profile for the app. `--device`\nis their yes: never add it on your own. With no terminal, `game_standalone` with `device: true` does the same,\nas a background job.\n\nIt needs Xcode signed in to their Apple account, the phone unlocked and trusting the Mac, and Developer Mode\non. When one is missing the result says which, with the fix; pass it on as it is (for Developer Mode: on the\nphone, Settings, Privacy & Security, Developer Mode, and the phone restarts). It says \"running\" only when it\nfound the game among the phone's programs; \"installed, not seen running\" is not \"running\". The team comes from\n`HOMIE_APPLE_TEAM`, else the keychain's only one: never ask for a team id, a phone's id or a name in the chat,\nand never repeat one. There is no such run for an Android phone yet: `standalone run \u003Cid> --for android` lets\nCapacitor ask which phone, and that has never been run on a real Android phone.\n\n## 4. A release\n\nOnly when the person asks to ship.\n\n1. `game.json` needs the app's id first: `\"standalone\": { \"appId\": \"com.example.gemrush\" }`. A store never lets\n   it change, so derive it from their owned domain and game slug, show it with the release plan, and keep it stable. `--release` stops and prints the\n   exact lines when it is missing. Version, build number, orientation, icon and Steam's numbers go in the same\n   block.\n2. A real icon: a square 1024 by 1024 PNG at `games\u002F\u003Cid>\u002Ficon.png`. Without one the app wears the game's cover\n   or a letter, which no store page should.\n3. Discover the existing signing identity and team with the platform tools; configure the build yourself.\n   If none exists, open Xcode\u002FApple Developer or the appropriate store's sign-in and let the owner approve.\n   Never tell a person to set environment variables, copy a team id, find a key or open a terminal.\n   Never ask for a password, keystore or certificate in the chat.\n   Keep credentials in the OS keychain or provider-managed secrets. If the host cannot complete signing,\n   produce the unsigned build and name the single missing provider approval; do not claim it is signed.\n   Apple signing and store submission still need real-account validation before promising a one-click flow.\n4. `npx --no-install homie-studio standalone build \u003Cid> --release`.\n5. **Uploading is the person's.** The build prints the exact steps for Steam (`steamcmd`), App Store Connect\n   (Transporter) and Google Play (the Play Console). Hand them over; run none of them.\n\nFor Steam: `npx --no-install homie-studio standalone steam \u003Cid>` writes Steam's build file from the numbers in\n`game.json`, or says what to create in Steamworks first, with the launch options to set there (the Linux one\nneeds `--no-sandbox` in its arguments). Nothing here has been started by Steam: not the overlay (Electron apps\noften show none), not the Linux build in Steam's runtime, not the build file through `steamcmd`. Say that, and\ndo not promise an overlay.\n\n## 5. A target this computer cannot make\n\n```sh\nnpx --no-install homie-studio standalone ci \u003Cid>\n```\n\nwrites `.github\u002Fworkflows\u002Fstandalone.yml`: the five builds on GitHub's own Windows, Linux and macOS machines,\nstarted by hand from the Actions tab. Commit it on a branch like any change, and tell the person to set the\nrepository variable `HOMIE_SITE` to the studio's address. It signs nothing but an Android release, never makes\na macOS or iOS release (its macOS app is unsigned and its iOS one is a simulator build), and uploads to no\nstore. The workflow itself has not been run by the people who made it: read the first run's log with them.\n\n## After a deploy\n\n`homie-studio deploy` says when it makes a different netplay version live than the copies that were built. Pass\nthat on: copies already out keep playing offline and with each other, and need an update to play with everyone.\n","**Apps:** For a business, venue, cause or customer app, follow the `app` skill: `apps\u002F\u003Cid>\u002Fapp.json`, one morphing screen, roles and parts. Reuse these engines and workflows; do not impose game rounds, scores, bots, a game demo or page navigation. The app check proves shared actions and reconnect; app stores use the same standalone command.\n\n\n# A game as an app of its own\n\nA studio is the folder with `studio.json`. `homie-studio standalone` wraps a game the studio already has. It does\nnot port it, rewrite it or change how it plays: the app shows the same files `homie-studio build` makes.\n`node_modules\u002F@homie-rocks\u002Fstudio\u002Fstandalone\u002FSTANDALONE.md` is the full guide; read it before a release, and\nread its \"What has been run and what has not\" to the person before they count on anything it lists as never\nrun.\n\nWith no terminal, the `game_standalone` tool does the same (with `plan: true` first). Its build is a background\njob that takes minutes: `studio_job` gives the result in words when it is done, and those words, with the list\nof what the standalone game does not have, are for the person.\n\n## 1. Plan first, and say what is missing\n\n```sh\nnpx --no-install homie-studio standalone plan \u003Cid>\n```\n\nIt changes nothing and installs nothing. Tell the person, in your own short words, all of this:\n\n- **Which targets this computer can build**, and for each one it cannot, why and the fix it printed. Install the prerequisites for the requested target yourself. The person only handles OS or store authorization prompts. A computer\n  that cannot make a target can still get it from GitHub (section 5).\n- **The address built into every copy.** A shipped copy keeps it for good. If it is a workers.dev address,\n  say so and recommend the studio's own domain before shipping. With no address the copy plays offline only.\n- **Every warning it printed**, as it is.\n- **What the standalone game does not have (v1)**, as the plan lists it. Say it before they ship anything, not\n  after: no player accounts or sign-in, no cloud saves (saves stay on the device and are lost when the app is\n  uninstalled), no shop, no room chat, no watching or big screen, only the public server through an open door,\n  no automatic updates, Steam's overlay and achievements never run, an unsigned Windows build, and nothing is\n  uploaded to a store for them. Do not soften it and do not leave a line out. If one of these matters to them,\n  the honest answer today is that the web game has it and the app does not.\n- **What a store is.** A build is the kind of file a store accepts for upload, never a promise that the store\n  takes the game. Before they pay anything, tell them what STANDALONE.md's \"Before you spend money\" says (Apple's\n  yearly membership and its review, which can reject a web game in a wrapper; Google Play's fee and its closed\n  test for new personal accounts; Steam Direct's fee for each app and its waiting periods), and that those facts\n  have a date on them: they check each store's own page.\n\nTwo things must be true before **Quick play** finds a room in a copy: the studio is on `@homie-rocks\u002Fstudio`\n0.32.0 or later (the `studio-setup` skill's upgrade), **and it has been deployed since** (the `publish` skill).\nThe plan cannot see which version the live site runs; ask, or deploy. A room made or joined by its code works\nwith an older site too (seen against 0.31.0, not promised for every older version): say both halves, and never\n\"it needs 0.32.0 to play online\".\n\nFor an older browser-hosted game, before anything ships name its revision: `\"netplay\": { \"version\": \"1\" }` in its `game.json`.\nAn older copy then keeps playing with other copies of its revision, and says \"Update \u003CName> to play online\nwith everyone.\" when it meets a newer one. Raise the number with every change an older copy cannot play with.\n\nFor a rules game, `room.offline` defaults to true: the app includes its guarded rules, host runtime and all\ntunables, and plays that build locally with bots. Say that those rules and tunables reach the device. With\n`room.offline: false` and `host: server`, the app needs a connection and carries no private rules. A server\nroom accepts the live build only: an older app is told to update and can play offline if enabled. With\n`host: browser`, older copies can still meet copies of the same build; every copy includes the rules.\n\n## 2. Build\n\n```sh\nnpx --no-install homie-studio standalone build \u003Cid>                    # every target this computer can make\nnpx --no-install homie-studio standalone build \u003Cid> --for mac,windows  # only these\n```\n\nIt builds the game for the web first, installs the wrapper tools into `.studio\u002Fstandalone\u002F\u003Cid>\u002F` the first time\n(a few hundred MB, once; say so before you start), and takes minutes: run it as a background task and tell the\nperson what is happening. Everything it makes is in `.studio\u002Fstandalone\u002F\u003Cid>\u002Fout\u002F\u003Ctarget>\u002F`. That folder is\ngit-ignored: never commit it, never edit it.\n\nRead the result and say it truthfully. A target is **built**, **skipped** (a tool is missing: say the fix) or\n**failed** (say why, in its words); a release that could not be signed is **UNSIGNED**, and the command does not\nreport success. \"Skipped\" is not \"built\", and built is not \"works\": the result says, for the one desktop build\nthis computer can run, \"started here and loaded the game: yes\" or \"NO\", and for every other target \"built, not\nstarted on this computer\". Pass that on as it is. The Windows and Linux builds have never been started by the\npeople who made this, on any computer: say so when you hand one over.\n\nEach kind has its own folder (`out\u002F\u003Ctarget>\u002Fdebug\u002F`, `out\u002F\u003Ctarget>\u002Frelease\u002F`): a build to try never replaces a\nrelease.\n\n## 3. Try it\n\n```sh\nnpx --no-install homie-studio standalone run \u003Cid>            # this computer's desktop build\nnpx --no-install homie-studio standalone run \u003Cid> --for ios  # or android: Capacitor asks which simulator or phone\n```\n\nPlay it with the person. Check that it finds a room when the studio is online (the room button says \"Room 3\")\nand plays with its bots when it is not (\"Playing offline · Try again\"). For a private server game with offline\nplay disabled, check that it says \"Connection needed\" instead. Test with networking actually unavailable,\nso a missing rules file cannot be hidden by a successful download.\n\n### On their own iPhone or iPad\n\n```sh\nnpx --no-install homie-studio standalone run \u003Cid> --for ios --device\n```\n\nbuilds the game for the one phone plugged in to the Mac, signs it for their Apple team, installs it over the\ncable, starts it, and looks for it among the phone's running programs. **Ask before you run it, in these\nwords: this adds the phone to your Apple team's device list** (a team may register a limited number a year, and\na device stays until the membership year renews), and Xcode makes a development profile for the app. `--device`\nis their yes: never add it on your own. With no terminal, `game_standalone` with `device: true` does the same,\nas a background job.\n\nIt needs Xcode signed in to their Apple account, the phone unlocked and trusting the Mac, and Developer Mode\non. When one is missing the result says which, with the fix; pass it on as it is (for Developer Mode: on the\nphone, Settings, Privacy & Security, Developer Mode, and the phone restarts). It says \"running\" only when it\nfound the game among the phone's programs; \"installed, not seen running\" is not \"running\". The team comes from\n`HOMIE_APPLE_TEAM`, else the keychain's only one: never ask for a team id, a phone's id or a name in the chat,\nand never repeat one. There is no such run for an Android phone yet: `standalone run \u003Cid> --for android` lets\nCapacitor ask which phone, and that has never been run on a real Android phone.\n\n## 4. A release\n\nOnly when the person asks to ship.\n\n1. `game.json` needs the app's id first: `\"standalone\": { \"appId\": \"com.example.gemrush\" }`. A store never lets\n   it change, so derive it from their owned domain and game slug, show it with the release plan, and keep it stable. `--release` stops and prints the\n   exact lines when it is missing. Version, build number, orientation, icon and Steam's numbers go in the same\n   block.\n2. A real icon: a square 1024 by 1024 PNG at `games\u002F\u003Cid>\u002Ficon.png`. Without one the app wears the game's cover\n   or a letter, which no store page should.\n3. Discover the existing signing identity and team with the platform tools; configure the build yourself.\n   If none exists, open Xcode\u002FApple Developer or the appropriate store's sign-in and let the owner approve.\n   Never tell a person to set environment variables, copy a team id, find a key or open a terminal.\n   Never ask for a password, keystore or certificate in the chat.\n   Keep credentials in the OS keychain or provider-managed secrets. If the host cannot complete signing,\n   produce the unsigned build and name the single missing provider approval; do not claim it is signed.\n   Apple signing and store submission still need real-account validation before promising a one-click flow.\n4. `npx --no-install homie-studio standalone build \u003Cid> --release`.\n5. **Uploading is the person's.** The build prints the exact steps for Steam (`steamcmd`), App Store Connect\n   (Transporter) and Google Play (the Play Console). Hand them over; run none of them.\n\nFor Steam: `npx --no-install homie-studio standalone steam \u003Cid>` writes Steam's build file from the numbers in\n`game.json`, or says what to create in Steamworks first, with the launch options to set there (the Linux one\nneeds `--no-sandbox` in its arguments). Nothing here has been started by Steam: not the overlay (Electron apps\noften show none), not the Linux build in Steam's runtime, not the build file through `steamcmd`. Say that, and\ndo not promise an overlay.\n\n## 5. A target this computer cannot make\n\n```sh\nnpx --no-install homie-studio standalone ci \u003Cid>\n```\n\nwrites `.github\u002Fworkflows\u002Fstandalone.yml`: the five builds on GitHub's own Windows, Linux and macOS machines,\nstarted by hand from the Actions tab. Commit it on a branch like any change, and tell the person to set the\nrepository variable `HOMIE_SITE` to the studio's address. It signs nothing but an Android release, never makes\na macOS or iOS release (its macOS app is unsigned and its iOS one is a simulator build), and uploads to no\nstore. The workflow itself has not been run by the people who made it: read the first run's log with them.\n\n## After a deploy\n\n`homie-studio deploy` says when it makes a different netplay version live than the copies that were built. Pass\nthat on: copies already out keep playing offline and with each other, and need an update to play with everyone.\n",{"name":5,"description":7,"compatibility":44},"Node 22 and a studio on @homie-rocks\u002Fstudio 0.32.0 or later (0.32.1 for a run on a real iPhone). A Mac for the macOS and iOS builds (Xcode for iOS). The Android SDK and JDK 21 for Android. Nothing is installed for the person; a target whose tool is missing is skipped, and a GitHub workflow can build it instead.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fhomie-rocks\u002Fhomie\u002Fskills\u002Fstandalone",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill standalone",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill standalone",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill standalone","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fhomie-rocks\u002Fhomie\u002Fskills\u002Fstandalone\u002FSKILL.md",true,[],[70,80,88,96,104,112],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":79},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":79},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\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":74,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":79},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":79},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":79},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]