Show HN: GitHub Copilot Technical Writing Skill

github.com

4 pointschris_money2022 comments

Its not super fancy, but I have found it useful from small emails to larger design docs so thought I would share.

I like it, putting established knowledge in skill form is not difficult or great innovation, but definitely useful and worthy to share. I would critique one or two things: For skills like this, which are intended to be shared and but at the same time not complete "frameworks", I think skills should be atomic. For this i would split it into the technical writing guidelines (tone, grammar, etc) and the workflow (drafts, review, the specific folders). Agents should be able to discover and load both without a problem, but it makes it easier for other people to pick-and-chose.

Secondly, I'd combine one/two into one markdown file each. I don't want the reviewer / writer to selectively read those, since a review always needs to apply all of them. I get that the goal of scoping the review procedure into 10 individual steps is to create more focus on each task by giving it its own procedure step, but in my experience doing small focused steps like that will lead to much longer review times and worst case a very fragmented text, because small edits are applied on top of each other, without considering the big picture. A recent LLM with sufficient reasoning should be able to apply all rules in one go.

Thanks for feedback! I’ll incorporate this

Reply on news.ycombinator.com