Share Skills

Choose or create a Skill

A Skill is a reusable instruction pack: when to use it, what steps to follow, what result to produce, and what to check. Use one for recurring work such as preparing a customer brief, reviewing a release note, or applying a team writing standard.

1. Write the instructions as a managed document with a clear title and scope.
2. Open the document action Use as skill….
3. Review its name, identifier, description, and supported tools, then complete the registration.
4. Use Update skill… to publish a later change to an existing Skill.

The upload dialog also offers Use this as a skill for a single file. A filename containing “skill” can select this automatically; turn it off when the file is only reference material.

When you ask an agent in chat to bring in a file whose name contains “skill”, the agent registers it as a Skill at once and tells you its identifier and link. This works when you are signed in to the agent’s connection, not with an agent token; with an agent token, the agent gives you the link so you can use Use as skill….

A short Skill can define its trigger, inputs, output, and checks. Adapt this example to your team before registering it.

Install on a particular tool

1. Open the desktop app’s Skills → Browse hub.
2. Choose the Skill and the detected tool or tools that should receive it.
3. Install and check the per-tool result.
4. Start a new conversation or reload the tool when needed so it discovers the installed instructions.

Browse hub lists the System Skills and each workspace Skill whose source document you can see. A Skill whose source document is private to someone else does not appear until that document is shared with you. A workspace owner or admin role does not show it.

A Skill with the Optional install policy is not installed on every computer. Members install it when they choose. An owner or admin can change its install policy so that members get it on their next sync; see Set a Skill’s install policy. The desktop Installed tab shows this device’s state. A tool missing from the computer must be installed before ArtifactBridge can place Skills in it.

Set a Skill’s install policy

Each workspace Skill has an install policy. The Install policy column in Settings → Agent → Skills shows it.

• Optional: members install it when they choose.
• Preinstalled: it installs on the tools of every member on their next sync. A member can remove it, and it stays removed.
• Required: it installs on the tools of every member on their next sync and stays installed. Members can’t remove it with ArtifactBridge. Files inside other tools can’t be locked, so a member can still delete them by hand.

System Skills ship with ArtifactBridge. Their install policy is always Required, and nobody can change it, owners and admins included. They install on every member’s tools on the next sync, and members can’t remove them with ArtifactBridge.

To read what each install policy does, point to the info icon after the Install policy column title, or move keyboard focus to it.

Only a workspace owner or admin can change the install policy. Select it in the row’s Install policy column and choose the new one. The dialog shows the consequence before anything changes: how many members get the Skill, how many had chosen not to install it, and who won’t get it right away. Members with automatic refresh off and members with older app versions don’t get it until they act. Running agent sessions keep what they loaded. Choose Set to confirm, or Cancel to change nothing.

The dialog can stop the change:

• Every member must be able to see the Skill’s source document. If some members can’t, the dialog says how many and offers Open sharing. Share the document, then choose the install policy again.
• A Skill that a security scan blocked can’t be Preinstalled or Required.
• A Skill whose security scan found a caution needs you to confirm that you reviewed it.
• A Deactivated Skill keeps its install policy, but delivery is paused. Activate it before you choose an install policy.

When more than 15 Skills would be Preinstalled or Required, the dialog warns you. Every member’s agents load the description of each of these Skills, and many of them can crowd the agents’ context. The warning does not stop the change.

A lower install policy changes nothing on members’ machines. Installed copies stay, as ordinary installs that members can remove. From Required to Preinstalled, earlier choices not to install it apply again. Members get no notice for a lower install policy. A raise sends each other member a notice in the Inbox; see skill notices.

If the connection drops after you choose Set, the dialog says it couldn’t confirm the change. Choose Check current state. ArtifactBridge reads the current install policy and does not send the change again. If someone else changed it first, the dialog names who changed it and offers Show current policy.

Install a Skill as a member

In Settings → Agent → Skills, members see each Skill’s install policy, not other members’ counts. Choose Install on an Optional Skill to request it on your tools. The row then says Requested, and the Skill installs on your next sync. Nothing is installed at that moment. If you removed a Preinstalled Skill, Install on my tools clears that choice.

