cowork-os plugin
cowork-os builds a Markdown workspace for Claude Cowork: team decisions, context, next actions and recurring routines.
- 54 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent reads and writes context files and works on a schedule.
- The signal sweep may read email and Slack if you connect them.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/cowork-osDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent reads and writes context files and works on a schedule.
- The signal sweep may read email and Slack if you connect them.
This is third-party code. Review the repository files before installing.
What it does
cowork-os is a process layer over Claude Cowork and other agents that read files. Decisions, open questions, project state, next actions and recurring routines sit in plain Markdown files the team edits itself. The agent reads context when a task starts and writes the result back when it ends. The set includes a folder structure, system instructions, a Knowledge Transfer interview about how work really happens, a decision lifecycle with a daily signal sweep, a sales pipeline, LinkedIn growth and 14 ready recurring tasks. The plugin adds commands such as `/cowork-os:install` and a skill. Without the plugin, the `INSTALL.md` file is enough.
Who it is for. Small teams and founders who work with Claude Cowork and want company context kept in files under their control.
Good fit when
- Know-how lives in people's heads and must be captured through a structured interview.
- Decisions get lost and need records with an owner, a review date and a reversal condition.
- Weekly marketing reviews and daily summaries are needed on a schedule from the agent.
- A team runs deals and wants reminders about overdue follow-ups.
Not a fit when
- A memory engine is needed to capture everything an agent does.
- Work runs without Claude Cowork and without file context.
- A ready hosted service with a UI is needed.
Example request
Run the Knowledge Transfer interview about sales and write the exception rules into context.Limitations
The setup targets Claude Cowork and agents with file access, and the recurring tasks use the Cowork scheduler. The LinkedIn and sales pipeline modules are built around specific processes and need tuning for your company. The daily signal sweep reads email and Slack, so restrict its access. The README is bilingual, English and Italian. Context files stay on your disk in plain text.
How to disable. Uninstall the plugin through `/plugin` and delete the created `context`, `decisions` and other folders. Disable Cowork schedules separately in its settings.
FAQ
How do I install it?
Run `/plugin marketplace add yempik-ai/cowork-os` and `/plugin install cowork-os@cowork-os`, then `/cowork-os:install`. Claude interviews you for about five minutes.
Can I do it without the plugin?
Yes. Copy the folder into a new Cowork project, paste `INSTALL.md` into the chat and answer about six questions.
How does it differ from claude-mem?
`claude-mem` is a memory engine. cowork-os sets up a workspace and process above or beside it, with files as the source of truth.
Are there dependencies?
No. There is no separate runtime or backend, and Cowork itself is the agent.
What does Knowledge Transfer include?
An objective-first interview that draws out unwritten rules, decision criteria and exceptions and writes them to files.
Discussion
No questions or reviews yet.
Related
PluginsA guide to Claude Cowork for no-code business tasks: 29 workflows, 70 ready prompts and CLAUDE.md templates
A scaffold for Claude Code and Codex: tasks in files, developer and QA roles, manual approval and shared state.
A plugin for Claude Code and Codex: department folders with rules and 35 skills to run a one-person company through AI agents
A Claude Code plugin that builds a knowledge system of markdown files from a conversation with you: folder structure, note templates, a processing pipeline and
A plugin that turns Claude Code into a personal chief of staff with persistent memory, a morning brief and a weekly review
A business operating system for Claude Code: a morning digest across mail, Slack, payments, analytics. The wizard installs a background daemon and programs
README in short
There is no separate app and no dependencies: files and instructions in the project folder steer the agent. Several agents work as separate runs around shared files.