Skilldocs

This is awesome! I have the wrong mental model for the MCP server install, though, and could use some help. I clicked on the "Claude Code can work in here" and am following the instructions. To install the MCP server using this command, do I need to check out a local copy of skilldocs source code? (Very sorry if this is obvious in docs that I should have seen.)```claude mcp add skilldocs -e SKILLDOCS_TOKEN= -- node /mcp/index.js```

on the source control question - since everyone's already live in the same doc like Figma, I'm not sure you actually want git branches, branching is for when people edit in isolation and need to reconcile later, which is the opposite of what you've built. what I'd actually want is lighter: the ability to name/tag a version before I hand the diff to my coding agent, so if the agent runs with a bad version of the skill I can point back to "the one from tuesday's meeting" instead of reconstructing it from memory. real branching only starts to matter once two agents are independently proposing edits to the same skill without a live human session tying them together, which sounds like a later problem, not a v1 one.

Skilldocs solves a surprisingly awkward collaboration gap! How are you thinking about source control once multiple people and agents are editing the same skill? Will comments and diffs eventually map cleanly back to Git branches/PRs?

Collaborating on .md files is a pain - we paste them into Notion, or open them locally and screenshare. Then after we edit and comment on them, there's no easy way to get the feedback back into the coding agents. So...I built Skilldocs. I picked the best features of some of my favorite products: @HackMD 's mono viewer, @Figma 's live cursors + follow (no screenshare necessary), Google Docs' real-time highlighting and comments, and @Bear 's beautiful wysiwyg markdown editor. After working on the doc together, leaving comments, and editing it, you can easily copy the diff and comments and send them to your coding agent of choice. I've started using it for collaborative docs in general. It's really fun having a meeting in it. Minor features I love: -Click on a teammates avatar to follow them through a doc or even through switching docs. It's like following in Figma - it feels like screenshare but snappier.-You can cmd+click to create multiple carets and edit several lines at once (after @Sublime ).Right now you can import skills via dropping a .md file, pasting markdown, importing from Github, or from your local machine via an MCP. Export is simple: copy the .md of the current doc, diff, or comments. I haven't built proper team source control yet but I've gotten a few requests - I'd love requests and suggestions here.h/t to @mikekerzhner for early ideation, and @bernatfortet @teamcoscreen @heshamghandour for early testing!