To stop a request, open the row’s More actions menu and choose Cancel install request…. Canceling stops automatic installation on all your machines. Copies already installed stay; remove them with Uninstall in the ArtifactBridge app on each machine. If Install or Cancel couldn’t be confirmed, the row offers Check again, which sends the same request again. ArtifactBridge never records it twice.

Check install status

For a Preinstalled or Required Skill, owners and admins see a count in the Install policy column, such as 12 of 14 members on v7. Members never see this count. Choose it to open the install status. It has three tabs. Needs attention lists the members who are not on the current version, each with the reason, such as Install failed, Refresh off, or No report, and what that member can do. The tab named for the current version, such as On v7, lists the members who have it. Members who chose not to install the Skill, and members it does not apply to, are under Not counted.

The status comes from the reports of members’ ArtifactBridge apps. A member may use machines that have not reported, and a new install policy shows Waiting until the first reports arrive. For another member’s failed install, the status shows the steps and the command that member can run. It does not run anything on their machine. Your own failed install offers Retry.

Install policies on your computer

The ArtifactBridge app installs the Skills your workspace expects when it refreshes your Skills (every 30 minutes while automatic refresh is on). It installs only on the tools in your refresh tool list that are on this computer. It never overwrites a copy that you changed, and it never writes into a folder of the same name that ArtifactBridge did not install.

• Automatic refresh off: nothing is installed on its own. Run artifactbridge skills apply-workspace to install the expected Skills now. It does not turn automatic refresh on. Add --dry-run to see the plan first.
• System: artifactbridge skills uninstall refuses to remove it (exit code 5), also when this computer is offline. ArtifactBridge checks the workspace that installed each copy. If it can't check a copy that has a System Skill’s name, it refuses until it can connect to that workspace.
• Required: artifactbridge skills uninstall refuses to remove it (exit code 5). If you delete its whole folder, or every file in it, the next refresh puts the files back. If you delete only some files, the copy shows Files missing, and the next refresh does not change it. Choose Repair in the desktop app, or run artifactbridge skills repair <slug>, to put back the deleted files.
• Preinstalled or requested: when you uninstall it from a tool, it stays removed from that tool on all your computers. Install it again to undo that. If you delete its whole folder by hand, it stays removed on this computer only.
• Remove a requested Skill everywhere: artifactbridge skills uninstall <slug> --cancel-request also cancels your install request. The command prints skills cancel <slug>: with cancelled, queued (sent when this computer next reaches ArtifactBridge) or refused.
• Refresh tool list: artifactbridge skills sync --auto clients claude,codex,grok sets the tools that get workspace Skills. It does not change automatic refresh.
• What is expected here: artifactbridge skills expected lists the Skills your workspace expects on this computer and what the next refresh would do.

Your app tells workspace managers which workspace Skills and versions it has, whether automatic refresh is on, and its app version. It sends no file names, paths, or Skill content. Older app versions do not install expected Skills and can still remove Required ones.

Workspace Skills in the desktop app

On each member’s computer, the ArtifactBridge app installs the Skills that the workspace preinstalls or requires, on the next sync. In the Skills view, a badge under the Skill’s name shows its install policy.

• System: the badge says System skill, and the row offers no Uninstall.
• Required: the badge says Required by workspace, and the row offers no Uninstall. artifactbridge skills uninstall refuses it too. If a member deletes its folder by hand, the next sync restores it when the path is free.
• Preinstalled: the badge says Preinstalled by workspace. Uninstall removes it at once, without a question, because Install brings it back. Removing it from a tool stops it from coming back on that tool, on all your machines. To get it back, choose Install on that tool.
• Requested: Remove from all my tools cancels your install request and removes the copies on this computer. Copies on your other machines stay until you remove them there. If this computer is offline, the cancellation is sent when it is next online.
• A Skill that is deactivated or blocked keeps its install policy, but delivery is paused, and the row shows no policy badge. You can uninstall it; if it is activated again, it comes back.

The badges also show whether a Skill is Legacy or Deactivated and its safety check result. Choose Details to read the reason, who accepted the check result and why, when the check ran, and the findings. When a Skill has a replacement, the row ends with Use and the replacement’s name, its check result and its own install button. When the replacement is on every tool that can take it, the row says Replaced by instead.

