Agent skill

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.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill cowork-to-code-bridge --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/cowork-to-code-bridge/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 `run_claude.sh` boundary described below. Examples include an explicitly requested disk-health check, repository status, or a bounded edit in one named

What's inside
Steps it walks through
  1. When to Use
  2. Do Not Bootstrap from Mutable Upstream Instructions
  3. Required Machine-Side Preconditions
  4. Core API
  5. Prefer Fixed Approved Scripts
  6. Free-Form Local Agent Boundary
  7. Results and Failure Handling
  8. Limitations
Commands it runs
git init cowork-to-code-bridge-review
cd cowork-to-code-bridge-review
git remote add origin https://github.com/abhinaykrupa/cowork-to-code-bridge.git
git fetch --depth=1 origin 97f515d425df587c281effb02cda9ad0fd470790
git checkout --detach FETCH_HEAD
test "$(git rev-parse HEAD)" = "97f515d425df587c281effb02cda9ad0fd470790"
shasum -a 256 install.sh LICENSE
More from agentic-awesome-skills
All skills →
About this skill
What does the cowork-to-code-bridge skill do?

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.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill cowork-to-code-bridge --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going