— ◌ 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

Connect an agent to SkillDocs

Any MCP client can 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 · The server One URL, every client. Nothing to install — no Node, no clone; the server runs here. 

      
    

    
2 · Your client
      

      

      
      
      
    

    
3 · 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."

    

      Clients that only speak stdio
      Everything above is the remote server over HTTP. For a client that can't do HTTP at all, there's an npm package that runs locally and does your file reading and writing for you — not published yet, so this line won't resolve until it is:
      

      Needs Node 18+. Until it's published there's no public clone either — the server lives in a private repo — so a stdio-only client can't be set up from here yet. Everything above (HTTP) works today.
    

    

      
    

  






  

    
Install this skill

    

    
1 · Paste this into Claude Code
      Pulls this doc's current text, writes the skill file — and listens for updates, so you're told when this doc moves ahead of your copy.
      

      
    

    
2 · Only if you don't have the plugin yet
      Once per machine. The listener rides along with it — it's a Claude Code hook, which is why only this route can carry it.
      

      
    

    

      No plugin — just the MCP server (no update notices)
      Paste this to any agent connected to SkillDocs. You get the skill, but not usage counting or update notices: those ride on a Claude Code hook, and an MCP server can't register one.
      

      
    

    

      By hand, no agent (no update notices)
      Save the markdown as . Claude Code loads skills at startup, so it's live in your next session. Nothing watches it afterwards — when this doc changes, your copy won't know.
      
    

    
    
    

      
    

  






  

    
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 folder

    
Pick a folder, 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 an agent 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

    

    
  







  

    
    

    

      ↑↓ move↵ runesc close
      searches titles · try “focus”, “dark”, “bold”