[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A7TB4TSXQ4MBY9TYGBTAPK":3,"skill-same:01M7A7TB4TSXQ4MBY9TYGBTAPK":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7A7TB4TSXQ4MBY9TYGBTAPK","stella-computer",null,"Control Windows desktop apps through Stella's persistent Computer Use runtime.","1missthesun\u002Fstella","1missthesun","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F117537817?v=4","01M7A7RSPHB9FZ1NPMT843HAH1","01M7A7RSQJC98ZNGV147N1ZPVY",2,"MIT","https:\u002F\u002Fgithub.com\u002F1missthesun\u002Fstella\u002Fblob\u002Fmaster\u002Fpackages\u002Fhome-seed\u002Fskills\u002Fstella-computer-windows\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: stella-computer\ndescription: Control Windows desktop apps through Stella's persistent Computer Use runtime.\n---\n\n# Stella Computer for Windows\n\nUse `code` for desktop-app work. The persistent JavaScript runtime is already initialized and exposes a frozen `sky` client. Bindings and delivered app instructions persist for this agent session.\n\n## Observe\n\nStart each desktop-app turn with fresh state:\n\n```js\nvar state = await sky.get_app_state({\n  app: \"Spotify\",\n  screenshot_policy: \"auto\",\n});\ncodeRuntime.write(state.text);\nif (state.screenshot) await codeRuntime.emitImage(state.screenshot.url);\n```\n\nEvery state includes an opaque semantic `state_id`, an immutable compound `observation_id`, `is_diff`, and, for a diff, `base_state_id`. A captured screenshot also has an independent `visual_state_id`; screenshot capture settings do not change `state_id`, while a different visual or resource generation changes `observation_id`. Treat a diff as valid only when its `base_state_id` matches the full state you are building on. Pass `disable_diff: true` whenever the base is unavailable or mismatched.\n\nUse `await sky.list_apps()` only when an app name cannot be resolved. Use `await sky.list_windows()` when the app has multiple top-level windows, then pass `window_id` instead of `app` to state and action calls.\n\nThe default state is a UI Automation diff when sufficient. A screenshot is returned only when visual context is needed. Prefer numbered `element_index` values over coordinates.\n\nPass `disable_diff: true` only when you need a complete recovery tree.\n\n## Act\n\nActions return a receipt after dispatch without rebuilding state or capturing a screenshot. Every action requires the `state_id` from the fresh state it was derived from, including element clicks, secondary actions, scrolling, selection, value\u002Ffocus actions, coordinates, drags, and keyboard input. Missing or stale provenance is rejected before native dispatch instead of targeting changed UI:\n\n```js\nawait sky.click({\n  app: \"Spotify\",\n  element_index: 42,\n  state_id: state.state_id,\n});\nawait sky.set_value({\n  app: \"Spotify\",\n  element_index: 18,\n  value: \"Daft Punk\",\n  state_id: state.state_id,\n});\nawait sky.perform_secondary_action({\n  app: \"Spotify\",\n  element_index: 9,\n  action: \"Invoke\",\n  state_id: state.state_id,\n});\nawait sky.scroll({\n  app: \"Spotify\",\n  element_index: 55,\n  direction: \"down\",\n  pages: 1,\n  state_id: state.state_id,\n});\nawait sky.drag({\n  app: \"Spotify\",\n  from_x: 420,\n  from_y: 310,\n  to_x: 720,\n  to_y: 310,\n  state_id: state.state_id,\n  observation_id: state.observation_id,\n});\nawait sky.press_key({\n  app: \"Spotify\",\n  key: \"Return\",\n  state_id: state.state_id,\n});\nawait sky.type_text({\n  app: \"Spotify\",\n  text: \"hello\",\n  state_id: state.state_id,\n});\n```\n\n`drag` also accepts `path: [{ x, y }, ...]` with at least two points. Drag\ncoordinates must come from the latest screenshot; observe again after the drag.\n\nAfter any action attempt, observe again before sending another standalone action; a failed or interrupted dispatch may still have changed the app, so its prior observation is invalidated. When several ordered actions need the same starting observation and no intermediate result is needed, send them together with `sky.batch([...])`. When the next step depends on a mutation becoming observable, call:\n\n```js\nvar nextState = await sky.wait_for_change({\n  app: \"Spotify\",\n  after_state_id: state.state_id,\n  ...(state.visual_state_id\n    ? { after_visual_state_id: state.visual_state_id }\n    : {}),\n  timeout_ms: 10000,\n  screenshot_policy: \"auto\",\n});\n```\n\nIt polls without advancing the saved diff baseline and returns a final diff anchored exactly to `after_state_id`. Pass `after_visual_state_id` when screenshot-only changes matter; omit it to wait only for semantic UI Automation changes. Then re-derive fresh indices. `sky.batch([...])` validates every action at the native dispatch boundary, then executes ordered actions. A stale action rejects the entire batch before command 0 is dispatched. Give every item the `state_id` from the same fresh starting state when they target the same app; do not batch across decision points, permission prompts, or navigation-policy boundaries. After any failed or partially completed batch, discard its starting state and observe again.\n\n## Text Selection\n\nUse semantic selection when the target exposes a UI Automation text range:\n\n```js\nawait sky.select_text({\n  app: \"Notepad\",\n  element_index: 7,\n  text: \"matching text\",\n  prefix: \"optional text before\",\n  suffix: \"optional text after\",\n  selection_type: \"text\",\n  state_id: state.state_id,\n});\n```\n\n`selection_type` may be `text`, `cursor-before`, or `cursor-after`. Prefix and suffix disambiguate repeated matches.\n\n## Coordinates And Input\n\nFor a visible control missing from the tree, use screenshot pixel coordinates from the latest attached screenshot:\n\n```js\nawait sky.click({\n  window_id: 123456,\n  x: 620,\n  y: 412,\n  state_id: state.state_id,\n  observation_id: state.observation_id,\n});\n```\n\nCoordinates are screenshot pixels and require a state captured with `screenshot_policy: \"always\"`, its semantic `state_id`, and its immutable `observation_id` from the latest observation of that window. They are relative to the window, so they still land right if the window moved. Before sending, Stella checks that the window has the same size and that the pixels around each point (and most of the window) look the same as in that screenshot; small animations pass, a dialog over the point or a different screen does not.\n\nFor a window that never stops changing (a game, a video, an animated launcher), pass `stale_check: \"window\"`: only the same window at the same size is required. You accept that what is under the point may have moved, so observe again after each action.\n\n```js\nawait sky.click({ window_id: 123456, x: 512, y: 300, state_id: state.state_id, observation_id: state.observation_id, stale_check: \"window\" });\n```\n\n### Delivery\n\nStella works in the background: the user keeps their pointer, keyboard focus and the window they are using. Never take over the screen unless the user asked for that in this task.\n\n`delivery` is `\"background\"` (default) or `\"foreground\"`. `\"auto\"` is still accepted and means `\"background\"`.\n\n- Background: element actions go through UI Automation (Invoke, Toggle, Select, Expand, Scroll, Value); other input is posted to the window as messages. The pointer and focus do not move.\n- Some windows ignore posted input: Chromium\u002FElectron\u002FEdge content (pointer: coordinate clicks, drags, scrolling), UWP\u002FXAML apps, GTK and Delphi\u002FVCL apps (pointer and keys). Stella refuses those actions with `background_unavailable` instead of sending input that would be lost. Element clicks still work there through UI Automation, so prefer `element_index` over coordinates.\n- If a background action changed nothing, the next state says so. Stella does not switch to foreground on its own.\n- Foreground brings the window to the front, sends real OS input at the pointer, then puts the user's previous window and pointer back. Use it only when the user asked Stella to take over the screen (for example \"go ahead and use my screen\"); otherwise tell the user what you could not do in the background.\n\n### Windows that expose no elements\n\nWhen the state says the window draws its own content or its Chromium accessibility tree stayed empty, element indices will not appear: work from `screenshot_policy: \"always\"` screenshots with x\u002Fy clicks, drags, `press_key` and `type_text`. Stella already asked Chromium windows to turn their accessibility tree on; when that works the web content is listed as elements and you should use them.\n\nA state without a screenshot says why (minimized, off-screen, or black pixels from exclusive fullscreen or protected content). Do not guess coordinates without a screenshot.\n\n### Errors that mean input was refused\n\nNothing (or only what the message says) was delivered. Do not retry them blindly and never work around them with your own input tools:\n\n- `background_unavailable`: this window would ignore background input of this kind; the message names the reason and your options. Use an element (UI Automation) route or `set_value` if there is one, otherwise tell the user. Retry with `delivery: \"foreground\"` only if the user asked Stella to take over the screen.\n- Other refusals name their cause in the message: the app runs as administrator (Windows drops Stella's input to it), or Windows would not bring the window to the front for foreground input. Tell the user.\n\nDo not add sleeps. `get_app_state` performs adaptive settling and extends its wait only while UI Automation events indicate continued changes.\n\nDo not use PowerShell, registry edits, app-bundle paths, or app-specific scripting to drive desktop apps. Use `Bash` only to diagnose the Computer Use runtime itself.\n","# Stella Computer for Windows\n\nUse `code` for desktop-app work. The persistent JavaScript runtime is already initialized and exposes a frozen `sky` client. Bindings and delivered app instructions persist for this agent session.\n\n## Observe\n\nStart each desktop-app turn with fresh state:\n\n```js\nvar state = await sky.get_app_state({\n  app: \"Spotify\",\n  screenshot_policy: \"auto\",\n});\ncodeRuntime.write(state.text);\nif (state.screenshot) await codeRuntime.emitImage(state.screenshot.url);\n```\n\nEvery state includes an opaque semantic `state_id`, an immutable compound `observation_id`, `is_diff`, and, for a diff, `base_state_id`. A captured screenshot also has an independent `visual_state_id`; screenshot capture settings do not change `state_id`, while a different visual or resource generation changes `observation_id`. Treat a diff as valid only when its `base_state_id` matches the full state you are building on. Pass `disable_diff: true` whenever the base is unavailable or mismatched.\n\nUse `await sky.list_apps()` only when an app name cannot be resolved. Use `await sky.list_windows()` when the app has multiple top-level windows, then pass `window_id` instead of `app` to state and action calls.\n\nThe default state is a UI Automation diff when sufficient. A screenshot is returned only when visual context is needed. Prefer numbered `element_index` values over coordinates.\n\nPass `disable_diff: true` only when you need a complete recovery tree.\n\n## Act\n\nActions return a receipt after dispatch without rebuilding state or capturing a screenshot. Every action requires the `state_id` from the fresh state it was derived from, including element clicks, secondary actions, scrolling, selection, value\u002Ffocus actions, coordinates, drags, and keyboard input. Missing or stale provenance is rejected before native dispatch instead of targeting changed UI:\n\n```js\nawait sky.click({\n  app: \"Spotify\",\n  element_index: 42,\n  state_id: state.state_id,\n});\nawait sky.set_value({\n  app: \"Spotify\",\n  element_index: 18,\n  value: \"Daft Punk\",\n  state_id: state.state_id,\n});\nawait sky.perform_secondary_action({\n  app: \"Spotify\",\n  element_index: 9,\n  action: \"Invoke\",\n  state_id: state.state_id,\n});\nawait sky.scroll({\n  app: \"Spotify\",\n  element_index: 55,\n  direction: \"down\",\n  pages: 1,\n  state_id: state.state_id,\n});\nawait sky.drag({\n  app: \"Spotify\",\n  from_x: 420,\n  from_y: 310,\n  to_x: 720,\n  to_y: 310,\n  state_id: state.state_id,\n  observation_id: state.observation_id,\n});\nawait sky.press_key({\n  app: \"Spotify\",\n  key: \"Return\",\n  state_id: state.state_id,\n});\nawait sky.type_text({\n  app: \"Spotify\",\n  text: \"hello\",\n  state_id: state.state_id,\n});\n```\n\n`drag` also accepts `path: [{ x, y }, ...]` with at least two points. Drag\ncoordinates must come from the latest screenshot; observe again after the drag.\n\nAfter any action attempt, observe again before sending another standalone action; a failed or interrupted dispatch may still have changed the app, so its prior observation is invalidated. When several ordered actions need the same starting observation and no intermediate result is needed, send them together with `sky.batch([...])`. When the next step depends on a mutation becoming observable, call:\n\n```js\nvar nextState = await sky.wait_for_change({\n  app: \"Spotify\",\n  after_state_id: state.state_id,\n  ...(state.visual_state_id\n    ? { after_visual_state_id: state.visual_state_id }\n    : {}),\n  timeout_ms: 10000,\n  screenshot_policy: \"auto\",\n});\n```\n\nIt polls without advancing the saved diff baseline and returns a final diff anchored exactly to `after_state_id`. Pass `after_visual_state_id` when screenshot-only changes matter; omit it to wait only for semantic UI Automation changes. Then re-derive fresh indices. `sky.batch([...])` validates every action at the native dispatch boundary, then executes ordered actions. A stale action rejects the entire batch before command 0 is dispatched. Give every item the `state_id` from the same fresh starting state when they target the same app; do not batch across decision points, permission prompts, or navigation-policy boundaries. After any failed or partially completed batch, discard its starting state and observe again.\n\n## Text Selection\n\nUse semantic selection when the target exposes a UI Automation text range:\n\n```js\nawait sky.select_text({\n  app: \"Notepad\",\n  element_index: 7,\n  text: \"matching text\",\n  prefix: \"optional text before\",\n  suffix: \"optional text after\",\n  selection_type: \"text\",\n  state_id: state.state_id,\n});\n```\n\n`selection_type` may be `text`, `cursor-before`, or `cursor-after`. Prefix and suffix disambiguate repeated matches.\n\n## Coordinates And Input\n\nFor a visible control missing from the tree, use screenshot pixel coordinates from the latest attached screenshot:\n\n```js\nawait sky.click({\n  window_id: 123456,\n  x: 620,\n  y: 412,\n  state_id: state.state_id,\n  observation_id: state.observation_id,\n});\n```\n\nCoordinates are screenshot pixels and require a state captured with `screenshot_policy: \"always\"`, its semantic `state_id`, and its immutable `observation_id` from the latest observation of that window. They are relative to the window, so they still land right if the window moved. Before sending, Stella checks that the window has the same size and that the pixels around each point (and most of the window) look the same as in that screenshot; small animations pass, a dialog over the point or a different screen does not.\n\nFor a window that never stops changing (a game, a video, an animated launcher), pass `stale_check: \"window\"`: only the same window at the same size is required. You accept that what is under the point may have moved, so observe again after each action.\n\n```js\nawait sky.click({ window_id: 123456, x: 512, y: 300, state_id: state.state_id, observation_id: state.observation_id, stale_check: \"window\" });\n```\n\n### Delivery\n\nStella works in the background: the user keeps their pointer, keyboard focus and the window they are using. Never take over the screen unless the user asked for that in this task.\n\n`delivery` is `\"background\"` (default) or `\"foreground\"`. `\"auto\"` is still accepted and means `\"background\"`.\n\n- Background: element actions go through UI Automation (Invoke, Toggle, Select, Expand, Scroll, Value); other input is posted to the window as messages. The pointer and focus do not move.\n- Some windows ignore posted input: Chromium\u002FElectron\u002FEdge content (pointer: coordinate clicks, drags, scrolling), UWP\u002FXAML apps, GTK and Delphi\u002FVCL apps (pointer and keys). Stella refuses those actions with `background_unavailable` instead of sending input that would be lost. Element clicks still work there through UI Automation, so prefer `element_index` over coordinates.\n- If a background action changed nothing, the next state says so. Stella does not switch to foreground on its own.\n- Foreground brings the window to the front, sends real OS input at the pointer, then puts the user's previous window and pointer back. Use it only when the user asked Stella to take over the screen (for example \"go ahead and use my screen\"); otherwise tell the user what you could not do in the background.\n\n### Windows that expose no elements\n\nWhen the state says the window draws its own content or its Chromium accessibility tree stayed empty, element indices will not appear: work from `screenshot_policy: \"always\"` screenshots with x\u002Fy clicks, drags, `press_key` and `type_text`. Stella already asked Chromium windows to turn their accessibility tree on; when that works the web content is listed as elements and you should use them.\n\nA state without a screenshot says why (minimized, off-screen, or black pixels from exclusive fullscreen or protected content). Do not guess coordinates without a screenshot.\n\n### Errors that mean input was refused\n\nNothing (or only what the message says) was delivered. Do not retry them blindly and never work around them with your own input tools:\n\n- `background_unavailable`: this window would ignore background input of this kind; the message names the reason and your options. Use an element (UI Automation) route or `set_value` if there is one, otherwise tell the user. Retry with `delivery: \"foreground\"` only if the user asked Stella to take over the screen.\n- Other refusals name their cause in the message: the app runs as administrator (Windows drops Stella's input to it), or Windows would not bring the window to the front for foreground input. Tell the user.\n\nDo not add sleeps. `get_app_state` performs adaptive settling and extends its wait only while UI Automation events indicate continued changes.\n\nDo not use PowerShell, registry edits, app-bundle paths, or app-specific scripting to drive desktop apps. Use `Bash` only to diagnose the Computer Use runtime itself.\n",{"name":5,"description":7},"master","a8de9ed0018bf340763d19d13a2fa42697938516","packages\u002Fhome-seed\u002Fskills\u002Fstella-computer-windows",1,"https:\u002F\u002Fgithub.com\u002F1missthesun\u002Fstella","https:\u002F\u002Fstella.sh","https:\u002F\u002Fgithub.com\u002F1missthesun","2026-11-15 03:51:46",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add 1missthesun\u002Fstella --skill stella-computer",{"tool":37,"command":38},"bunx","bunx skills add 1missthesun\u002Fstella --skill stella-computer",{"tool":40,"command":41},"pnpm","pnpm dlx skills add 1missthesun\u002Fstella --skill stella-computer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F1missthesun\u002Fstella\u002Fblob\u002Fmaster\u002Fpackages\u002Fhome-seed\u002Fskills\u002Fstella-computer-windows\u002FSKILL.md",true,[],[46,52,58,67,74,81],{"skillNo":47,"name":5,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7E09S0EJ3P47YANQC80TWQD","Control Linux desktop apps (Hyprland) through Stella's persistent Computer Use runtime.","https:\u002F\u002Fgithub.com\u002F1missthesun\u002Fstella\u002Fblob\u002Fmaster\u002Fpackages\u002Fhome-seed\u002Fskills\u002Fstella-computer-linux\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7A7VEDYQ7GGMN5M3BQSSR9V","stella-browser","https:\u002F\u002Fgithub.com\u002F1missthesun\u002Fstella\u002Fblob\u002Fmaster\u002Fpackages\u002Fstella-browser\u002Fskills\u002Fstella-browser\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":62,"licenseFileUrl":63,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7A7V9FMKK1F4FYE7F840PPG","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002F1missthesun\u002Fstella\u002Fblob\u002Fmaster\u002Fpackages\u002Fstella-browser\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002F1missthesun\u002Fstella\u002Fblob\u002Fmaster\u002Fpackages\u002Fstella-browser\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7A7V5R5PPEK44XQW873ZREC","x-api","Use X (Twitter) through Stella's connected account.","https:\u002F\u002Fgithub.com\u002F1missthesun\u002Fstella\u002Fblob\u002Fmaster\u002Fpackages\u002Fhome-seed\u002Fskills\u002Fx-api\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7A7V0AT0JMNKWB6CN6NMAZ6","visual-craft","Read before making something people will look at, where the look is the work — a website or landing page, an HTML canvas or interactive piece, an animation or motion graphics, a video, an image, or a visual design. Not for routine UI fixes or code whose output isn't visual.","https:\u002F\u002Fgithub.com\u002F1missthesun\u002Fstella\u002Fblob\u002Fmaster\u002Fpackages\u002Fhome-seed\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7A7TSE4NCFK7D3Z35P3D1RD","stella-office","Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using Stella's bundled `stella-office` CLI. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.","https:\u002F\u002Fgithub.com\u002F1missthesun\u002Fstella\u002Fblob\u002Fmaster\u002Fpackages\u002Fhome-seed\u002Fskills\u002Fstella-office\u002FSKILL.md",[],[]]