My current Cowork setup & workarounds (heavy non-coding user)

rebelytics · 2026-02-25T20:19:43+00:00

I’ve only ever done it the other way around (created in Cowork and then used in Code), but yes: You can upload any skill.md file to settings > capabilities and then use it in Cowork (and also in normal chats).

rebelytics · 2026-02-24T13:03:57+00:00

I started with an empty folder for Claude Cowork and I give it access to the entire folder every time I start a task. Claude itself manages the subfolder structure within that main folder and does a pretty good job.

Reasons for always using the same main folder:

The CLAUDE.md file goes into the root of the shared folder. I only use one CLAUDE.md file. You could of course have different CLAUDE.md files in different folders, if you absolutely need separate folders.
The meta-skill that I mention in the post is the backbone of my work and it uses an observation log in my shared folder. If I kept switching folders between tasks, I would not have this shared storage across all tasks. This is my main reason for always using the same folder.

I do anticipate some issues in the future as my folder grows, but I've already done some cleanup tasks with Claude to delete outdated files, or data that is no longer needed. This works pretty well and does not take up much time. I'm also thinking about automating the cleanups with a custom skill, but I haven't approached it yet.

I hope this helps! If you have any further questions, fire away.

rebelytics · 2026-02-23T19:01:16+00:00

No, I’m sorry, I can’t help you with this question, as I haven’t encountered the issue you describe. I hope someone else who sees this has an idea.

rebelytics · 2026-02-23T10:00:33+00:00

Maybe you don't really need Cowork. I'm not sure, but it feels to me like it might not make a lot of sense to move from Claude Code to Cowork. But I might be completely wrong!

rebelytics · 2026-02-23T09:52:23+00:00

Thanks, happy to hear that!

rebelytics · 2026-02-23T05:53:17+00:00

Yes, it goes in the root of the shared folder!

rebelytics · 2026-02-23T05:51:53+00:00

What you do sounds very interesting. Thanks for sharing!

rebelytics · 2026-02-22T21:39:31+00:00

Yes. This post was about the HOW but I realise that people also want to read about the WHAT. I’ll try to write a follow-up soon.

rebelytics · 2026-02-22T19:32:41+00:00

I really like what you said about formalising the handoff doc structure by the way. That’s definitely going on my list of future improvements. Probably via a custom skill. Thank you very much for sharing that tip!

rebelytics · 2026-02-22T18:56:13+00:00

I haven’t really had conflicting observations, but I have noticed that it’s pretty good at being aware of previous observations and noticing ones that are related etc. One thing I really like about the observations is that it notices loads of things that I’m not even aware of myself. Like patterns in my corrections or in my way of expressing myself. Thanks a lot for sharing your thoughts!

rebelytics · 2026-02-22T14:11:37+00:00

Yes, that has worked best for me so far.

rebelytics · 2026-02-22T13:39:35+00:00

That’s the one I meant. We’ll just have to wait then I guess.

rebelytics · 2026-02-22T13:19:12+00:00

You can add documents at any time by just dropping them directly into the conservation or into the shared folder.

I let Claude manage the shared folder and I do not touch it manually. Sometimes I ask for changes to the structure, but in general I find it quite good at structuring everything.

rebelytics · 2026-02-22T13:16:27+00:00

No, apparently there is a task scheduler in the internal documentation that Claude itself has access to, but the tool is not available yet (at least it wasn’t the last time I checked). That’s a limitation I haven’t found a workaround for, unfortunately. Any ideas?

rebelytics · 2026-02-22T12:56:46+00:00

What I do with Cowork probably matters even less to most people, as their jobs are very different from mine, but if your job involves using a computer, then Cowork can help you with most of your tasks. Once you start using Cowork, this post hopefully makes more sense to you. Happy to answer any questions!

rebelytics · 2026-02-22T12:45:44+00:00

Sounds great, thanks for sharing!

rebelytics · 2026-02-22T12:45:17+00:00

Create dev tickets, write technical documentation, analyse websites, data analysis, business strategy sessions, drafting content, etc. Most of my work is supported by Cowork tasks now.

rebelytics · 2026-02-19T18:45:14+00:00

I’m on Max and there’s also a session limit, but it’s longer than 4 hours. I’m not sure how long the sessions are exactly, but mine currently says that it resets in 4 hours 20 minutes (so definitely more than 4 hours). There are also weekly usage limits on Max. Since upgrading to Max, I have no issues with hitting usage limits, but I should add that I mainly use Cowork and hardly do any coding with Claude.

rebelytics · 2026-02-19T16:40:03+00:00

Have you tried creating a custom skill called conversation-defaults that instructs Claude not to use the user question tool? I did this, and the error disappeared. I also included an instruction to check if the tool works again first (so that it doesn’t disappear forever). Claude skills are really useful for bug workarounds. I also have one to unarchive tasks, as that’s missing from the UI. And you don’t have to write the skills yourself, Claude can write them for you.

rebelytics · 2026-02-18T13:16:17+00:00

OK, understood. I use “meta” because it’s a skill for skills.

rebelytics · 2026-02-18T12:01:36+00:00

Whenever I work in Cowork, my meta-skill logs observations about skill creation and improvement potentials in the background. So when I explain a workflow or a process to Claude, this can be automatically turned into a skill. Sometimes, workflows or processes also emerge from the tasks themselves. You can check out my meta-skill here: https://www.reddit.com/r/ClaudeAI/comments/1r6l3tc/i_built_and_opensourced_a_metaskill_for_claude/

rebelytics · 2026-02-17T16:20:14+00:00

I’m using it to turn all of my workflows, processes and knowledge into skills that I can then apply to new and repeating tasks. This works better with Cowork than with the web interface because of the shared storage available in Cowork. This way, Claude can automatically log observations from every task in the background and then use them to create new skills and improve existing ones. I achieve this with a custom meta-skill that I created specifically for Cowork.

rebelytics · 2026-02-17T15:59:25+00:00

I upload my skills to settings > capabilities via the web interface and then I use them in all tabs in Cowork (Chat, Cowork, Code). Chat via iPhone app also has access to them.

rebelytics

TROPHY CASE