Token导航 LogoToken导航TokenDH.com
效率需要联网clawhub未标认证来源可访问clear审计通过

error-prone容易出错

Agent Skill

error-prone 用于记录任务执行中的错误、用户纠正、经验和能力缺口,适合在 OpenClaw 中希望让 Agent 持续沉淀问题、修正和最佳实践时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

4,005

周安装

162

GitHub Stars

公开资料未说明

下载量

1,257
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:error-prone(容易出错)
来源仓库:https://github.com/dylanfeltus/error-prone
安装命令:
openclaw skills install error-prone
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install error-prone

简介

通过故意引入现实缺陷,使 AI 生成文本更贴近人类表达风格。

  • 适用于撰写邮件、消息、社交帖子等需要自然语境的文本场景。
  • 调用时需提供原始文本及期望的“人性化”程度参数。error-prone 属于效率类 Skill,可作为该场景下的辅助能力补充。
  • 通过 clawhub 安装,需确认是否允许修改输出内容及潜在格式风险。
  • 注意避免在不适场景下使用,以防误导或降低专业性。

SKILL.md

name
error-prone
description
Makes AI-generated text sound more human by intentionally introducing realistic imperfections. Use when writing emails, messages, social posts, or any text that needs to feel authentic and not AI-generated. Triggers on phrases like "make it sound human", "add imperfections", "make it less AI", "humanize this", "error-prone mode", or when the user wants copy that doesn't feel robotic.

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

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

76.25%
按下载量换算958

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills