Skill

to-pseudobot

Rewrite text to feel obviously bot- or AI-generated — programmatic artifacts, fake server-glitch fragments, slightly-broken phrasing, overly-neutral tone. Use when the user wants a message that reads like a malfunctioning auto-responder.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin novelty-text-editor

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Rewrite the user's text so it reads as if a program or AI generated it — including subtle "glitches" that suggest a server error during generation.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars0

Forks0

Last CommitApr 30, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

To-Pseudobot

Rewrite the user's text so it reads as if a program or AI generated it — including subtle "glitches" that suggest a server error during generation.

Rewrite rules

Insert programmatic artifacts: phrases like "auto-generated message," "generated by AI," "bot-generated response," "[BEGIN_AUTOMATED_REPLY]".

Introduce subtle errors: extra spaces, accidental word repetition, half-truncated sentences. Example: "Please do not hesitate to hesitate to reach out."

Faux server / system glitches: drop in lines like ERROR: Unable to fetch recipient data, Processing delay: 5 seconds, Message generation incomplete — please disregard if irrelevant.

Random text fragments: meaningless filler — "Fetching data," "Attempting connection," "Thank you for your patience — end of line."

Tone: maintain a formal or overly-neutral register, as though the message wasn't really meant for a human.

Preserve factual content; the glitches should feel incidental, not destroy the message.

Inputs

Source text — inline, clipboard, or file path.

Glitch density (optional) — light / medium (default) / heavy.

Output

Print the pseudobot version to stdout. With --in-place, overwrite the source.

Honesty note

Don't use this on text being sent to someone who would mistake it for a real automated system message in a way that causes harm (e.g. fake bank notices). It's a novelty/comedy transform.

To-Pseudobot

Rewrite the user's text so it reads as if a program or AI generated it — including subtle "glitches" that suggest a server error during generation.

Rewrite rules

Insert programmatic artifacts: phrases like "auto-generated message," "generated by AI," "bot-generated response," "[BEGIN_AUTOMATED_REPLY]".
Introduce subtle errors: extra spaces, accidental word repetition, half-truncated sentences. Example: "Please do not hesitate to hesitate to reach out."
Faux server / system glitches: drop in lines like ERROR: Unable to fetch recipient data, Processing delay: 5 seconds, Message generation incomplete — please disregard if irrelevant.
Random text fragments: meaningless filler — "Fetching data," "Attempting connection," "Thank you for your patience — end of line."
Tone: maintain a formal or overly-neutral register, as though the message wasn't really meant for a human.
Preserve factual content; the glitches should feel incidental, not destroy the message.

Inputs

Source text — inline, clipboard, or file path.
Glitch density (optional) — light / medium (default) / heavy.

Output

Print the pseudobot version to stdout. With --in-place, overwrite the source.

Honesty note

Don't use this on text being sent to someone who would mistake it for a real automated system message in a way that causes harm (e.g. fake bank notices). It's a novelty/comedy transform.