Open a skill, and everyone is in it at once - real cursors, inline comments, and an editor that renders as you type. Then hand the whole conversation + diff back to the agent.
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.
Skilldocs launched on Product Hunt on August 13th, 2026 and earned 159 upvotes and 10 comments, placing #7 on the daily leaderboard. Open a skill, and everyone is in it at once - real cursors, inline comments, and an editor that renders as you type. Then hand the whole conversation + diff back to the agent.
On the analytics side, Skilldocs competes within Productivity, Developer Tools and Artificial Intelligence — topics that collectively have 1.7M followers on Product Hunt. The dashboard above tracks how Skilldocs performed against the three products that launched closest to it on the same day.
Who hunted Skilldocs?
Skilldocs was hunted by Rajiv Ayyangar. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Skilldocs including community comment highlights and product details, visit the product overview.
Rajiv Ayyangar
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!