Agent skill

Coworker

Reference for the Coworker file-queue automation system: task lifecycle, directory state machine, PowerShell workers, scheduler configuration, and operational conventions.

Apache-2.0Auto-check passedProductivity & Automation

Install Coworker

skills CLI

$ npx skills add platonai/Browser4 --skill coworker -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 coworker --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .claude/skills && cp -r skills-src/coworker/skills/coworker .claude/skills/coworker && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "coworker" agent skill from https://github.com/platonai/Browser4/tree/main/coworker/skills/coworker into .claude/skills/coworker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coworker", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/platonai/Browser4/tree/main/coworker/skills/coworker

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add platonai/Browser4 --skill coworker -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 coworker --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .agents/skills && cp -r skills-src/coworker/skills/coworker .agents/skills/coworker && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "coworker" agent skill from https://github.com/platonai/Browser4/tree/main/coworker/skills/coworker into .agents/skills/coworker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coworker", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add platonai/Browser4 --skill coworker -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 coworker --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/coworker/skills/coworker .cursor/skills/coworker && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "coworker" agent skill from https://github.com/platonai/Browser4/tree/main/coworker/skills/coworker into .cursor/skills/coworker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coworker", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/platonai/Browser4.git --path coworker/skills/coworker

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add platonai/Browser4 --skill coworker -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 coworker --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/coworker/skills/coworker .gemini/skills/coworker && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "coworker" agent skill from https://github.com/platonai/Browser4/tree/main/coworker/skills/coworker into .gemini/skills/coworker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coworker", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install platonai/Browser4 coworker

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add platonai/Browser4 --skill coworker -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .github/skills && cp -r skills-src/coworker/skills/coworker .github/skills/coworker && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "coworker" agent skill from https://github.com/platonai/Browser4/tree/main/coworker/skills/coworker into .github/skills/coworker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coworker", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add platonai/Browser4 --skill coworker -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 coworker --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/coworker/skills/coworker .opencode/skills/coworker && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "coworker" agent skill from https://github.com/platonai/Browser4/tree/main/coworker/skills/coworker into .opencode/skills/coworker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "coworker", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: coworker
GitHub stars: 1.2k
Token cost: ~3.9k tokens
SKILL.md length: 1,246 words
Files: 1
Skills in repo: 17
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Reference for the Coworker file-queue automation system: task lifecycle, directory state machine, PowerShell workers, scheduler configuration, and operational conventions.

Works in 8 steps: Main task execution → Queue processor / watchdog → Unified scheduler → …
You need to understand how Coworker works
SKILL.md covers What Coworker is for, Main workflows and scripts, How tasks move through… and Key PowerShell commands /…, plus 3 more sections
Calls gh

What it does

Coworker is an agent skill from platonai/Browser4. Reference for the Coworker file-queue automation system: task lifecycle, directory state machine, PowerShell workers, scheduler configuration, and operational conventions. Use when you need to understand how Coworker works or debug its behavior.

Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation. It works with PowerShell. The repository describes itself as: Browser4 — an AI-native browser engine for autonomous agents, intelligent extraction, and large-scale web automation. The licence is Apache-2.0.

When your agent uses it

You need to understand how Coworker works
Debug its behavior

Example prompts

“/coworker”

Requirements

Pre-approved tools (allowed-tools): Bash(pwsh:*), Bash(./coworker/scripts/*)

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Main task execution
Queue processor / watchdog
Unified scheduler
Draft refinement pipeline
GitHub Issues pipeline
Task-source ingestion
Git sync / pushing approved work
Memory helpers

What it can do on your machine

Read from SKILL.md and the folder at commit 0fdba82. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash(pwsh:*)
- Bash(./coworker/scripts/*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Coworker loads about 3.9k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 1,246 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~64
When it runs · the whole SKILL.md, loaded when a task matches: ~3.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from platonai/Browser4 at commit 0fdba82, republished under its Apache-2.0 licence (© platonai). 1,246 words, ~3,909 tokens.

Download SKILL.mdSave it as .claude/skills/coworker/SKILL.md (or your agent's skills folder).

name: coworker
description: Reference for the Coworker file-queue automation system: task lifecycle, directory state machine, PowerShell workers, scheduler configuration, and operational conventions. Use when you need to understand how Coworker works or debug its behavior.
allowed-tools: Bash(pwsh:*), Bash(./coworker/scripts/*)
title: Coworker — File-queue task pipeline system reference

Coworker

This repository contains a file-queue automation system called Coworker. The active implementation is the PowerShell worker in coworker/scripts/engineer.ps1: it watches task files, renames them, runs GitHub Copilot against the repository, logs the run, and routes the task through review/approval/push folders. (coworker/README.md:1-40, coworker/scripts/engineer.ps1:50-80, coworker/scripts/engineer.ps1:413-717)

What Coworker is for

Use Coworker when you want an agentic workflow driven by task files in the repo, not by chat alone.
A task can be a plain Markdown file or a structured file with Title:, Description:, and Prompt:. If the structured header is missing, the full file becomes the prompt. (coworker/scripts/engineer.ps1:11-20, coworker/scripts/engineer.ps1:536-541)
The worker runs GitHub Copilot CLI with broad repo access to execute the task against the current repository. The helper command is configurable in coworker/scripts/config.psd1. (coworker/scripts/workers/gh-copilot.ps1:37-65, coworker/scripts/config.psd1:1-12)
Important: the current/live workflow is file-based. The folder-based “story.md / analysis / plan / design / impl.patch / e2e” pipeline described in coworker/docs/architect/orchestrator.md and coworker/scripts/architect/orchestrator.ps1 exists as design/legacy material, but it is not the main coworker entrypoint used by coworker.ps1. (coworker/docs/architect/orchestrator.md:1-38, coworker/scripts/architect/orchestrator.ps1:17-29, coworker/scripts/engineer.ps1:57-68)

Main workflows and scripts

1. Main task execution

Primary entrypoint: ./coworker/scripts/engineer.ps1
It ensures the task directories exist, optionally accepts a task file path, moves that file into coworker/tasks/main/1ready, generates a descriptive kebab-case filename, moves it to 2working, runs Copilot, writes logs, then moves the task to main/3complete or 5approved. (coworker/scripts/engineer.ps1:22-35, coworker/scripts/engineer.ps1:82-95, coworker/scripts/engineer.ps1:417-500, coworker/scripts/engineer.ps1:551-713)
The prompt given to Copilot explicitly says: finish the task described in the file, but do not move that task file yourself. The script handles routing after execution. (coworker/scripts/engineer.ps1:531-545)

2. Queue processor / watchdog

Recommended wrapper for one-shot or recurring checks: ./coworker/scripts/process-coworker-queue.ps1
It checks for pending files in 1ready or 5approved, avoids duplicate coworker runners, can optionally run task-source monitoring first, and has loop-detection logic that can kill a stuck coworker process and move the task from 2working to main/3aborted. (coworker/scripts/process-coworker-queue.ps1:28-37, coworker/scripts/process-coworker-queue.ps1:55-69, coworker/scripts/process-coworker-queue.ps1:71-174, coworker/scripts/process-coworker-queue.ps1:176-250)

3. Unified scheduler

Preferred automation entrypoint: ./coworker/scripts/coworker-scheduler.ps1
Scheduler definitions live in coworker/scripts/coworker-scheduler.config.psd1.
Current defaults:
- coworker every 15s, dependent on task-source processing, only when 1ready or 5approved has files.
- draft-refinement every 15s, only when 0draft/refine/1ready has files.
- commit-github-issues every 15s, only when issues/github/commit/ready has files.
- refine-github-issues every 15s, only when issues/draft/refine/0ready has files.
- process-task-source exists but is disabled by default. (coworker/scripts/coworker-scheduler.config.psd1:1-62)
The scheduler launches child PowerShell processes, keeps live worker output in each child terminal, records a console transcript log under coworker/tasks/300logs/, and writes a JSON status snapshot. (coworker/scripts/coworker-scheduler.ps1)

Draft refinement is separate from main task execution.
Queue:
- coworker/tasks/main/0draft/refine/1ready
- coworker/tasks/main/0draft/refine/2working
- coworker/tasks/main/0draft/refine/3done
Main scripts:
- coworker/scripts/workers/refine-drafts.ps1
- coworker/scripts/process-draft-refinement-queue.ps1
refine-drafts.ps1 moves files from ready -> working, asks Copilot to return only the refined document, then writes the refined content and moves the file to done. (coworker/README.md:128-152, coworker/scripts/workers/refine-drafts.ps1:31-39, coworker/scripts/workers/refine-drafts.ps1:89-151, coworker/scripts/process-draft-refinement-queue.ps1:28-71)

5. GitHub Issues pipeline

Two-stage pipeline for extracting, refining, and creating GitHub issues from natural-language drafts:
1. Refine (coworker/scripts/workers/refine-github-issues.ps1): Scans issues/draft/refine/0ready, invokes the agent to extract individual issues from each draft, formats each as structured markdown, and writes them to issues/github/commit/ready.
2. Commit (coworker/scripts/workers/commit-github-issues.ps1): Scans issues/github/commit/ready and creates each file as a GitHub issue via gh issue create.
Directories: issues/draft/refine/0ready → 1working → 2done (or 0error on failure); staged files land in issues/github/commit/ready.
Supports optional Labels:, Assignees:, and Repo: metadata fields in each issue block. (coworker/scripts/workers/refine-github-issues.ps1:1-29, coworker/scripts/workers/commit-github-issues.ps1:1-19)
Both tasks are enabled by default in the scheduler config. (coworker/scripts/coworker-scheduler.config.psd1:35-60)

6. Task-source ingestion

coworker/scripts/process-task-source.ps1 can create new task files in coworker/tasks/main/1ready from:
- GitHub issues assigned to a configured user
- a polled URL containing a keyword
Defaults are repo platonai/Browser4, assignee galaxyeye, and keyword @galaxyeye. (coworker/scripts/process-task-source.ps1:18-25, coworker/scripts/process-task-source.ps1:40-58, coworker/scripts/process-task-source.ps1:61-106, coworker/scripts/process-task-source.ps1:109-151)
This source monitor is useful, but remember it is disabled in the default scheduler config. (coworker/scripts/coworker-scheduler.config.psd1:62-67)

7. Git sync / pushing approved work

When Coworker sees files in 5approved, it first moves them into a date-based folder under 6git-pushed, then invokes coworker/scripts/workers/git-sync.ps1. (coworker/scripts/engineer.ps1:365-399)
git-sync.ps1 does not contain custom git logic; it asks GitHub Copilot to commit all changes in the repo, pull, push, and auto-resolve conflicts. Treat this as powerful and potentially risky. (coworker/scripts/workers/git-sync.ps1:16-29)

8. Memory helpers

Before executing a task, coworker.ps1 calls coworker/scripts/workers/coworker-memory-generator.ps1 -Type init and appends returned memory context/instructions to the task prompt. (coworker/scripts/engineer.ps1:508-545)
Daily/monthly/yearly/global memory summaries are generated from coworker/tasks/300logs. (coworker/scripts/workers/coworker-memory-generator.ps1:15-22, coworker/scripts/workers/coworker-memory-generator.ps1:103-172, coworker/scripts/workers/coworker-memory-generator.ps1:174-347, coworker/scripts/workers/coworker-daily-memory-generator.ps1:49-56, coworker/scripts/workers/coworker-daily-memory-generator.ps1:169-233)

How tasks move through directories

Show full SKILL.md (564 more words)Show less

Main task lifecycle

Draft in coworker/tasks/main/0draft (manual authoring area). (coworker/README.md:16-28, coworker/tasks/main/0draft/README.md:1-37)
Queue by moving/copying the task file to coworker/tasks/main/1ready. (coworker/README.md:30-40) The runner scans 1ready recursively, so tasks placed in date-organized subfolders (e.g. 1ready/2026/0905/..., as written by review-recent-issues/organize workers) are picked up too; dot-prefixed files/folders (.gitkeep, .locks, .hidden.md) are always ignored. (coworker/scripts/engineer.ps1:248-253, coworker/scripts/common/Watchers.ps1:17-78)
Rename + start work: Coworker generates a descriptive kebab-case name and moves the file to coworker/tasks/main/2working. (coworker/scripts/engineer.ps1:417-500, coworker/scripts/workers/rename.ps1:30-60, coworker/scripts/workers/rename.ps1:153-178)
Execute: Copilot works against the repo; logs are written under coworker/tasks/300logs/YYYY/MM/DD. (coworker/scripts/engineer.ps1:548-552, coworker/scripts/engineer.ps1:575-687)
Finish:
- normal tasks -> coworker/tasks/main/3complete/YYYY/MMDD/...
- tasks containing #auto-approve -> coworker/tasks/main/5approved/YYYY/MMDD/... (coworker/scripts/engineer.ps1:696-713, coworker/README.md:48-55)
Approval / push:
- human review can happen in main/3complete and optionally 4review
- moving a reviewed task to 5approved causes the next run to move it into 6git-pushed/YYYY/MMDD/... and invoke git sync. (coworker/README.md:7-12, coworker/scripts/engineer.ps1:348-399)
Failure path: stuck/aborted tasks can end up in coworker/tasks/main/3aborted. (coworker/scripts/process-coworker-queue.ps1:133-174)

0draft/refine/1ready -> 0draft/refine/2working -> 0draft/refine/3done. (coworker/README.md:128-152, coworker/scripts/workers/refine-drafts.ps1:31-39, coworker/scripts/workers/refine-drafts.ps1:129-151)

Separate GitHub issues lifecycle

Refine: issues/draft/refine/0ready -> 1working -> 2done (or 0error on failure).
Commit: issues/github/commit/ready -> created via gh issue create.
#auto-approve in a draft's last 5 lines also routes the original draft to github/commit/ready as an issue. (coworker/scripts/workers/refine-github-issues.ps1:31-36, coworker/scripts/workers/refine-github-issues.ps1:447-465, coworker/scripts/workers/commit-github-issues.ps1:1-19)

Key PowerShell commands / entrypoints

From repository root in PowerShell:

powershell

# Run the unified scheduler continuously
.\coworker\scripts\coworker-scheduler.ps1

# Run one scheduler pass
.\coworker\scripts\coworker-scheduler.ps1 -Once

# Run one coworker queue check
.\coworker\scripts\process-coworker-queue.ps1 -Once

# Run coworker directly now
.\coworker\scripts\engineer.ps1

# Queue a specific task file directly
.\coworker\scripts\engineer.ps1 .\path\to\task.md

# Process draft refinement once
.\coworker\scripts\process-draft-refinement-queue.ps1 -Once

# Refine all ready drafts
.\coworker\scripts\workers\refine-drafts.ps1 -Path .\coworker\tasks\main\0draft\refine\1ready

# Extract and refine GitHub issues from drafts
.\coworker\scripts\workers\refine-github-issues.ps1

# Create GitHub issues from staged files
.\coworker\scripts\workers\commit-github-issues.ps1

# Poll external task sources once
.\coworker\scripts\process-task-source.ps1 -Once

# Run git sync manually
.\coworker\scripts\workers\git-sync.ps1

References: coworker/README.md:34-40, coworker/README.md:85-90, coworker/README.md:121-152, coworker/scripts/engineer.ps1:22-35, coworker/scripts/process-task-source.ps1:3-16.

Important config files

coworker/scripts/config.psd1 — defines the Copilot command. Current default is gh copilot --model gpt-5.4 --no-ask-user --log-level info --allow-all. (coworker/scripts/config.psd1:1-12)
coworker/scripts/config.ps1 — loads config.psd1 and exposes $COPILOT. (coworker/scripts/config.ps1:1-12)
coworker/scripts/coworker-scheduler.config.psd1 — scheduler tasks, intervals, pending paths, and status/log paths. (coworker/scripts/coworker-scheduler.config.psd1:1-41)
coworker/tasks/100templates/*.prompt.md — prompt templates for the older orchestrator pipeline, not the normal file-runner path. (coworker/docs/architect/orchestrator.md:23-38, coworker/scripts/architect/orchestrator.ps1:17-23, coworker/tasks/100templates/analysis.prompt.md:1-8, coworker/tasks/100templates/implementation.prompt.md:1-15)
coworker/README.md and coworker/tasks/main/0draft/README.md — the clearest human-facing usage docs. (coworker/README.md:1-153, coworker/tasks/main/0draft/README.md:1-37)

Conventions and safety notes

Prefer the active file workflow. For normal use, create a Markdown task file and queue it; do not start with the older story.md orchestrator structure unless you are intentionally working on that subsystem. (coworker/scripts/engineer.ps1:57-68, coworker/docs/architect/orchestrator.md:9-30)
Numeric filenames are OK. Coworker auto-creates 0draft/1.md..5.md placeholders and can rename generic/numeric task files to descriptive kebab-case names. (coworker/scripts/engineer.ps1:172-185, coworker/scripts/engineer.ps1:340, coworker/scripts/engineer.ps1:417-489)
Do not manually move files out of 2working while a run is active. The worker prompt and post-processing assume the script, not the agent, handles state transitions. (coworker/scripts/engineer.ps1:531-545, coworker/scripts/engineer.ps1:693-713)
Use #auto-approve sparingly. It bypasses manual review and sends the task straight to the approval/push path. (coworker/README.md:48-55, coworker/scripts/engineer.ps1:696-713)
Review before 5approved. Approval eventually triggers a Copilot-driven git commit/pull/push over the whole repo. (coworker/scripts/engineer.ps1:365-399, coworker/scripts/workers/git-sync.ps1:16-29)
Expect broad tool access. The configured Copilot command already includes --allow-all, and many calls also add --allow-all-tools / --allow-all-paths. Coworker is meant to act on the repository, not just read it. (coworker/scripts/config.psd1:1-12, coworker/scripts/engineer.ps1:575-585, coworker/scripts/workers/refine-drafts.ps1:108-118)
Check logs first when debugging. Task logs and Copilot logs are written per day under coworker/tasks/300logs/YYYY/MM/DD. Scheduler child-process logs go under that same directory using HHmmss-<taskname>.stdout.log filenames. (coworker/scripts/engineer.ps1:103-106, coworker/scripts/engineer.ps1:548-552, coworker/scripts/coworker-scheduler.config.psd1:7-8, coworker/scripts/coworker-scheduler.ps1:163-169)
GitHub CLI auth is required. The docs explicitly require gh to be installed and authenticated. (coworker/README.md:42-46)

Recommended mental model for agents

Treat Coworker as a filesystem-backed state machine around GitHub Copilot:

task files are the queue
numbered directories are the state
PowerShell scripts are the orchestrators
300logs is the audit trail
5approved is the point of no return for automated git operations

If you need to use Coworker safely, the normal path is:

draft a Markdown task
queue it in coworker/tasks/main/1ready
run process-coworker-queue.ps1 -Once or the scheduler
inspect main/3complete and 300logs
only then move the task to 5approved if you want automated commit/push

Files

Just SKILL.md in coworker/skills/coworker of platonai/Browser4.

Open the folder on GitHubat commit 0fdba82

Compare with similar skills

Coworker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Coworker compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Coworker this skillplatonai/Browser4	1.2k	—	~3.9k	Automated safety check: Pass	Apache-2.0	yesterday
Hunting For Suspicious Scheduled Tasksmukul975/Anthropic-Cybersecurity-Skills	34k	—	~1.2k	Automated safety check: Pass	Apache-2.0	1 mo ago
Windows Automationvellum-ai/vellum-assistant	1.4k	—	~1.5k	Automated safety check: Pass	MIT	yesterday
Outlook Nativetaracodlabs/aiden	852	—	~816	Automated safety check: Pass	Apache-2.0	27 days ago
Powershell Protaracodlabs/aiden	852	—	~747	Automated safety check: Pass	Apache-2.0	27 days ago
File Managementaipoch/medical-research-skills	1.9k	—	~1.6k	Automated safety check: Pass	MIT	23 days ago

Similar skills

Hunting For Suspicious Scheduled Tasks
mukul975/Anthropic-Cybersecurity-Skills
Hunts for adversary persistence and execution via Windows scheduled tasks (T1053.005) by analyzing Security Event ID 4698 task-creation events, suspicious task properties, and unusual execution…
34k GitHub stars~1.2k tokensUpdated 1 mo ago
Productivity & AutomationAuto-check passed
Windows Automation
vellum-ai/vellum-assistant
Automate native Windows apps and system interactions with PowerShell, documented COM APIs, and Microsoft UI Automation through the Windows host executor.
1.4k GitHub stars~1.5k tokensUpdated yesterday
Productivity & AutomationAuto-check passed
Outlook Native
taracodlabs/aiden
Outlook calendar + inbox via PowerShell COM or Microsoft Graph
852 GitHub stars~816 tokensUpdated 27 days ago
Productivity & AutomationAuto-check passed
Powershell Pro
taracodlabs/aiden
Expert PowerShell: processes, services, WMI, REST, scheduled tasks
852 GitHub stars~747 tokensUpdated 27 days ago
Productivity & AutomationAuto-check passed
File Management
aipoch/medical-research-skills
Organize, back up, compress, split, and merge files/folders using rule-driven plans; use when you need safe previews, conflict handling, and verification before executing file operations.
1.9k GitHub stars~1.6k tokensUpdated 23 days ago
Productivity & AutomationAuto-check passed
UiPath Project Generator
marcelocruzrpa/uipath-ai-skills
Generates UiPath Studio projects, REFramework scaffolds, XAML workflows and expressions through 104 deterministic Python generators instead of hand-written XAML.
108 GitHub stars~6.9k tokensUpdated 2 mo ago
Productivity & AutomationAuto-check passed

Questions about Coworker

What does Coworker do?

Reference for the Coworker file-queue automation system: task lifecycle, directory state machine, PowerShell workers, scheduler configuration, and operational conventions. Coworker is an agent skill from platonai/Browser4. Reference for the Coworker file-queue automation system: task lifecycle, directory state machine, PowerShell workers, scheduler configuration, and operational conventions.

When should I use Coworker?

Coworker fits situations like: you need to understand how Coworker works; debug its behavior.

How do I install Coworker in Claude Code?

Run `npx skills add platonai/Browser4 --skill coworker -a claude-code`. Or copy the skill folder (coworker/skills/coworker in platonai/Browser4) into .claude/skills/coworker in your project. Claude Code loads it when a task matches its description.

How do I install Coworker in Codex?

Run `npx skills add platonai/Browser4 --skill coworker -a codex`. Or copy the skill folder (coworker/skills/coworker in platonai/Browser4) into .agents/skills/coworker in your project. Codex loads it when a task matches its description.

Can I use Coworker in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add platonai/Browser4 --skill coworker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/coworker, .gemini/skills/coworker, .github/skills/coworker and .opencode/skills/coworker in your project.

What does Coworker need to run?

Going by SKILL.md and its folder, Coworker needs the command-line tools its instructions call (gh). Its frontmatter pre-approves these tools: Bash(pwsh:*), Bash(./coworker/scripts/*).

Does Coworker access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Coworker safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Coworker use?

Coworker is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Coworker use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Coworker?

Skills that share tags, products or a category with Coworker: Hunting For Suspicious Scheduled Tasks (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Windows Automation (vellum-ai/vellum-assistant, 1.4k stars), Outlook Native (taracodlabs/aiden, 852 stars) and Powershell Pro (taracodlabs/aiden, 852 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Coworker?

platonai (a GitHub user) maintains it in platonai/Browser4, which has 1,153 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 9, 2026.

Source: platonai/Browser4 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Coworker

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Coworker

What Coworker is for

Main workflows and scripts

1. Main task execution

2. Queue processor / watchdog

3. Unified scheduler

4. Draft refinement pipeline

5. GitHub Issues pipeline

6. Task-source ingestion

7. Git sync / pushing approved work

8. Memory helpers

How tasks move through directories

Main task lifecycle

Separate draft-refinement lifecycle

Separate GitHub issues lifecycle

Key PowerShell commands / entrypoints

Important config files

Conventions and safety notes

Recommended mental model for agents

Files

Compare with similar skills

Similar skills

More from platonai/Browser4

Related

Questions about Coworker