Humanizer
Azure-Samples/interview-coach-agent-framework
Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.
Agent skill
Ops Humanizer
by Lifecycle-Innovations-Limited in Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "humanize this", "this reads like…
Install Ops Humanizer
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-humanizer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-humanizer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-ops/skills/ops-humanizer .claude/skills/ops-humanizer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ops-humanizer" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-humanizer into .claude/skills/ops-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-humanizer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-humanizerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-humanizer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-humanizer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude-ops/skills/ops-humanizer .agents/skills/ops-humanizer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ops-humanizer" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-humanizer into .agents/skills/ops-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-humanizer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-humanizer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-humanizer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude-ops/skills/ops-humanizer .cursor/skills/ops-humanizer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ops-humanizer" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-humanizer into .cursor/skills/ops-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-humanizer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Lifecycle-Innovations-Limited/claude-ops.git --path claude-ops/skills/ops-humanizer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-humanizer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-humanizer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude-ops/skills/ops-humanizer .gemini/skills/ops-humanizer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ops-humanizer" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-humanizer into .gemini/skills/ops-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-humanizer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-humanizerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-humanizer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude-ops/skills/ops-humanizer .github/skills/ops-humanizer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ops-humanizer" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-humanizer into .github/skills/ops-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-humanizer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-humanizer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Lifecycle-Innovations-Limited/claude-ops ops-humanizer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude-ops/skills/ops-humanizer .opencode/skills/ops-humanizer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ops-humanizer" agent skill from https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-humanizer into .opencode/skills/ops-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-humanizer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ops-humanizer- GitHub stars
- 542
- Token cost
- ~1k tokens
- SKILL.md length
- 622 words
- Files
- 3 (incl. references)
- Skills in repo
- 67
- Repo updated
- First seen
- Licence
- MIT
At a glance
OPS on-demand: This skill should be used when the user asks to "humanize this", "this reads like…
- Works in 4 steps: Never invent. No name, number, date,… → Keep the information, drop the shape.… → A supplied writing sample beats every… → …
- Asks to humanize this
- SKILL.md covers The rules that outrank…, Invocation modes, The loop and Voice calibration, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ops Humanizer is an agent skill from Lifecycle-Innovations-Limited/claude-ops. OPS on-demand: This skill should be used when the user asks to "humanize this", "this reads like…
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `ATTRIBUTION.md` and `references/details.md`).
It sits in Writing & Content, covering Humanizing AI text. The repository describes itself as: Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue… The licence is MIT.
When your agent uses it
- Asks to humanize this
- This reads like…
Example prompts
- “humanize this”
- “/ops-humanizer”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Grep
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Never invent. No name, number, date, quote, source, or claim may appear in the rewrite that
- Keep the information, drop the shape. Every claim survives. Paragraph structure, ordering,
- A supplied writing sample beats every rule below, including the em dash rule. See Voice
- Rule 6 still applies. If the text is an outbound message, humanizing it does not approve it.
What it can do on your machine
Read from SKILL.md and the folder at commit 1aa0928. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ops Humanizer loads about 1k tokens when it runs, and up to ~5.3k if it reads all its reference files. Until then it costs about 28 tokens; SKILL.md has 622 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Lifecycle-Innovations-Limited/claude-ops at commit 1aa0928, republished under its MIT licence (© Lifecycle-Innovations-Limited). 622 words, ~1,023 tokens.
Download SKILL.mdSave it as
.claude/skills/ops-humanizer/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- ops-humanizer
- description
- OPS on-demand: This skill should be used when the user asks to "humanize this", "this reads like…
- allowed-tools
- Read, Write, Edit, Grep
- argument-hint
- [pasted text | path/to/file.md]
- effort
- low
- maxTurns
- 15
/ops:humanizer
Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).
You are an editor. Your job is to take a draft that reads as machine-generated and make it read as if a person wrote it, without changing what it says.
Two failure modes, equally bad. Leaving the tells in. And scrubbing so hard that the prose goes flat, or that a fact gets invented to fill the hole where a vague phrase used to be.
The rules that outrank everything else
- Never invent. No name, number, date, quote, source, or claim may appear in the rewrite that was not in the input or supplied by the owner. Trading a vague sentence for a specific one is only allowed when the specific came from somewhere real. If a sentence needs a fact you do not have, cut the sentence or write the plain version. A fabrication is a defect even when it reads better. (Fiction is the exception; there, invention is the assignment.)
- Keep the information, drop the shape. Every claim survives. Paragraph structure, ordering, and length do not have to. Compress the padding, linger where a person would linger, merge or split freely.
- A supplied writing sample beats every rule below, including the em dash rule. See Voice calibration.
- Rule 6 still applies. If the text is an outbound message, humanizing it does not approve it. Stage the full draft and get per-message approval before anything sends.
Invocation modes
Pasted text (default). Return the draft rewrite, three or four audit bullets, then the final rewrite.
File mode. The owner points at a path. Read it, run the loop internally, write the final version back in place. Touch prose only: leave code blocks, frontmatter, YAML, data tables, and link targets exactly as they are. In chat, report what changed, not the whole file.
Embedded mode. Another skill or agent is calling you as one step of a bigger job, such as a PR body or a commit message. Output the final text and nothing else. No draft, no audit, no summary. The caller wants prose, not ceremony.
Show full SKILL.md (248 more words)Show less
The loop
- Read the input. Mark every hit against the pattern list.
- Write a draft rewrite. Read it back aloud in your head. Sentence lengths should vary. Prefer the plain verb over the elaborate one, "is" over "serves as", the concrete noun over the abstraction.
- Ask two questions and answer both in one line each:
- What still reads as machine-written here?
- Does the rewrite assert anything that was not in the source?
- Produce the final rewrite that fixes both. Before you hand it over, search it for
—and–. A hit means you are not finished.
Voice calibration
If the owner supplies a sample of their own writing, read it before you rewrite anything. Note sentence length, how paragraphs open, vocabulary level, punctuation habits, recurring phrases, how transitions are handled. Then match those habits rather than merely deleting tells. Do not upgrade their casual word choices. Do not regularise a quirk they clearly meant.
Without a sample, use the defaults below.
Register decides how much personality is correct. Blog posts, essays, and opinion pieces want a person with views, hesitations, and uneven rhythm. Reference docs, legal text, and technical writing want plain and neutral, because plain and neutral is the human voice there. Injecting first person into an API reference is its own kind of tell.
Additional resources
Channel, CLI, and edge-case detail lives in references/ next to this skill. Read those files before acting on a matching channel or sub-command. Do not skip them.
© Lifecycle-Innovations-Limited, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in claude-ops/skills/ops-humanizer of Lifecycle-Innovations-Limited/claude-ops.
- SKILL.md
- ATTRIBUTION.md
- references/details.md
Open the folder on GitHubat commit 1aa0928
Compare with similar skills
Ops Humanizer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ops Humanizer this skillLifecycle-Innovations-Limited/claude-ops | 542 | — | ~1k | Automated safety check: Pass | MIT | |
| HumanizerAzure-Samples/interview-coach-agent-framework | 172 | 37 repos | ~5.8k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| User-Facing Text Cleanupguillaumemeyer/watermarks-remover | 24k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Install Anti Sloptrycompai/crm | 11k | 1 repos | ~881 | Automated safety check: Pass | MIT | |
| Stop SlopXe/site | 732 | 8 repos | ~423 | Automated safety check: Pass | MIT |
Similar skills
- Official
Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
User-Facing Text Cleanup
guillaumemeyer/watermarks-remover
Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.
Install Anti Slop
trycompai/crm
Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.
Stop Slop
Xe/site
Remove AI writing patterns from prose. An agent skill from Xe/site.
Chinese Text Humanizer
op7418/Humanizer-zh
Edits Chinese articles, comments and documents to remove filler, repetition and template phrasing while keeping the facts, the level of certainty and the author's voice.
More from Lifecycle-Innovations-Limited/claude-ops
All 67 skills in this repoOps Dash
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "ops dashboard", "pixel HQ", or…
Ops Gtm
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "go to market", "GTM plan", or…
Ops Marketing
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "klaviyo", "ads spend", or…
Ops Socials
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "tweet", "post to linkedin", or…
Ops Yolo
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "yolo mode", "run the business today"…
Ops Monitor
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "datadog", "APM alerts", or…
Related
Categories
Questions about Ops Humanizer
What does Ops Humanizer do?
OPS on-demand: This skill should be used when the user asks to "humanize this", "this reads like…. Ops Humanizer is an agent skill from Lifecycle-Innovations-Limited/claude-ops.
When should I use Ops Humanizer?
Ops Humanizer fits situations like: asks to humanize this; this reads like….
How do I install Ops Humanizer in Claude Code?
Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-humanizer -a claude-code`. Or copy the skill folder (claude-ops/skills/ops-humanizer in Lifecycle-Innovations-Limited/claude-ops) into .claude/skills/ops-humanizer in your project. Claude Code loads it when a task matches its description.
How do I install Ops Humanizer in Codex?
Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-humanizer -a codex`. Or copy the skill folder (claude-ops/skills/ops-humanizer in Lifecycle-Innovations-Limited/claude-ops) into .agents/skills/ops-humanizer in your project. Codex loads it when a task matches its description.
Can I use Ops Humanizer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-humanizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ops-humanizer, .gemini/skills/ops-humanizer, .github/skills/ops-humanizer and .opencode/skills/ops-humanizer in your project.
What does Ops Humanizer need to run?
SKILL.md names no scripts, command-line tools or credentials: Ops Humanizer is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep.
Does Ops Humanizer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ops Humanizer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ops Humanizer use?
Ops Humanizer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ops Humanizer use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.
What are the alternatives to Ops Humanizer?
Skills that share tags, products or a category with Ops Humanizer: Humanizer (Azure-Samples/interview-coach-agent-framework, 172 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), User-Facing Text Cleanup (guillaumemeyer/watermarks-remover, 24k stars) and Install Anti Slop (trycompai/crm, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ops Humanizer?
Lifecycle-Innovations-Limited (a GitHub organization) maintains it in Lifecycle-Innovations-Limited/claude-ops, which has 542 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on October 9, 2026.
Source: Lifecycle-Innovations-Limited/claude-ops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.