Agent skill · software engineering · sickn33
cowork-to-code-bridge
Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.
Why this skill is useful
Adds executable scripts for safely queuing and executing tasks on the user's local machine, which the AI cannot generate on its own.
What it needs
Requires cowork-to-code-bridge installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Supporting material availability This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files: <support-root>/scripts/gitstatus.sh <support-root>/scripts/runclaude.sh Obtain the required material from the declared upstream source, or from a user-provided installation of that source. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable. cowork-to-code-bridge Use this skill only when the user explicitly asks to operate on a machine they own or administer and the required work cannot be completed in the current sandbox. The bridge queues a named script through a shared local directory; it does not make a local task safe merely because it opens no inbound port. [!WARNING] The bridge daemon and its scripts run with the local account's permissions. They can access local files, credentials, processes, and outbound network connections available to that account. Treat every queued task as execution on the user's real machine. When to Use Use this skill only when all of the following are true: the user explicitly requested work on their own machine; the bridge was already installed and independently verified by the owner; the exact local path, action, permission scope, and expected output are known; the action cannot be completed safely in the current sandbox; a fixed approved script can perform the task, or the user explicitly approves the stronger runclaude.sh boundary described below. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/cowork-to-code-bridge