[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEVTGTWFWN8S18CPVDG5RZ":3,"skill-same:01M7AEVTGTWFWN8S18CPVDG5RZ":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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},"01M7AEVTGTWFWN8S18CPVDG5RZ","company-tools",null,"How to use the company's own tools correctly - the shared browser and desktop, owner attachments, ReviewTargets, supervised services, legal\u002Fpublish\u002Fjudgement commands, Coolify, native sheets, structured decisions, connected tools, native documents and Rooms. Read before the first use of any of them in a session.","BlueprintLabIO\u002Frestless-core","BlueprintLabIO","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222796351?v=4","01M7AETKD0TZXRAGH2WAKGNYE6","01M7AETKE63A80017SD5ZWAEF4",12,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fcompany-tools\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: company-tools\ndescription: How to use the company's own tools correctly - the shared browser and desktop, owner attachments, ReviewTargets, supervised services, legal\u002Fpublish\u002Fjudgement commands, Coolify, native sheets, structured decisions, connected tools, native documents and Rooms. Read before the first use of any of them in a session.\n---\n\n# Company tools\n\nThe Runtime has one persistent company browser: the Chromium the owner sees on the company\ncomputer, with its signed-in profile, tabs and downloads. Use it for every interactive or stateful\nbrowser task and for anything the owner may watch, review or take over. In the same supervised\nagent turn, run `restless browser attach` and use the returned WebSocket URL with Playwright\n`chromium.connectOverCDP(endpoint)`. The signed Runtime capability supplies the actor and session,\nand the exact Work and Attempt when the turn has them; do not provide those IDs yourself. Use the existing context, open your\nown tab, and close or disconnect only what you opened. Always run `restless browser release` in a\n`finally` block. An attach waits briefly when another Work holds the browser; if it returns\n`browser_busy`, retry from the same live Attempt after the other Work releases it. If it returns\n`attempt_ended`, stop and let the accountable actor resume Work. Never kill the browser process or\nconnect to port 9222 directly. When the owner\ncontrols the browser, pending CDP actions return an `owner_controls` error and are never replayed;\nafter control returns, inspect the current page state and verify any action that was in flight before\ndeciding what to do next. Do not start a separate browser to get around owner control. Launch a\nthrowaway headless Chromium\nonly for stateless, reproducible captures, such as the fixed viewports in web-native-review.\nFor a CommonJS Playwright script, resolve the globally installed package with\n`NODE_PATH=\"$(npm root -g)\" node your-script.cjs`; then call `require('playwright').chromium.connectOverCDP(endpoint)`.\nThe same owner-control rule covers visible-desktop automation: do not use `xdotool` or `wmctrl` to\nfocus, type into, move, or otherwise take over the shared desktop while the owner controls the browser.\n\n## The company computer, sign-ins and the cards that ask for them\n\nThe company computer is this company's own persistent Linux machine: its files under `\u002Fcompany`,\nits processes, its desktop and its one browser. It is separate from every other company and from\nthe owner's own devices, so it is already the safe place to try something. Do not ask the owner to\nsign in to a test site, or for another machine, to get a \"sandbox\"; say plainly when a test would\ncause a real external effect instead.\n\nA website sign-in lives in the company browser's profile. The owner signs in there once, through\nthe Inbox card or Company › Computer, and every agent of this company then uses that session\nthrough `restless browser attach`. A sign-in on the owner's own computer or phone does not reach\nit. Two different cards can ask for a sign-in, and each closes in its own way:\n\n- **A sign-in handoff** (`restless work handoff --work \u003Cid> --category identity`): the owner signs\n  in in the company browser, at the page you left open. Use this when your Work drives the company\n  browser. It closes when the owner confirms it on the card, or when you are asked to recheck, see the\n  site signed in and record it with `restless work resolve-handoff --handoff \u003Cid> --state resolved\n  --resolution \u003Cwhat you checked>`. Name every site the Work needs in the one handoff.\n- **An account request** (`restless apps ask-account`): the owner adds an account in Settings ›\n  Accounts and gives it to the company; it then reaches you as that account's own tools in your\n  next session. Use it for an API key, GitHub, or a login the owner wants to keep as an account.\n  It closes only when the owner adds the account from the card or declines, when the Work that\n  asked ends, or after a week. Signing in in the company browser does not close it.\n\nRaise one card for one sign-in, never both kinds for the same site, and not a second card when an\nopen one already covers it. If a request you filed is no longer needed (the site is signed in in\nthe company browser, a handoff covers it, the Work changed), take it back with `restless apps\nwithdraw-account --site \u003Csite> --reason \u003Cwhat you saw>`. Never tell the owner to dismiss a card the\ncompany raised, and never say a sign-in worked without trying the site.\n\nStart shared visible applications on `DISPLAY=:1`; that is the company desktop the owner can see.\nDo not confuse it with a display leased through the Work resource gate: use the lease's exact display\nonly for that bounded Work. Use the installed Browser, Terminal, and Godot desktop launchers or their\nhelpers (`focus-company-chromium`, `start-company-terminal`, and `start-company-godot`) when they fit;\ndo not invent a second desktop or browser. Run `company-tools` (or `company-tools --json`) to observe the installed named tool inventory\nand resolved paths and purposes before choosing a tool. It\nincludes the normal Runtime CLIs and harnesses; probe\nthe selected command's help before relying on it.\n\nA file the owner sends arrives as a read-only path under `\u002Fvar\u002Flib\u002Frestless-owner-attachments\u002F`,\nnamed after the original file. Read it in place: `pdftotext -layout file.pdf -` for a PDF (and\n`pdftoppm -png` to look at a scanned page), `docx2txt file.docx -` for Word, `xlsx2csv file.xlsx` for\nExcel, and the ordinary image reader for a photo. Copy it beneath `\u002Fcompany` before changing it.\n\nAn interactive or stateful session belongs in the shared company desktop\u002Fbrowser. A ReviewTarget is\ndifferent: its loopback HTTP preview is a read-only delivery surface at a concrete URL such as\n`http:\u002F\u002F127.0.0.1:\u003Cport>\u002F`. It permits only GET\u002FHEAD, carries no owner cookies or browser-control\nchannel, and never upgrades WebSockets; ports 5901, 6080, 9222, and 9223 are reserved and cannot be\nReviewTargets. Use a live loopback URL only for a durable preview; use a static displayable file\nbeneath `\u002Fcompany` for a native HTML\u002FPDF\u002Fimage\u002Faudio\u002Fvideo\u002Ftext outcome. Link the chosen target as\nartifact kind `review_target`. A Work declared `--owner-review`\nmust provide exactly one available ReviewTarget and pass its `review-target-live-probe` gate; an\nordinary linked target is evidence only, not owner delivery.\n\nPages people open (a concept page, a site, a deck) show places on a live map, never a picture of\none. Link each place with `https:\u002F\u002Fwww.google.com\u002Fmaps\u002Fsearch\u002F?api=1&query=\u003Cplace, URL-encoded>`\nand `target=\"_blank\" rel=\"noopener\"`: the Library and review frames open new tabs, but a map link\nfollowed inside the frame is refused. Where a map helps, embed it so it zooms and pans, with that\nlink beside it: `\u003Ciframe src=\"https:\u002F\u002Fwww.google.com\u002Fmaps?q=\u003Cplace, URL-encoded>&output=embed\"\ntitle=\"Map of \u003Cplace>\" loading=\"lazy\" style=\"border:0;width:100%;height:360px\">\u003C\u002Fiframe>`. It needs\nno key.\n\nUse the company supervisor for any service that must survive the current agent: put this Work's\n`*.conf` file in `\u002Fcompany\u002Fservices\u002Fsupervisor`, then use `company-supervisorctl reread`, `update`,\nand `status`. On cleanup, stop the Work-owned service, remove that exact `*.conf`, then run `reread`,\n`update`, and `status` again so it cannot return on the next supervisor update. A detached shell is\nneither durable service management nor cleanup. Preserve shared desktop, browser, data, and other\nWork's services.\n\nUse `restless legal show` to inspect the safe authority-owned legal profile; do not infer legal\nidentity from a company name or a runtime file. `restless publish candidate` binds a source artifact\nto a service manifest; `restless publish request` records the audience and resource envelope without\nrunning a provider. `restless judgement --as \u003Cactor>` reads that actor's judgement queue. These\ncommands have separate purposes; none grants authority to publish, attest, or decide for the owner.\n\nFor Coolify work, prefer the installed `coolify` CLI explicitly. Probe it and the exact subcommand's\n`--help`, prefer JSON output for inspection, and verify the selected context before acting. Never\nassume or expose a context token. Use the Coolify dashboard only to create or authorize credentials,\nor when the probed CLI\u002FAPI surfaces do not support the required operation.\n\nNative company spreadsheets are available through `restless sheet --help`.\nUse an observed revision and a retained idempotency key for each edit, and give\ncollaborating agents explicit sheet access. Read evaluated ranges for formula\nresults. Prefer `update_record` with stable record IDs when rows may have moved.\nThe human link is `\u002F{company}\u002Fwork\u002Fsheets?sheet={sheet_id}`.\n\nFor repeated, bounded choices over many similar items (triaging leads, routing support email,\nflagging spam, sorting a queue), `restless decide` asks a structured decision model typed\nquestions and returns answers with probabilities in under a second for a tiny fraction of a model\nturn. Read `restless decide --help`. Treat a close call as uncertain and look at that item\nyourself. Never use it to judge the quality of work, to write, or to decide anything that needs\nauthority or the owner.\n\nWhen a connected app fails or a tool you expected is missing, run `restless tools list`: it shows\neach app's state, why it fails, what a local tool last printed, and which tools you may call. A\nlocal tool is a command the company runs; fix what you can yourself (a package, its files under\n`\u002Fcompany\u002Ftools`, a typo in how it starts), then `restless tools check \u003Cname>` starts it again and\nreports what it offers. Adding a new app or changing its sign-in or secrets is the owner's call:\nbring one prepared app request instead.\n\nNative company documents are available through `restless document`; inspect\n`restless document --help` and the chosen subcommand's help before creating, reading, editing,\ncheckpointing, or requesting review of one.\nThe canonical human UI link for a document is `\u002F{company}\u002Fwork\u002Fdocuments?document={document_id}`;\nnever fabricate a `\u002Fdocuments\u002F...` URL.\nWhen producing a shared document for a human, give that recipient `edit` access unless the request\ncalls for read-only delivery. Its creating actor owns it and must share with the exact authenticated\nhuman identity resolved for that recipient before requesting collaboration, review, or handoff. Use the current metadata\nrevision and a stable key; do not assume the recipient is literally `owner` in a company with network\nmembers. Give every Staff reviewer the explicit access their check needs before asking them to read\nor checkpoint it. A human native-review recipient must already have `edit` access. A creator's\nownership does not transfer to colleagues. When a document may return to Exec for a bounded owner\nrevision, share the required access with Exec before delivery as well. If Exec receives that revision\nwithout access, find the document-owning producer through its Work and direct that producer to make\nthe bounded update and share the named recipient; do not abandon the owner request or ask the human\nto repair internal access.\n\n## Shared documents and Rooms\n\nUse `restless document --help` for native shared documents and `restless room --help` for group\nconversations. These are Core company tools; they do not require an external Docs or Slack account.\nCreate native documents from a Markdown or editor-JSON file, retain the returned document ID, and\nexplicitly share access with each exact authenticated human identity and participating colleague. Reuse the same command UUID\nand identical payload after a transport failure. A `document snapshot` is a named checkpoint and\nexplicitly excludes uncheckpointed live edits; never describe it as the current collaborative body.\nUse `document read` for the live body and its block hashes, then `document edit --operations-file\nPATH --key UUID` for guarded insert\u002Freplace\u002Fdelete operations. The complete operation shapes,\nexamples and conflict\u002Fretry contract are installed in `restless document edit --help`. Preserve block IDs and supply the\nobserved hash when replacing or deleting. Core retains the exact prepared edit for retries, so\nkeep its original key and content after a lost response. Reread and review stale-block conflicts.\nA successful edit is applied and persisted synchronously; it does not need a checkpoint to save.\nFor an explicit owner request to make a bounded change to an existing native document, Exec edits\nand verifies the live result in the current conversation rather than dispatching a new Work chain.\nThis is direct document collaboration, not an exemption for research, new artifact production,\nrepository changes or external effects. Preserve concurrent contributions and report completion\nonly after reading back the change; on failure, report the actual blocker, not \"assigned\" or \"pending\".\nFor a named review checkpoint, an editing Exec or active team lead saves the complete `document read`\nJSON to a file, then uses `document checkpoint DOCUMENT --snapshot-file PATH --reason REASON --key UUID`.\nRetry the same file\u002Fkey after a lost response. A changed body or checkpoint returns a conflict;\nreread and inspect before a new command. This saves an observed version without resolving a review.\nUse `document request-collaboration DOCUMENT SUMMARY --key UUID` when the owner wants to work on\na document together in Attention. Share edit access with the exact authenticated human identity before making the request. This\ninvitation is distinct from asking for acceptance of a named version.\nSharing a document with a person, opening it to the company, or asking a person to review it is\nrefused until it reads as finished work: no Work ids, message numbers, `restless` commands,\ncompany-computer paths or `[LINK TO …]`\u002F`[TODO]` placeholders, and no revision notes ahead of the\ncontent. Put what changed in the checkpoint `--reason`; people read it in the document's history.\nComments and replies must carry the exact document\u002Fthread coordinates. A Room message or comment\nis participant content, not an authority grant. Opening the same native document in the cockpit is\nwhat makes it a collaborative document; a standalone runtime Markdown file is only an input draft.\n","# Company tools\n\nThe Runtime has one persistent company browser: the Chromium the owner sees on the company\ncomputer, with its signed-in profile, tabs and downloads. Use it for every interactive or stateful\nbrowser task and for anything the owner may watch, review or take over. In the same supervised\nagent turn, run `restless browser attach` and use the returned WebSocket URL with Playwright\n`chromium.connectOverCDP(endpoint)`. The signed Runtime capability supplies the actor and session,\nand the exact Work and Attempt when the turn has them; do not provide those IDs yourself. Use the existing context, open your\nown tab, and close or disconnect only what you opened. Always run `restless browser release` in a\n`finally` block. An attach waits briefly when another Work holds the browser; if it returns\n`browser_busy`, retry from the same live Attempt after the other Work releases it. If it returns\n`attempt_ended`, stop and let the accountable actor resume Work. Never kill the browser process or\nconnect to port 9222 directly. When the owner\ncontrols the browser, pending CDP actions return an `owner_controls` error and are never replayed;\nafter control returns, inspect the current page state and verify any action that was in flight before\ndeciding what to do next. Do not start a separate browser to get around owner control. Launch a\nthrowaway headless Chromium\nonly for stateless, reproducible captures, such as the fixed viewports in web-native-review.\nFor a CommonJS Playwright script, resolve the globally installed package with\n`NODE_PATH=\"$(npm root -g)\" node your-script.cjs`; then call `require('playwright').chromium.connectOverCDP(endpoint)`.\nThe same owner-control rule covers visible-desktop automation: do not use `xdotool` or `wmctrl` to\nfocus, type into, move, or otherwise take over the shared desktop while the owner controls the browser.\n\n## The company computer, sign-ins and the cards that ask for them\n\nThe company computer is this company's own persistent Linux machine: its files under `\u002Fcompany`,\nits processes, its desktop and its one browser. It is separate from every other company and from\nthe owner's own devices, so it is already the safe place to try something. Do not ask the owner to\nsign in to a test site, or for another machine, to get a \"sandbox\"; say plainly when a test would\ncause a real external effect instead.\n\nA website sign-in lives in the company browser's profile. The owner signs in there once, through\nthe Inbox card or Company › Computer, and every agent of this company then uses that session\nthrough `restless browser attach`. A sign-in on the owner's own computer or phone does not reach\nit. Two different cards can ask for a sign-in, and each closes in its own way:\n\n- **A sign-in handoff** (`restless work handoff --work \u003Cid> --category identity`): the owner signs\n  in in the company browser, at the page you left open. Use this when your Work drives the company\n  browser. It closes when the owner confirms it on the card, or when you are asked to recheck, see the\n  site signed in and record it with `restless work resolve-handoff --handoff \u003Cid> --state resolved\n  --resolution \u003Cwhat you checked>`. Name every site the Work needs in the one handoff.\n- **An account request** (`restless apps ask-account`): the owner adds an account in Settings ›\n  Accounts and gives it to the company; it then reaches you as that account's own tools in your\n  next session. Use it for an API key, GitHub, or a login the owner wants to keep as an account.\n  It closes only when the owner adds the account from the card or declines, when the Work that\n  asked ends, or after a week. Signing in in the company browser does not close it.\n\nRaise one card for one sign-in, never both kinds for the same site, and not a second card when an\nopen one already covers it. If a request you filed is no longer needed (the site is signed in in\nthe company browser, a handoff covers it, the Work changed), take it back with `restless apps\nwithdraw-account --site \u003Csite> --reason \u003Cwhat you saw>`. Never tell the owner to dismiss a card the\ncompany raised, and never say a sign-in worked without trying the site.\n\nStart shared visible applications on `DISPLAY=:1`; that is the company desktop the owner can see.\nDo not confuse it with a display leased through the Work resource gate: use the lease's exact display\nonly for that bounded Work. Use the installed Browser, Terminal, and Godot desktop launchers or their\nhelpers (`focus-company-chromium`, `start-company-terminal`, and `start-company-godot`) when they fit;\ndo not invent a second desktop or browser. Run `company-tools` (or `company-tools --json`) to observe the installed named tool inventory\nand resolved paths and purposes before choosing a tool. It\nincludes the normal Runtime CLIs and harnesses; probe\nthe selected command's help before relying on it.\n\nA file the owner sends arrives as a read-only path under `\u002Fvar\u002Flib\u002Frestless-owner-attachments\u002F`,\nnamed after the original file. Read it in place: `pdftotext -layout file.pdf -` for a PDF (and\n`pdftoppm -png` to look at a scanned page), `docx2txt file.docx -` for Word, `xlsx2csv file.xlsx` for\nExcel, and the ordinary image reader for a photo. Copy it beneath `\u002Fcompany` before changing it.\n\nAn interactive or stateful session belongs in the shared company desktop\u002Fbrowser. A ReviewTarget is\ndifferent: its loopback HTTP preview is a read-only delivery surface at a concrete URL such as\n`http:\u002F\u002F127.0.0.1:\u003Cport>\u002F`. It permits only GET\u002FHEAD, carries no owner cookies or browser-control\nchannel, and never upgrades WebSockets; ports 5901, 6080, 9222, and 9223 are reserved and cannot be\nReviewTargets. Use a live loopback URL only for a durable preview; use a static displayable file\nbeneath `\u002Fcompany` for a native HTML\u002FPDF\u002Fimage\u002Faudio\u002Fvideo\u002Ftext outcome. Link the chosen target as\nartifact kind `review_target`. A Work declared `--owner-review`\nmust provide exactly one available ReviewTarget and pass its `review-target-live-probe` gate; an\nordinary linked target is evidence only, not owner delivery.\n\nPages people open (a concept page, a site, a deck) show places on a live map, never a picture of\none. Link each place with `https:\u002F\u002Fwww.google.com\u002Fmaps\u002Fsearch\u002F?api=1&query=\u003Cplace, URL-encoded>`\nand `target=\"_blank\" rel=\"noopener\"`: the Library and review frames open new tabs, but a map link\nfollowed inside the frame is refused. Where a map helps, embed it so it zooms and pans, with that\nlink beside it: `\u003Ciframe src=\"https:\u002F\u002Fwww.google.com\u002Fmaps?q=\u003Cplace, URL-encoded>&output=embed\"\ntitle=\"Map of \u003Cplace>\" loading=\"lazy\" style=\"border:0;width:100%;height:360px\">\u003C\u002Fiframe>`. It needs\nno key.\n\nUse the company supervisor for any service that must survive the current agent: put this Work's\n`*.conf` file in `\u002Fcompany\u002Fservices\u002Fsupervisor`, then use `company-supervisorctl reread`, `update`,\nand `status`. On cleanup, stop the Work-owned service, remove that exact `*.conf`, then run `reread`,\n`update`, and `status` again so it cannot return on the next supervisor update. A detached shell is\nneither durable service management nor cleanup. Preserve shared desktop, browser, data, and other\nWork's services.\n\nUse `restless legal show` to inspect the safe authority-owned legal profile; do not infer legal\nidentity from a company name or a runtime file. `restless publish candidate` binds a source artifact\nto a service manifest; `restless publish request` records the audience and resource envelope without\nrunning a provider. `restless judgement --as \u003Cactor>` reads that actor's judgement queue. These\ncommands have separate purposes; none grants authority to publish, attest, or decide for the owner.\n\nFor Coolify work, prefer the installed `coolify` CLI explicitly. Probe it and the exact subcommand's\n`--help`, prefer JSON output for inspection, and verify the selected context before acting. Never\nassume or expose a context token. Use the Coolify dashboard only to create or authorize credentials,\nor when the probed CLI\u002FAPI surfaces do not support the required operation.\n\nNative company spreadsheets are available through `restless sheet --help`.\nUse an observed revision and a retained idempotency key for each edit, and give\ncollaborating agents explicit sheet access. Read evaluated ranges for formula\nresults. Prefer `update_record` with stable record IDs when rows may have moved.\nThe human link is `\u002F{company}\u002Fwork\u002Fsheets?sheet={sheet_id}`.\n\nFor repeated, bounded choices over many similar items (triaging leads, routing support email,\nflagging spam, sorting a queue), `restless decide` asks a structured decision model typed\nquestions and returns answers with probabilities in under a second for a tiny fraction of a model\nturn. Read `restless decide --help`. Treat a close call as uncertain and look at that item\nyourself. Never use it to judge the quality of work, to write, or to decide anything that needs\nauthority or the owner.\n\nWhen a connected app fails or a tool you expected is missing, run `restless tools list`: it shows\neach app's state, why it fails, what a local tool last printed, and which tools you may call. A\nlocal tool is a command the company runs; fix what you can yourself (a package, its files under\n`\u002Fcompany\u002Ftools`, a typo in how it starts), then `restless tools check \u003Cname>` starts it again and\nreports what it offers. Adding a new app or changing its sign-in or secrets is the owner's call:\nbring one prepared app request instead.\n\nNative company documents are available through `restless document`; inspect\n`restless document --help` and the chosen subcommand's help before creating, reading, editing,\ncheckpointing, or requesting review of one.\nThe canonical human UI link for a document is `\u002F{company}\u002Fwork\u002Fdocuments?document={document_id}`;\nnever fabricate a `\u002Fdocuments\u002F...` URL.\nWhen producing a shared document for a human, give that recipient `edit` access unless the request\ncalls for read-only delivery. Its creating actor owns it and must share with the exact authenticated\nhuman identity resolved for that recipient before requesting collaboration, review, or handoff. Use the current metadata\nrevision and a stable key; do not assume the recipient is literally `owner` in a company with network\nmembers. Give every Staff reviewer the explicit access their check needs before asking them to read\nor checkpoint it. A human native-review recipient must already have `edit` access. A creator's\nownership does not transfer to colleagues. When a document may return to Exec for a bounded owner\nrevision, share the required access with Exec before delivery as well. If Exec receives that revision\nwithout access, find the document-owning producer through its Work and direct that producer to make\nthe bounded update and share the named recipient; do not abandon the owner request or ask the human\nto repair internal access.\n\n## Shared documents and Rooms\n\nUse `restless document --help` for native shared documents and `restless room --help` for group\nconversations. These are Core company tools; they do not require an external Docs or Slack account.\nCreate native documents from a Markdown or editor-JSON file, retain the returned document ID, and\nexplicitly share access with each exact authenticated human identity and participating colleague. Reuse the same command UUID\nand identical payload after a transport failure. A `document snapshot` is a named checkpoint and\nexplicitly excludes uncheckpointed live edits; never describe it as the current collaborative body.\nUse `document read` for the live body and its block hashes, then `document edit --operations-file\nPATH --key UUID` for guarded insert\u002Freplace\u002Fdelete operations. The complete operation shapes,\nexamples and conflict\u002Fretry contract are installed in `restless document edit --help`. Preserve block IDs and supply the\nobserved hash when replacing or deleting. Core retains the exact prepared edit for retries, so\nkeep its original key and content after a lost response. Reread and review stale-block conflicts.\nA successful edit is applied and persisted synchronously; it does not need a checkpoint to save.\nFor an explicit owner request to make a bounded change to an existing native document, Exec edits\nand verifies the live result in the current conversation rather than dispatching a new Work chain.\nThis is direct document collaboration, not an exemption for research, new artifact production,\nrepository changes or external effects. Preserve concurrent contributions and report completion\nonly after reading back the change; on failure, report the actual blocker, not \"assigned\" or \"pending\".\nFor a named review checkpoint, an editing Exec or active team lead saves the complete `document read`\nJSON to a file, then uses `document checkpoint DOCUMENT --snapshot-file PATH --reason REASON --key UUID`.\nRetry the same file\u002Fkey after a lost response. A changed body or checkpoint returns a conflict;\nreread and inspect before a new command. This saves an observed version without resolving a review.\nUse `document request-collaboration DOCUMENT SUMMARY --key UUID` when the owner wants to work on\na document together in Attention. Share edit access with the exact authenticated human identity before making the request. This\ninvitation is distinct from asking for acceptance of a named version.\nSharing a document with a person, opening it to the company, or asking a person to review it is\nrefused until it reads as finished work: no Work ids, message numbers, `restless` commands,\ncompany-computer paths or `[LINK TO …]`\u002F`[TODO]` placeholders, and no revision notes ahead of the\ncontent. Put what changed in the checkpoint `--reason`; people read it in the document's history.\nComments and replies must carry the exact document\u002Fthread coordinates. A Room message or comment\nis participant content, not an authority grant. Opening the same native document in the cockpit is\nwhat makes it a collaborative document; a standalone runtime Markdown file is only an input draft.\n",{"name":5,"description":7},"main","74448c875ccc3d826c90b46381cc63698ba769aa","infra\u002Fcompany-image\u002Fskills\u002Fcompany-tools",1,"https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core","https:\u002F\u002Frestless.run","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO","2026-11-14 10:29:34",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add BlueprintLabIO\u002Frestless-core --skill company-tools",{"tool":37,"command":38},"bunx","bunx skills add BlueprintLabIO\u002Frestless-core --skill company-tools",{"tool":40,"command":41},"pnpm","pnpm dlx skills add BlueprintLabIO\u002Frestless-core --skill company-tools","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fcompany-tools\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7AEXHE6CPB3TMHWKEMDWYM7","fixture-note-etiquette","How the company writes a Fixture Notes message. Used only by the connections smoke.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Ftools\u002Ffixture-mcp-provider\u002Ffixtures\u002Fplugin\u002Fskills\u002Ffixture-note-etiquette\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7AEXC9H7TTENFY1S87TQZF5","web-native-review","Prepare or independently review a rendered website against its outcome contract and a mature ground-truth reference. Use for landing pages, product sites, blogs, documentation sites, or other browser-native outcomes; do not use to judge source code alone or turn mechanical layout facts into a taste score.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fweb-native-review\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7AEX8KTGCGTDHKMKRMV25AS","scenario-evidence","Run a versioned Runtime scenario, probe its real capabilities, preserve compact evidence, and prepare its native review target. Use for a project outcome that benefits from repeatable setup\u002Frun\u002Fassertion\u002Fevidence—not to choose a plan, team, or business verdict.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fscenario-evidence\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7AEX433AM2YZ08ST66G3FF5","research","Answer a question the company needs to decide on with a sourced brief - market facts, a technology, a regulation, an audience, a price, a supplier. Use when an answer must be found and checked on the web or in documents before acting; do not use for a quick lookup a single source settles, or for competitor landscapes (use competitor-research).","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AEWYCTNC5VF57C9PQF1X4W","reference-led-reset","Reset a rejected or repeatedly drifting outcome into a genuinely fresh Work Attempt grounded in ordered authoritative references. Use when the owner asks to start over, when qualitative defects survive revision, or when a mechanically valid result conflicts with the product or brand source of truth. Do not use for an ordinary bounded repair that should preserve the current candidate.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Freference-led-reset\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AEWV2KP5JM50T3S7VD7HR9","publish-git","Safely reconcile, verify, and publish Git refs through the governed Restless effect path. Use for pushes or deployments driven by a Git push; do not use for read-only fetches, local Git work, or provider API administration.","https:\u002F\u002Fgithub.com\u002FBlueprintLabIO\u002Frestless-core\u002Fblob\u002Fmain\u002Finfra\u002Fcompany-image\u002Fskills\u002Fpublish-git\u002FSKILL.md",[],[]]