← Products

Writing
⚙ Needs: the text to humanize (pasted in the conversation) —…

Humanizer — rewrite AI-sounding prose using Wikipedia's "Signs of AI writing" patterns

Remove 35 AI-writing patterns — inflated claims, sales language, overused AI words, em dashes, chatbot artifacts — while keeping every fact and matching the writer's voice

At a glance
What
Remove 35 AI-writing patterns — inflated claims, sales language, overused AI words, em dashes, chatbot artifacts — while keeping every fact and matching the writer's voice
Cost
Free
Needs
the text to humanize (pasted in the conversation) — optionally a writing sample of yours so the agent can match your voice
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @ztemerbekov
⌁

Install

Prerequisites: the text to humanize (pasted in the conversation) — optionally a writing sample of yours so the agent can match your voice Install "Humanizer — rewrite AI-sounding prose using Wikipedia's 'Signs of AI writing' patterns" for me. It gives my agent @ztemerbekov's humanizer playbook: mark the 35 AI-writing patterns in the text, keep every fact and claim (never invent), match the writer's voice (a supplied writing sample takes priority), preserve the text's language, draft and read aloud, then do the final pass — checking no fact was added or lost and stripping each flagged dash — and return the draft, the remaining patterns, and the final rewrite (or embedded mode: just the final text), watching the false-positives guidance so real human quirks survive. MIT licensed. Repository: https://github.com/ztemerbekov/a1-marketing-skills/blob/main/skills/a1-humanize/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "a1-humanize". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. paste the text to rewrite and, ideally, a sample of my own writing for voice matching; strip the A1 Telegram footer if I don't want it). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.