DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to turn your notes or transcript into a human-sounding work piece with Work Humanizer

Build a post or memo on your own argument, order and examples instead of an AI draft.

Who it is forA team lead or founder with rough notes or a voice-memo transcript who needs a launch post, update or internal memo that sounds like them.

The problemAI drafts flatten a person's reasoning, and the test found the most human results came from the writer's own notes.

The outcomeA piece that keeps your claims, their order and your examples, with questions only where your notes leave gaps.

What you need first

  • An agent that loads SKILL.md, such as Claude Code, Codex or Cursor
  • The skills/work-humanizer folder copied into the agent's skills folder
  • Your draft or notes as text
  • Python, only if you want to run check.py

Steps

  1. Copy the skills/work-humanizer folder into your agent's skills folder if you have not already.
  2. Send: Use Work Humanizer on this: followed by your notes or transcript pasted in.
  3. Check the skeleton it builds from your claims and examples, and answer any questions about gaps.
  4. If it offers a shorter option, decide whether to use it, since it never cuts on its own.
  5. Read the final fact audit and confirm nothing from your notes was dropped or strengthened.

Prompt for your agent

Use the work-humanizer skill from the phuryn/work-humanizer repo on my notes in <notes-file>. Build the piece on my claims, in my order, with my examples, and ask only about gaps. Output the piece and the fact audit. Verify that each claim in the piece matches a claim in my notes at the same strength.

Caveat. The README says that rewriting an AI draft on its own still lands near the same AI detector scores, so the gain comes from your own reasoning, and the detector results rest on 4 texts for the notes case.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page