Make it work with Claude Cowork

[gazialankus]

I installed it and Claude Code sees and uses the agents but Claude Cowork does not. Given a lot of agents here are not coding agents, Claude Cowork makes a lot of sense for this. There are skills and plugins I think this can fit perfectly with.

[msitarzewski]

Hey @gazialankus — this is a great call. You're right that many of our agents (design, marketing, sales, product, project management, support) are natural fits for Cowork since they're knowledge work, not code.

I've been looking into this seriously. Here's what I've found and where I think we're headed:

The Mapping

Cowork plugins are file-based — no code, no build steps. The format is:

plugin-name/
├── .claude-plugin/plugin.json    # manifest
├── skills/                       # auto-triggered domain knowledge
│   └── skill-name/SKILL.md
└── commands/                     # explicit /slash commands
    └── command-name.md

Our divisions map naturally to Cowork plugins, and our agents map to skills:

Our Division	→ Cowork Plugin	Agents → Skills
Sales	agency-sales	8 agents → 8 skills
Marketing	agency-marketing	15 agents → 15 skills
Design	agency-design	8 agents → 8 skills
Product	agency-product	4 agents → 4 skills
Project Management	agency-project-management	7 agents → 7 skills
Support	agency-support	6 agents → 6 skills
Engineering	agency-engineering	~20 agents → ~20 skills
...	...	...

The SKILL.md format is just markdown with YAML frontmatter (name + description) — which is almost identical to what our convert.sh already generates for Antigravity and Gemini CLI.

What I'm Thinking

A convert_cowork() function in convert.sh that:

1. Groups agents by division into plugins
2. Generates a plugin.json manifest per division
3. Converts each agent into a skills/agent-name/SKILL.md
4. Optionally generates stub commands where they make sense

And a matching install_cowork() in install.sh.

This is a real integration — not a hack. Anthropic's own knowledge-work-plugins repo uses the exact same file-based approach, and our agent prompts are already structured with the right kind of content (identity, workflow, deliverables, communication style).

Timeline

Adding this to our integration roadmap. It'll be the 11th supported tool. If you (or anyone else reading this) wants to take a crack at a PR, the pattern is well-established in convert.sh — look at convert_antigravity() or convert_gemini_cli() for reference, and the knowledge-work-plugins repo for the target format.

Keeping this open to track the work.

[4shil]

PR #143 implements this — #143

Each division maps to a Claude Cowork plugin (agency-design, agency-marketing, etc.), and each agent becomes a skill inside that plugin. 12 plugins, 121 agents total.

Install with: ./scripts/install.sh --tool claude-cowork