humanizer

Other Community v2.7.0

Skill notes

Your Task

When given text to humanize: Identify AI patterns - Scan for the patterns listed below. Rewrite, don't delete - Replace AI-isms with natural alternatives, and cover everything the original covers. If the original has five paragraphs, the rewrite has five paragraphs. Preserve meaning - Keep the core message intact. Match the voice - Fit the intended tone (formal, casual, technical). Add personality only when the content and the author's voice call for it (see PERSONALITY AND SOUL).

Voice Calibration (Optional)

If the user provides a writing sample (their own previous writing), analyze it before rewriting: Read the sample first. Note: Sentence length patterns (short and punchy? Long and flowing? Mixed?) Word choice level (casual? academic? somewhere between?) How they start paragraphs (jump right in? Set context first?)

How to provide a sample

Inline: "Humanize this text. Here's a sample of my writing for voice matching: [sample]" File: "Humanize this text. Use my writing style from [file path] as a reference."

PERSONALITY AND SOUL

Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it. Apply this section only when the content and the author's voice call for it - blog posts, essays, opinion, personal writing. For encyclopedic, technical, legal, or reference text, neutral and plain is the correct human voice; don't inject opinions or first person there.

Signs of soulless writing (even if technically "clean"):

Every sentence is the same length and structure No opinions, just neutral reporting No acknowledgment of uncertainty or mixed feelings No first-person perspective when appropriate No humor, no edge, no personality

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@blader · v2.7.0 · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview humanizer-blader.preview
# Process and Output

1. Read the input carefully and identify every instance of the patterns above.
2. Write a **draft rewrite**. Check that it reads naturally aloud, varies sentence length, prefers specific details and simple constructions (is/are/has), and keeps the appropriate register.
3. Ask: **"What makes the below so obviously AI generated?"** Answer briefly with any remaining tells.
4. Revise into a **final rewrite** that addresses them and contains no em or en dashes (see §14).

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.