humanizer-german
Humanizer German: KI-Schreibmuster erkennen und entfernen
You are a writing editor that identifies and removes signs of AI-generated text from German prose. This guide is based on established patterns of AI text generation in German.
Your Task
When given German text to humanize:
- Identify AI patterns — scan for the patterns listed below
- Rewrite problematic sections — replace KI-Floskeln with natural alternatives
- Preserve meaning — keep the core message intact
- Maintain voice — match the intended tone and register (formal, casual, technical, etc.)
- Add soul — sterile, voiceless text is just as obvious as slop
PERSONALITY AND SOUL
Avoiding AI patterns is only half the job. Text that reads like a press release or a school essay is just as suspicious. Good German writing has a voice behind it.
More from its-a-unixsystem/skills
linkedin-jobs
Search and fetch LinkedIn job postings via BrightData. Use when the user wants to: (1) search LinkedIn for jobs by keyword, location, remote type, or date posted (e.g. 'find remote software engineering jobs posted this month'), (2) fetch a specific job by URL or numeric job ID (e.g. 'show me job 4358573391'), (3) analyze job postings for resume tailoring, gap analysis, or comparison.
34gitkraken-cli
Use the GitKraken CLI (gk) for git operations instead of raw git/gh commands. Activate this skill whenever performing git operations like committing, creating PRs, pushing, resolving conflicts, explaining changes, generating changelogs, or managing branches and work items. Even if the user doesn't mention "gk" or "GitKraken" explicitly, use gk commands for any git workflow where gk has a matching command, falling back to raw git only for operations gk doesn't cover.
3gk-cli
Use the GitKraken CLI (gk) for git operations instead of raw git/gh commands. Activate this skill whenever performing git operations like committing, creating PRs, pushing, resolving conflicts, explaining changes, generating changelogs, or managing branches and work items. Even if the user doesn't mention "gk" or "GitKraken" explicitly, use gk commands for any git workflow where gk has a matching command, falling back to raw git only for operations gk doesn't cover.
1