When automatic refresh is off on a computer, the app shows which Skills the workspace expects there and offers Install now, which runs artifactbridge skills apply-workspace. Installing now does not turn automatic refresh on. A folder with the same name that ArtifactBridge did not write is never overwritten; the app names the folder and leaves it as it is.

The app tells workspace managers which workspace Skills and versions it has, whether automatic refresh is on, and its app version. It sends no file contents or paths. See Settings → Advanced → What your workspace sees.

Update or remove local Skills

Apply an available update from the desktop Skills view. To keep installed Skills current on a schedule, enable Settings → Advanced → Keep skills up to date. Check the last scheduled result there. Remove a Skill from a selected tool using the local uninstall action and confirm the tools affected. This does not delete the workspace’s source document.

When your access to a Skill’s source document ends, the Skill leaves Browse hub and one-time use on the next read. Files that are already installed on your computer stay until you uninstall them.

If you or your agent change an installed Skill on your computer, updates for that copy pause and your change stays. See Keep your changes to an installed Skill.

Mark a Skill as legacy, deactivate it, or activate it

Workspace owners, admins, and the owner of the Skill’s SKILL.md document manage its lifecycle in Settings → Agent → Skills. Open the ⋯ menu on the Skill’s row. Other members do not see this menu.

• Mark as legacy… keeps the Skill working and updating. Enter a message of up to 280 characters. A replacement is optional. Members and agents see the message and “Use replacement instead.” Use Edit legacy mark… or Remove legacy mark to change it later.
• Deactivate… stops ArtifactBridge from delivering the Skill now. Enter a reason. A replacement is optional. The dialog shows how many tool installs and members the deactivation affects. On their next sync, up-to-date desktop apps move the Skill out of each recorded tool into the ArtifactBridge Trash on that computer. They do not delete the files.
• Activate… delivers the Skill again. On their next sync, desktop apps restore copies from the Trash when the path is free. If a folder is already at that path, the app does not overwrite it, and the activation report shows a conflict. Activate also clears an earlier legacy mark.

Who can activate. After an owner or admin deactivates a Skill, only an owner or admin can activate it. After the SKILL.md document owner deactivates it, the current document owner or an admin can activate it. An admin can use Deactivate as admin… to take over a document owner’s deactivation. Nothing moves again on the computers. If the SKILL.md document is archived, the Skill stays deactivated until someone unarchives the document. A Skill that is deactivated only because its document is archived has no ⋯ menu: unarchive the document to activate it. If a manager also deactivated it, the menu shows Remove deactivation…, which clears only the deactivation that a manager set.

Status and reports. The Status column shows Active, Legacy, or Deactivated. Move the pointer over the status, or move the keyboard focus to it, to see the cause, the reason, the replacement, and who acted and when. The table hides deactivated Skills until you turn on Show deactivated. A deactivated Skill that you still have installed stays in the list. After a deactivation or activation, View lifecycle reports in the row menu shows what the members’ tools reported for that operation: reported removed, problem, or no report after a deactivation; reported restored, conflict, failed, or no report after an activation. A member may use more computers than have reported.

What members do. On a legacy Skill that you have installed, Install replacement asks your desktop app to install the replacement on the same tools. On a deactivated Skill that you still have, Uninstall asks your desktop app to delete it from those tools on its next sync, including any copy in the Trash. If the Skill is activated later, it does not come back for you. The SKILL.md page shows the same actions in its Skill section.

The ArtifactBridge Trash and its limits. A deactivation cannot reach every copy at once. Sessions that are already running keep the Skill until they end. Offline computers change when they reconnect. Older desktop apps, installs from before this feature that the app cannot verify, and copies made outside ArtifactBridge stay until the member removes them. Members who lost access to the document keep their copy. If you delete the SKILL.md document before the computers sync, they keep their copy. The delete dialog warns you when members have not reported removal. A copy stays in the Trash until the member uninstalls the Skill. Agents cannot deactivate or activate a Skill. An agent can read a legacy Skill with its notice, and it gets the reason instead of the content of a deactivated Skill.

