162 Markdown documents, one cloud knowledge base, searchable by meaning from Claude Code, Cursor, or n8n — and by your teammates. One command deploys it. The payoff is that a written answer gets made once and reused, instead of re-litigated three times a quarter.
Built a skill Wednesday night, opened a different Mac Thursday morning, and it was gone. The full-mesh Syncthing setup that keeps the config behind my workflow automation software identical on 4 machines - .stignore rules for 360,000 files, an onboarding SOP, and the mistakes I made.
Your knowledge sits in dozens of folders and hundreds of chat threads, so the answers come back generic. Build a knowledge base on your file system instead: the four-layer architecture, a step-by-step build sequence, and a checklist to tick off as you go.
Content, video, audio, design, publishing
Five Claude Code Skills, one unattended content pipeline: persona cloning, sourcing, drafting, image generation, and scheduled publishing. A workflow automation pattern built on single-responsibility design and file-based handoffs — each step reads exactly what the last one wrote.
Content teams rarely stall on writing, they stall on supply. This Claude Code Skill takes one topic, pulls real discussions, extracts non-obvious angles, and returns platform-ready drafts: 125 posts to 24 pieces in about ten minutes, with the full pipeline.
Battle-tested Ghost CMS practices from 18 months running two self-hosted sites: VPS deployment, Cloudflare DNS, theme work, newsletter growth, SEO configuration and multi-site ops, including the Admin API that lets ai automation tools publish without a human in the editor.
When I rebuild one with AI agents, you get the write-up — including the parts that didn't work. No weekly roundup, no "5 tools you need."