Emil Novak

Two weeks of SkillDocs
I launched SkillDocs on August 12 collaborative markdown for the files that teach your agents how to work. Live cursors, inline comments, and an MCP server so the agent works the same loop you do.
Here's what's landed since. Full changelog with screenshots: https://skilldocs.dev/changelog
New things:

• tables are a live grid you edit in place, not a picture that falls apart the moment you click into it.

• Focus mode on F. Try it. it's beautiful.

• Nested folders, and any folder opens as a sortable table.

• `skilldocs_find`, so an agent coming back tomorrow can ask "which doc is this file?" instead of needing an id it no longer has.

• MCP moved to a URL nothing to install, works in any client with OAuth, so no year-long token travels through your shell history.

• Paste a GitHub repo URL and pick what to import.

• Comments now pin to characters in the CRDT, so editing inside a quoted phrase stops orphaning the thread.
  Here are three of my favorite improvements:
  Dark theme

  

  It toggles from three places: the next to the wordmark, the on the style bar, and Appearance in the settings menu. One state, three doors. Each cycles Light Dark Match system, and Match system follows the OS live. Plus - I love how the logo looks in dark mode.
  The skill listener

  

  Nobody knows which skills their team actually uses. You can guess from the repo, but the repo tells you what exists, not what runs.
  Merge a two-file hook into your skills repo and counting starts for everyone no per-person setup, no token to paste. Identity comes from git email, and the server accepts a claimed count only when the named repo is a connected source of that workspace, so nobody can inflate someone else's numbers. It sends the skill name, the repo, a git email and a timestamp. Never prompts, never arguments, never file contents. `SKILLDOCS_LISTENER=off` opts out.
  The same beacon carries a hash of your local skill file. If it differs from the doc's latest published version, your agent gets one short note, at most twice per version, then it stays quiet. Nothing ever writes a skill file for you.
  K palette

  

  Jump to a doc, run a command, enter focus mode, format the selection, or change the theme. All from K. h/t @Superhuman
  ---
  If you're writing skills with other people, I'd genuinely like to know where this breaks for you. I'm trying to make this the most collaborative, beautiful way to review and edit skills.

Big launch coming in four weeks.

Most agent tooling stops at the classic Observe - Evaluate loop. You can stop, pause, insert a human into your flows. But it mostly happens in development. Once agents hit production they're on their own, and engineers lean on Sentry or PostHog to find out something broke. Then improvement is you, by hand: digging through traces, tuning a prompt, redeploying, hoping.

I spent a long time thinking at the code level.

Take an issue. Write code. Open a PR. Smoke test it. Fix CI. Debug. Review. Merge.

When I started using agents, I carried that same workflow across:

Take issue X. Refine it first. Follow the acceptance criteria. Implement it. Review the output. Smoke test it. Rebase it for human review.