Keep your changes to an installed Skill

ArtifactBridge records the files that it writes for each Skill on each tool. Before an update, an install, a retry, or an uninstall, it compares the Skill folder on your computer with that record. If you or your agent changed, added, or deleted a file, ArtifactBridge does not change the folder. It keeps the copy as it is and pauses updates for that copy only. A copy with deleted files and no other change shows Files missing, not Edited locally. Other Skills and other tools continue to update. Changes to line endings and system files such as .DS_Store are not changes.

• Desktop app. The Skill shows once, under Updates paused, with the label Edited locally. Point to the tool count on the row to see which tool has the changed copy. Select Review change on that row. The review shows the changed lines and three actions: Discard, Keep mine, and Propose update or Update shared skill. Select Skills above the Skill name, or Skills in the sidebar, to go back to the list. Keep mine keeps the copy. The Skill stays under Updates paused with the label Local edit kept, and Review change opens the copy again. Changed ArtifactBridge guidance, and a changed copy that has no row under Updates paused, show under Local changes. Discard asks for confirmation and saves a backup before it restores the team version. An update or uninstall from the app that finds a changed copy shows “Updates paused” or “Not removed”. This is not a failure. A Skill with deleted files shows under Files missing with a Repair button, also when your workspace requires it.
• Terminal. artifactbridge skills update shows held <skill> (<tool>): edited locally and continues with the other Skills. A command that names the Skill (skills update <skill>, skills install, skills retry, or skills uninstall) stops for that copy with the code local_edit_held. Exit code 3 means that the command kept at least one copy as it is and no copy failed. Other tools in the same command can still be written.
• Scheduled updates. The update log shows held <skill>: edited locally (<tool>). The last run counts held copies separately from failures, so a held copy does not make the run fail.

Review a local edit. artifactbridge skills changes list --local --json lists local edit metadata without a network request. It does not read staged changes or send your files. Open an item in the desktop app, or run artifactbridge skills changes show <id> --json, to check the current team version and see the exact contribution that can be sent. Propose update is available only for a clean combination of the changes to SKILL.md. Changes to other files, including added files that an earlier Discard kept, prevent it. The desktop app explains why the change cannot be shared and still offers Keep.

How your change is shared. The document behind the Skill decides. If the document is a working document and you created it, Update shared skill replaces Propose update. One click updates the shared skill, and people who installed it may receive this version. The update adds one new version of the document. Your copy then takes the shared version, which holds your change and any lines the team changed in the meantime. A backup of your copy is saved first. The copy is no longer a local change, and its updates continue. If someone changed the shared skill again right after your update, the copy stays under Updates paused. Earlier versions stay, the Skill’s safety checks still apply, and no proposal is created. In every other case, including every governed document, Propose update files an ordinary proposal, also for a working document that another member created. The document’s review mode does not change, and anyone in the workspace can decide the proposal in the Inbox, as with every change. If the owner or the review mode changes after you checked the change, the app shows the current change again and asks you to confirm. It never switches between an update and a proposal on its own.

After you share. When a proposal is filed, the copy shows Sent for review, and its main button is View proposal. That button opens the proposal from this copy in the Inbox. Keep or discard local copy in the row’s menu still opens Keep mine and Discard. If you change the copy again while the proposal is open, the main button is Review change again, and a View proposal link still opens the earlier proposal. If the result of a share is unknown, the main button is Check again. When the proposal is accepted, rejected or closed, the row no longer shows Sent for review. A refused share says why, for example that a safety check needs a person to review the change, and your files stay as they are.

Keep, send, or discard. artifactbridge skills changes keep <id> works offline. Send uses skills changes send <id> --confirm <digest>. Discard uses skills changes discard <id> --confirm <discard-digest>. Both digests come from Show. If your copy or the team version changed, review the current item and confirm again. A lost connection after Send can leave the result unknown. Check again retries the same confirmed change. It does not create a second proposal or a second version for that retry. Only a person can Send, Update or Discard a local edit. Built-in Skills and ArtifactBridge guidance can be kept or restored locally; they cannot be sent for review.

