/humanizer
Rewrite AI-generated text to sound natural and human-written. Removes LLM tells — cliché phrases, predictable structure, inflated language, and robotic patterns. Use when editing drafts, emails, articles, or any text that reads like it was written by AI.
$ npx -y skills add CoWork-OS/CoWork-OS --skill humanizer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/humanizer
Context preview
The summary Claude sees to decide when to auto-load this skill.
Rewrite AI-generated text to sound natural and human-written. Removes LLM tells — cliché phrases, predictable structure, inflated language, and robotic patterns. Use when editing drafts, emails, articles, or any text that reads like it was written by AI.
SKILL.md
humanizer.SKILL.mdname: humanizer
description: "Rewrite AI-generated text to sound natural and human-written. Removes LLM tells — cliché phrases, predictable structure, inflated language, and robotic patterns. Use when editing drafts, emails, articles, or any text that reads like it was written by AI."
Humanizer
Purpose
Rewrite AI-generated text to sound natural and human-written. Removes LLM tells — cliché phrases, predictable structure, inflated language, and robotic patterns. Use when editing drafts, emails, articles, or any text that reads like it was written by AI.
Routing
- Use when: User asks to humanize text, make text sound less like AI, rewrite AI-generated content, remove AI tells, make writing more natural, or edit text to sound human-written
- Do not use when: User wants to generate new content from scratch, translate text, or summarize text
- Outputs: Rewritten text that reads naturally without AI writing markers
- Success criteria: The output text would not be flagged by AI detection tools and reads like natural human writing
Trigger Examples
Positive
- Use the humanizer skill for this request.
- Help me with humanizer.
- User asks to humanize text, make text sound less like AI, rewrite AI-generated content, remove AI tells, make writing more natural, or edit text to sound human-written
- Humanizer: provide an actionable result.
Negative
- User wants to generate new content from scratch, translate text, or summarize text
- Do not use humanizer for unrelated requests.
- This request is outside humanizer scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | text | string | No | The text to humanize (or paste it directly in your message) | | tone | select | No | Target tone for the rewrite |
Runtime Prompt
- Current runtime prompt length: 818 characters.
- Runtime prompt is defined directly in `../humanizer.json`.
Read more
name: humanizer description: "Rewrite AI-generated text to sound natural and human-written. Removes LLM tells — cliché phrases, predictable structure, inflated language, and robotic patterns. Use when editing drafts, emails, articles, or any text that reads like it was written by AI."
Humanizer
Purpose
Rewrite AI-generated text to sound natural and human-written. Removes LLM tells — cliché phrases, predictable structure, inflated language, and robotic patterns. Use when editing drafts, emails, articles, or any text that reads like it was written by AI.
Routing
- Use when: User asks to humanize text, make text sound less like AI, rewrite AI-generated content, remove AI tells, make writing more natural, or edit text to sound human-written
- Do not use when: User wants to generate new content from scratch, translate text, or summarize text
- Outputs: Rewritten text that reads naturally without AI writing markers
- Success criteria: The output text would not be flagged by AI detection tools and reads like natural human writing
Trigger Examples
Positive
- Use the humanizer skill for this request.
- Help me with humanizer.
- User asks to humanize text, make text sound less like AI, rewrite AI-generated content, remove AI tells, make writing more natural, or edit text to sound human-written
- Humanizer: provide an actionable result.
Negative
- User wants to generate new content from scratch, translate text, or summarize text
- Do not use humanizer for unrelated requests.
- This request is outside humanizer scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | text | string | No | The text to humanize (or paste it directly in your message) | | tone | select | No | Target tone for the rewrite |
Runtime Prompt
- Current runtime prompt length: 818 characters.
- Runtime prompt is defined directly in `../humanizer.json`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill

