So your team can get on with the proper work.
No IT department needed. No technical background required.
Let’s talk →If your business has grown but the way it runs hasn’t kept pace, that’s usually where I come in. Work tracked in spreadsheets, information buried in email chains, software that’s barely being used — I find where AI can take that load off and build the automation that does it. You get something working, not a report.
I've been using Claude Cowork as a daily driver since the research preview. Scheduled tasks, skills, vault memory, and n8n integrations baked in. It replaced a lot of the glue I used to build by hand.
Three weeks ago a research pipeline I run finished overnight. Clean exit. No errors, no timeouts, nothing in the logs that looked wrong. The next morning I found three new entries in the records database with scores, bri
The subfolder pattern works in Copilot Cowork, so the design question actually matters. How to structure SKILL.md as a dispatch router, where organisational content belongs, and why the growing community marketplaces are a risk, not a shortcut.
A week after my first Copilot Cowork custom skills post, Microsoft has quietly changed three of the behaviours I documented. The install flow, the Skills panel, and the skill format have all moved. None of it is in Microsoft Learn yet.
I tested Copilot Cowork custom skills for a week. The docs make setup look simple, but there's undocumented behaviour, built-in skill conflicts, and a persistence gap vs Claude Cowork.
I started using Claude Cowork about three weeks ago. Most of the coverage is by devs, written for other devs. I'm not one. I'm a non-developer who builds personal AI infrastructure (automations, skills, pipelines