When the team version moves. A kept copy asks you once when a new team version is accepted, and once when your own proposal is accepted, rejected or closed. The scheduled refresh checks a sent proposal at most every five minutes. If the team accepted exactly your copy, ArtifactBridge updates its record silently and nothing on disk changes. While a proposal is open, an update never removes its record. Offline, Show compares your copy with the last team version this machine checked; Send and Discard wait until you are online. After Discard, Show saved copy opens the saved files. When an install stops at a folder that ArtifactBridge did not install, the tray offers Move aside and install. When a removal keeps an edited copy, it offers Back up and remove. Copies installed before this update get one Link prompt for the selected workspace. Nothing runs until you click.

Replace your change with the team version. Add --discard-local, for example artifactbridge skills update <skill> --clients claude --discard-local. ArtifactBridge first makes a backup of the copy and shows where the backup is. Then it writes the team version. Files that you added stay in the folder, and updates continue. A file that you added with the same name as a new team file goes into the backup and is then replaced. If a folder or a link is in that place, the command stops with path_occupied: move it, then run the command again. skills uninstall <skill> --discard-local also makes a backup before it removes the files that ArtifactBridge installed. Only a person can use --discard-local and --move-aside. When an agent runs them, the command stops with requires_person and changes nothing.

Put back deleted files. artifactbridge skills repair <skill> --clients claude writes the deleted files again, with the content that ArtifactBridge installed. It works offline. Files that you changed or added stay as they are, and the installed version does not change. If the installed files are no longer on your computer, the command stops with repair_unavailable: install the Skill again.

Get your change back. artifactbridge skills restore-backup <skill> --clients claude puts back the newest complete backup. Use --at <backup-id> for an older one. It works offline. It does not overwrite a file that you added. After a restore, the copy shows as changed again and its updates stay paused. Backups are in the ArtifactBridge state folder, in skills/backups/. ArtifactBridge keeps each backup for 30 days, and always keeps the last five for each copy. Backups count toward the size of the state folder. If the files that ArtifactBridge must back up are larger than 100 MB in total, it makes no backup and the command changes nothing (backup_failed). Folders that stay in place, described below, do not count toward this limit.

Folders that ArtifactBridge leaves in place. A folder in a Skill folder that ArtifactBridge did not install, such as node_modules/, .git/, or .venv/, stays where it is. ArtifactBridge never writes into it or removes it, and backups do not copy it. The backup lists it as kept in place. ArtifactBridge does not follow links: if a Skill folder, or a folder in it, is a link, the copy is not written.

A folder that ArtifactBridge did not install. If a Skill folder already exists and ArtifactBridge did not install it, an install stops with target_not_owned. Add --move-aside to move the folder into the state folder, in skills/moved-aside/, and then install. ArtifactBridge checks every moved file and never deletes a moved folder. artifactbridge doctor shows how many moved folders there are and where. The folder must be on the same disk as the state folder; if not, the command stops with move_aside_cross_volume.

Skills installed before this version. Older versions did not record the written files. When such a copy is unchanged and has the team’s current version, the next scheduled update adopts it without a prompt. A copy that cannot be checked is held as “not linked”. artifactbridge skills link lists these copies for the selected workspace, and artifactbridge skills link --yes links them, so updates can check them again. artifactbridge doctor names copies that need a link. To link a copy from another workspace, select that workspace with artifactbridge workspace use <id> first.

The ArtifactBridge Skill and the workspace picker. artifactbridge setup, the sign-in step that connects your tools, and artifactbridge skills sync install the ArtifactBridge Skill (artifactbridge) and the workspace picker (artifactbridge-session-workspace). These commands also keep your changes. If you or your agent changed, added, or deleted a file in one of these folders, the command does not write into the folder and shows kept your edited copy of <skill> (<tool>). The other steps of the command continue. A copy that an older version installed is replaced only if it has exactly the files of one ArtifactBridge release. skills sync does not delete the folder: it writes only the files of the Skill and never removes a file that you added. When the ArtifactBridge Skill follows the Skill Hub, skills update artifactbridge and scheduled updates also keep a changed copy; add --discard-local to replace it after a backup. When setup removes a tool, or artifactbridge uninstall runs without --purge, ArtifactBridge makes a backup of a changed copy in skills/backups/ in the state folder before it removes the files that it installed. Files that you added stay. A copy that ArtifactBridge cannot check, for example because its record cannot be read or the folder is a link, stays as it is, and the command names it.

