Error Prone

v1.0.0

Makes AI-generated text sound more human by intentionally introducing realistic imperfections. Use when writing emails, messages, social posts, or any text t...

0· 129·0 current·0 all-time
byDylan Feltus@dylanfeltus

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for dylanfeltus/error-prone.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Error Prone" (dylanfeltus/error-prone) from ClawHub.
Skill page: https://clawhub.ai/dylanfeltus/error-prone
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install error-prone

ClawHub CLI

Package manager switcher

npx clawhub@latest install error-prone
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the SKILL.md. The skill is instruction-only and only describes text transformations (typos, contractions, tone). It does not request unrelated binaries, environment variables, or config paths.
Instruction Scope
Instructions stay within text-editing: apply errors at different severity levels, preserve meaning, and match context. However there is an internal inconsistency: Rule 1 ('Never break meaning') conflicts with some examples (autocorrect disasters, skipped words, 'massage' vs 'manager') that could change intent or introduce harmful misunderstandings. Also suggestions like 'send as multiple messages' simulate interaction behavior but do not require extra system access.
Install Mechanism
No install spec and no code files — lowest risk. Nothing will be downloaded or executed on disk by the skill itself.
Credentials
No environment variables, credentials, or config paths are requested. The skill does not ask for unrelated secrets or system access.
Persistence & Privilege
always is false and the skill does not request persistent system presence or modify other skills. Autonomous invocation is allowed by default (platform default) but is not excessive here.
Assessment
This skill appears to do what it says: deliberately add human-like imperfections to text. It does not request credentials or install code, which reduces technical risk. Two practical cautions: (1) test outputs before sending in sensitive contexts (legal, medical, security) because some recommended 'errors' could change meaning or produce embarrassing/unsafe results; (2) be mindful of misuse — making text more deceptive is a feature that can enable social-engineering. If you install it, try it on non-sensitive drafts first and review carefully (especially Level 3 outputs). If you need guarantees that meaning never changes, this skill's examples show that guarantee may be hard to achieve in practice.

Like a lobster shell, security has layers — review code before you run it.

latestvk978mwz9nqg9xs55a09stqe2cn8392km
129downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Error-Prone

Make your writing worse on purpose. Because perfect copy is creepy.

AI text has a smell. Too clean, too polished, too correct. People can tell. Error-Prone adds realistic human imperfections so your emails, messages, and posts actually sound like a person wrote them.

How to Use

When asked to write or edit text with error-prone mode, apply imperfections from the levels below. Default to Level 1 unless asked for more chaos.

Levels

Level 1: Professional Human (default)

Subtle. Still competent. Just not suspiciously perfect.

Apply 2-3 of these per paragraph:

  • One typo per ~100 words (teh, adn, hte, becuase, recieve, occured, definately)
  • Occasional missing comma or extra comma
  • Start one sentence with "And" or "But" or "So"
  • Use a contraction where formal writing wouldn't (it's vs it is, we're vs we are)
  • One slightly awkward word choice (use "get" instead of "obtain", "thing" instead of "element")
  • Inconsistent capitalization in lists
  • End a sentence with a preposition ("the team I'm working with" not "the team with which I'm working")

Level 2: Casual Human

Texting-your-coworker energy. Clearly typed fast.

Apply 4-6 of these per paragraph:

  • Everything from Level 1, plus:
  • Double space after a period sometimes
  • "lol" or "haha" once per message
  • Trailing off with "..."
  • Start with "So" or "Anyway" or "Yeah so"
  • Run-on sentence (join two sentences with "and" instead of a period)
  • Gonna, wanna, kinda, sorta
  • Skip a word that the brain fills in ("I think we should [go] with option B")
  • Lowercase sentence starts occasionally
  • "me and Dylan" instead of "Dylan and I"
  • One autocorrect-style error (ducking, he'll instead of hell)

Level 3: Unhinged

Sent from my phone while walking. Stream of consciousness. Autocorrect chaos.

Apply 8+ of these per paragraph:

  • Everything from Level 1-2, plus:
  • Multiple typos per sentence
  • No punctuation for 2-3 sentences then suddenly perfect punctuation
  • Repeated words ("I think think we should")
  • Wrong homophone (their/there/they're, your/you're)
  • Abandon a sentence halfway and start a new thought
  • ALL CAPS for one word for emphasis
  • "idk" "tbh" "ngl" "imo"
  • Emoji that's slightly wrong context (using 💀 to mean "that's funny")
  • Send as multiple messages instead of one (simulate hitting enter too early)
  • "wait no" or "actually nvm" corrections
  • Autocorrect disasters ("I'll ask the massage" instead of "manager")

Rules

  1. Never break meaning. Imperfections should not change what the text says. A reader should still understand the message perfectly.
  2. Match the context. Professional email = Level 1. Slack message = Level 2. Tweet reply = Level 2-3.
  3. Vary the errors. Don't use the same typo twice. Real humans make different mistakes.
  4. Don't overdo it. The goal is "human" not "illiterate". Even Level 3 should be readable.
  5. Preserve the user's voice. Add imperfections to THEIR style, don't change what they're saying.

Examples

Before (AI-generated):

I wanted to follow up regarding our conversation about the Q3 marketing strategy. I've prepared a comprehensive analysis of the proposed budget allocation and would appreciate the opportunity to discuss it at your earliest convenience.

After (Level 1 — Professional Human):

I wanted to follow up on our conversation about the Q3 marketing strategy. I've put together an analysis of the proposed budget allocation and would love to discuss it when you get a chance.

After (Level 2 — Casual Human):

Hey, wanted to follow up on our q3 marketing convo. I put together a budget analysis thing... would love to chat about it when you get a sec

After (Level 3 — Unhinged):

hey so I did that budget analysis for q3 marketing its actually pretty interesting ngl anyway lmk when your free to chat about it *you're lol

Comments

Loading comments...