— ◌ Hidden
Viewing an old version — read-only
✎ Mono editing at 2 places · Esc to stop
👁 Preview editing at 2 places · Esc to stop · editable ·
Connecting — read-only copy
± Diff read-only — vs the last marked version
?
Someone is sharing their view
skilldocs

Sign in

SkillDocs is for the Product Hunt team. Sign in with your work Google account.

New here? Take the tour → Privacy

Copy this

Your browser wouldn't let the page write to the clipboard. It's selected — hit ⌘C.

Connect a GitHub repo

Paste a repo link — SkillDocs scans the whole repo for markdown skills, then you choose what to bring in. Public repos need no token.

Open GitHub's token page and: 1. name it anything (say, "SkillDocs") · 2. under Repository access choose Only select repositories and pick this repo · 3. under Permissions → Repository permissions set Contents to Read-only · 4. hit Generate token, copy the github_pat_… string, and paste it below. It's stored server-side for this workspace and never shown again.

New version — reload

This tab is running an older build of SkillDocs and its edits are paused to protect the document. Your unsaved changes come along with the reload — nothing is lost.

Feedback

What's broken, missing, or confusing? I read every piece of feedback that comes in.
— Rajiv · rajivayyangar@gmail.com

SkillDocs ⌁ Claude Code

The SkillDocs MCP server lets an agent work the review loop with you: push a local skill up, read back the team's edits and comments, reply, and pull the text down.

1 · Register the server Paste this into your terminal. Nothing to install — no Node, no clone; the server runs here. 

      
      Copying mints your API token and pastes it in — nothing to fill in by hand. It stays off the screen, but it does land in your clipboard and your shell history. Valid a year, scoped to this workspace.
    

    
2 · The tools
      skilldocs_open push a skill up, get its URL · skilldocs_read doc + threads · skilldocs_diff what changed vs the baseline · skilldocs_comments open threads · skilldocs_reply / skilldocs_resolve answer feedback · skilldocs_pull the collaborated text, back to your file
    

    
Typical loop: "push skills/triage/SKILL.md to skilldocs" → team comments here → "read the skilldocs diff and comments, apply the feedback, reply to the threads."

    

      Other clients, or running it locally
      Any client that speaks HTTP takes the same URL and header — Claude Desktop, Cursor. For one that only speaks stdio, there's an npm package that does your file reading and writing for you:
      

      Needs Node 18+. From a clone instead: git clone https://github.com/rajivayyangar/skilldocs, then cd skilldocs/mcp && npm install, and point the command at node $PWD/index.js rather than npx.
    

    

      
    

  






  

    
Version history

    
Versions are snapshots you (or an import) marked. Past versions are read-only — you can view and copy them, and restore one to make it the current text.

    

    

      
    

  






  

    
Changes since the baseline

    

    

    

      
      
      
    

  






  

    
Move to section

    
Pick a section, or type a new name.

    

    
    

      
      
    

  






  

    
New doc

    
Paste a GitHub link to a skill, or paste the markdown itself.

    
    

      
    

    
 

    
That looks like a whole repo — 

    

    

      
      
    

  






  

    
Share this doc

    

    
    
Copy as text

    

      
      
      
      
    

    
⌁ Get it into an agent: the SkillDocs MCP server lets Claude Code push this doc up, read back the diff and comments, and reply. 

    

      
    

  









  

    
Multi-cursor

    

      
⌘clickadd a cursor (⌥click works too)

      
⌘Dselect next occurrence of the selection

      
esccollapse back to one cursor

      
⌘Zundo · ⌘⇧Z redo

      
⌘Ffind · ⌘G find next