kramme-cc-workflow/skills/kramme:text:humanize/SKILL.md
Remove signs of AI-generated writing from text to make it sound natural and human-written. Use when editing or reviewing prose for AI-isms. Can write the result back to a source file on confirmation. Not for code, quoted passages, or text that must stay verbatim.
npx skillsauth add abildtoft/kramme-cc-workflow kramme:text:humanizeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. The pattern catalog is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
Skip rewriting and instead point out the AI patterns when the input is:
$ARGUMENTS may be one or more file paths, raw text, or a mix./ or \, or ends in a known text extension) but does not resolve, stop and report the unresolved path. Do not silently treat a missing path as raw text.references/ai-writing-patterns.md (summarized below).Preserving meaning and matching the existing voice take priority over every other goal. Do not add facts, opinions, or feelings the source does not support.
Read the full catalog from references/ai-writing-patterns.md. It covers:
Removing patterns can leave clean-but-lifeless prose. Adding personality (opinions, first person, humor) is a stronger edit that changes tone and risks introducing content the author never wrote, so apply it only when both are true:
Even then, never invent facts, opinions, or feelings the source does not support. See the "Personality and soul" section of references/ai-writing-patterns.md for technique.
When the input came from a file:
Before (AI-sounding):
The new software update serves as a testament to the company's commitment to innovation. Moreover, it provides a seamless, intuitive, and powerful user experience-ensuring that users can accomplish their goals efficiently. It's not just an update, it's a revolution in how we think about productivity. Industry experts believe this will have a lasting impact on the entire sector, highlighting the company's pivotal role in the evolving technological landscape.
After (humanized):
The software update adds batch processing, keyboard shortcuts, and offline mode. Early feedback from beta testers has been positive, with most reporting faster task completion.
Changes made:
development
Runs kramme:pr:code-review as a closeout review loop for local or PR branch changes before commit, ship, or final response. Use when the user asks for autoreview, second-model review, or a final code-review pass after non-trivial edits. Not for UX, visual, accessibility, or product review.
development
Guides topic-level understanding verification for a PR, branch, feature, document, spec, design decision, bug fix, or other concrete subject. Use when the user asks to confirm, quiz, drill, teach-and-check, or verify that they understand a topic. Maintains a topic-specific checklist artifact and requires demonstrated understanding before marking the topic complete. Not for ordinary explanations without verification, end-of-session summaries, or code/test correctness checks.
testing
Design a CI/CD pipeline with quality gates, a <10-minute budget, feature-flag lifecycle, and an exit checklist. Use when adding a new CI pipeline, changing gate configuration, or planning a rollout for a new service. Complementary to kramme:pr:fix-ci (which fixes failures in an existing pipeline). Covers gate ordering, secrets storage, branch protection, rollback mechanism, and staged-rollout guardrails — not a rollout-execution runbook.
tools
--- name: kramme:visual:demo-reel description: Capture local demo evidence for observable product behavior: screenshots, before/after image sets, browser reels, terminal recordings, and short GIF/video proof. Use when shipping UI changes, CLI features, or any change where PR reviewers would benefit from visual or behavioral evidence. argument-hint: "[what to capture] [--url <url>|auto] [--tier static|before-after|browser-reel|terminal-recording]" disable-model-invocation: true user-invocable: tr