Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I built a simple internal chatbot that answers your team's SOPs and FAQs using your existing Google Drive docs in the walkthrough, I show: – how it finds the right doc for any question – how your team can “@” specific files (like in Slack) – how to set...

27,263 Aufrufe • vor 1 Jahr •via X (Twitter)

11 Kommentare

Profilbild von Byte86
Byte86vor 1 Jahr

chatbot

Profilbild von PDF GPT
PDF GPTvor 2 Jahren

This is my favorite AI tool for reviewing reports. Just upload a report, ask for a summary, and get one in seconds. It's like ChatGPT, but built for documents. Try it for free.

Profilbild von Russ
Russvor 1 Jahr

Chatbot

Profilbild von MΞTA SPΞLL
MΞTA SPΞLLvor 1 Jahr

chatbot

Profilbild von Veaz
Veazvor 1 Jahr

Chatbot

Profilbild von Felix L.
Felix L.vor 1 Jahr

Chatbot

Profilbild von 0x
0xvor 1 Jahr

chatbot

Profilbild von Deshawn Smith
Deshawn Smithvor 1 Jahr

Chatbot

Profilbild von Jeremy Henricks
Jeremy Henricksvor 1 Jahr

chatbot

Profilbild von Marko van Kampen
Marko van Kampenvor 1 Jahr

chatbot

Profilbild von Brent Cosnett
Brent Cosnettvor 1 Jahr

Chatbot

Ähnliche Videos

The number one question I get in the Claude Code / Cowork Community: "how do I share my Cowork skills with my team?" Here's the problem. You build a great skill. You zip it up. You drop it in Slack. Your teammate downloads it, uploads it, and maybe it works. Maybe they upload it wrong. Maybe you update the skill next week and nobody gets the new version. You're now maintaining skills through chat messages and hoping for the best. That doesn't scale. I just put out a video breaking down the three methods I've tested for sharing skills and plugins across a team. From dead simple to fully synced. Method 1: Shared drive (Google Drive, SharePoint, etc). You put your skill files in a shared folder. Teammates download and upload them into Cowork. It works, but updates are manual and there's no version control. Method 2: Built-in sharing on Team and Enterprise plans. You can share any skill directly with a colleague or publish it to your org directory. When you update the skill, everyone gets the update automatically. This is the easiest path if you're on a paid plan. The catch: there's no approval workflow for org-wide sharing, so set a clear owner. Method 3: GitHub repo. This is what I use. Your entire Cowork workspace -- skills, plugins, claude.md, folder structure, project files -- lives in a private repo. Teammates clone it. When you push an update, they pull it. Everyone stays in sync. You get version history, access control, and a single source of truth. The GitHub method sounds technical, but it's really just two steps: clone the repo, point Cowork at the folder. I walk through the whole thing in the video, including how to use .gitignore to keep personal files (like your morning briefing) out of the shared repo. This works for Cowork, Claude Code, and Open Codex. The infrastructure is the same. Full video linked below. If you've found a different approach that works for your team, I want to hear about it. Comment or reply and let's figure out the best practices together.

JJ Englert

16,176 Aufrufe • vor 3 Monaten