The ArtifactBridge guidance block. artifactbridge setup, the sign-in step that connects your tools, artifactbridge env use, and artifactbridge skills sync write a block of ArtifactBridge guidance between two marker lines in the guidance file of each tool, for example CLAUDE.md, AGENTS.md, or the Hermes SOUL.md. Your text outside the markers stays. If you or your agent change the text inside the block, these commands keep it as it is and show kept your edited ArtifactBridge guidance in <file>. A kept block does not get new ArtifactBridge text. After env use, it can still name the MCP server of the earlier environment. The command tells you, and artifactbridge doctor names the file and the earlier server. Update the server address in that file yourself. For Codex, the block ends with the list of installed Skills, between its own marker lines (# >>> artifact-bridge installed skills >>>). ArtifactBridge writes this list from the Skills on your computer. It updates the list after a Skill install, update, or uninstall, also when you changed the text above the list. If you or your agent change the list, ArtifactBridge makes a backup of the guidance file in skills/backups/ in the state folder, writes the list again, and tells you one time. A Codex block that an older version wrote has no separate list. If you changed such a block, ArtifactBridge keeps all of it, and its list of Skills is not updated. If ArtifactBridge cannot read its record of the block, it does not change the block and tells you. To get the current ArtifactBridge text back, delete the block with its two marker lines and run artifactbridge setup. When artifactbridge uninstall removes the block, or setup removes a tool, ArtifactBridge first makes a backup of a changed block: in skills/backups/ in the state folder, or with --purge in ~/ArtifactBridge skill backups/<run>/. If the backup fails, nothing is removed. An older CLI replaces the whole block, with your changes in it.

Uninstall ArtifactBridge completely. artifactbridge uninstall --purge makes a backup of each changed Skill copy, the ArtifactBridge Skill and the workspace picker included, in ~/ArtifactBridge skill backups/<run>/ before it removes the Skill files, and moves earlier moved-aside folders there too. Files that you added stay in the Skill folders. These backups stay after the state folder is removed; skills restore-backup does not read them, so copy the files back yourself. When the desktop installer cleans up an earlier installation, it puts the backups of changed copies in the old state folder that it moves aside.

Older versions of the CLI. An older CLI does not check for changes and replaces changed files. Update the desktop app and the CLI on each computer where you or your agents change Skills.

What the workspace sees. When the server supports it, ArtifactBridge reports that a copy is held, with a fixed code and a time only. Local-edit state reports never contain file names, paths, sizes, or content. Install reports name only the files of the Skill itself, never a path on your computer or a file that you added.

Propose a change from a local tool

Some agents improve a Skill while they work. A tool with a write-approval gate, such as Hermes, stages the change on your computer instead of writing it. The desktop app lists the staged change under Changes from your tools and shows the exact lines. Send for review files one ordinary change on the document that backs the Skill, with the tool, the computer, and your reason as its source. Nothing leaves your computer before that step. Anyone in the workspace can accept it in the Inbox, as with every change. In the Inbox, the change names the Skill. The detail shows the tool, the computer, and the reason above the change, and the decision card lists the tools and computers that Accept changes updates. After someone accepts, the change shows a Rollout section: how many installed tools run the new version, and each tool as Updated, Waiting, Held: local edit, or Failed. Your own failed tools offer Retry. Another member’s failed tool shows the command that member runs. In Settings → Agent → Skills, the Installs column shows how many of your tools run the current version, and the In review column counts the open changes to each Skill and opens the newest one in the Inbox. The same flow is available from the terminal: artifactbridge skills changes list, show, send, and discard.

Held tools. When a member’s copy of a Skill has local changes, ArtifactBridge does not update it (see Keep your changes to an installed Skill). The Rollout then shows that tool as Held: local edit instead of Waiting, with the member and the computer that reported last. The Installs column counts your held tools, for example “1 held”. Point to the count or move the keyboard focus to it to read why. ArtifactBridge shows only this state. The content of the local change stays on the computer. A held tool is counted once for each member and tool, not for each computer: if you use one tool on two computers, the computer that reported last sets the state.

Changes from a local edit. When a change comes from a member’s edit to an installed copy of a Skill, its Inbox row says “proposed a change from a local edit”. The detail shows its source as Local edit, the tool and the computer, and the member who sent it, for example “Local edit · Claude Code on dana-mbp · sent by Dana Reyes”. The reason heading names the member: “Why Dana changed it”. The source is information only. It does not give the change more trust, and anyone in the workspace decides as for every change.

Suggest skill changes from your sessions

The desktop app can review your Claude Code and Codex sessions and suggest changes to the workspace Skills they used. It is on by default. Turn it off in Settings → General → Skill reviewer. A suggestion shows on the Skills view under Changes from your tools. To see every review on this computer, run artifactbridge skills reviewer status.

What it reads. When a Claude Code or Codex session ends on this computer, the reviewer checks if the session loaded a skill from your workspace. It reads only those sessions. It stops at that check for all other sessions.

What leaves your computer. A short summary of each session: your messages to the agent, the skills it read, its ArtifactBridge tool calls and their errors, and the end of its last message. The summary never holds file contents, command output, or tool results. Values that look like secrets are removed first.

What ArtifactBridge keeps. No session content. The server uses the summary for one review on the ArtifactBridge model (Cloudflare Workers AI). It does not save the summary, the prompt, or the result. It keeps only usage records with no content: counts, time taken, token totals, the model name, and a fixed result code.

What it costs. Each review uses agent credits of your workspace. When the workspace reaches its weekly agent credit limit, reviews stop until the limit resets.

What you decide. A suggestion stays on this computer until you choose Send for review. Then anyone in the workspace can accept it in the Inbox. You can turn the reviewer off at any time.

Turn it off. Suggestions that you did not send are discarded. Changes that you already sent stay in the Inbox. A workspace owner can turn the reviewer off for the whole workspace in Settings → Agent → Skills; then no computer in the workspace sends a review.

Undo a bad skill change

A workspace Skill is the text of its source document, so you undo a bad change by rolling back that document. Open the document’s History and select Roll back to V3… on the last good version. See Roll back to an earlier version. Before you confirm, the dialog says what the rollback reaches:

• An active Skill gets the restored text. Members’ tools get it at their next refresh, usually within 30 minutes.
• A Skill pinned to a version keeps giving members that pinned version. Rolling back the document does not change what members get.
• A deactivated Skill gets the restored text, but it reaches no one until someone activates the Skill.
• Modules. Other documents that the Skill uses stay at their current versions. Roll each one back from its own History if needed.

Skill Hub gives the restored text a new version number. It does not bring back the earlier number, so installed tools see the restored text as a newer version. An agent can also propose the rollback with rollback_to_version or rollback_to_version_id; see Agent rollbacks. A human decides.

Use a Skill once

A connected agent can discover and read an enabled workspace Skill for the current conversation without installing it. It finds the same Skills that Browse hub shows you. A deactivated Skill may appear there, but the agent cannot read it. The agent gets the reason and, when you can see it, the replacement. A legacy Skill still works, and the agent gets its notice with the content. Ask the agent to load the relevant Skill before doing the task. Installation is useful when you want the tool to discover the Skill again in future sessions.

Skills in a space

You add a Skill to a space by its name. Only managed-document Skills that you can see can be added. The read of a space lists the Skills that the reader gets through that space. Each Skill shows its description. A Skill that comes from an included space that the reader can open also shows that space; a Skill that the space points at directly does not. The agent does not install these Skills, and they do not start on their own. The agent compares the task with each description and fetches each matching Skill with artifactbridge_read_skill. The copied space context and the space read tell the agent to fetch the current version, so an approved change is in the next fetch. The space read shows the source of the Skill as it is now. The version and the content hash that the fetch returns identify the exact text that the agent used. A fetched Skill is text in the session: its files are not on the computer, and ArtifactBridge does not run its scripts. A reader who cannot see the source document of a Skill does not get the Skill. See Add spaces, folders, documents, and Skills.