Humanizer Kill Gpt
Runs a cross-language cleanup for writing tells shared by large frontier LLMs, not only GPT: English source constructs that survive other language translation and language-surface translationese. Use only when the user asks to remove AI/GPT tells from text (de-GPT, GPT 티, AI 티, 번역체 GPT, 자폐 말투 — colloquial shorthand for rigid or over-complete model prose, not a claim about autism).
Install
/plugin marketplace add kargnas/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add kargnas/skills --skill humanizer-kill-gptgit clone --depth 1 https://github.com/kargnas/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/humanizer-kill-gpt ~/.claude/skills/humanizer-kill-gptPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Humanizer: Kill GPT Tells When starting, let the user know in one line that this skill is being used. Remove recurring AI-writing fingerprints from English and Korean text. Despite the skill name, these patterns are not unique to GPT: large frontier language models commonly converge on the same over-complete, over-explained, overly balanced, and translation-shaped prose. The catalog keeps “GPT tell” as a familiar shorthand. Some users call this style `자폐 말투`. Treat that phrase only as colloquial request vocabulary for rigid or socially miscalibrated model prose. MUST NOT equate the writing patterns with autism or use the phrase to characterize autistic people. Most translated Korean tells start upstream: an English model-writing construct survives literal translation. This skill therefore uses two coupled passes. | Text situation | Run | |---|---| | English draft | Pass A only | | Korean draft written natively | Pass B only | | Korean translated from English, or English that will be translated to Korean | Pass A first, then Pass B | This skill targets cross-language patterns shared by large frontier models. A broader Korean-language cleanup workflow may cover additional punctuation, spacing, and lexical-distribution patterns that are outside this skill's scope.
Details
- Skill name
humanizer-kill-gpt- Repository
- kargnas/skills
- Path
skills/humanizer-kill-gpt/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Humanizer Kill Gpt skill do?
Runs a cross-language cleanup for writing tells shared by large frontier LLMs, not only GPT: English source constructs that survive other language translation and language-surface translationese. Use only when the user asks to remove AI/GPT tells from text (de-GPT, GPT 티, AI 티, 번역체 GPT, 자폐 말투 — colloquial shorthand for rigid or over-complete model prose, not a claim about autism).
How do I install the Humanizer Kill Gpt skill?
Claude Code plugin: /plugin marketplace add kargnas/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Humanizer Kill Gpt popular?
It lives in kargnas/skills, which has 9 GitHub stars and 1 forks.
Related skills
AI Ready
9kargnas/skills
Use only when the user asks to make the repo AI-ready or AI-optimized (AGENTS.md migration, debugging/testing setup, docs). Do not run on your own.
Design Frontend Sangrak
9kargnas/skills
Use when starting frontend work in a project with no existing design system, when building or theming UI with shadcn/ui or Tailwind CSS, or when asked to review/audit web UI. Default design baseline for new screens, plus container-first responsive rules, URL-first routing, scoped async loading, theme/i18n defaults, and applied UX laws.
Git Lore
9kargnas/skills
Captures, queries, and configures decision context in native Git trailers. Use for non-trivial commit messages, constraints, rejected alternatives, directives, test gaps, Lore history queries, or installing Lore rules in project or global agent instructions.
Industrial Waste Heat Recovery
5dungnotnull/industrial-waste-heat-recovery-agent-skill
Industrial Waste-Heat Recovery System Design — Production-grade evidence-backed analysis harness with flexible agent architecture, skill registry, and modular sub-agents. Use for: waste-heat recovery design, heat exchanger selection, ORC systems, pinch analysis, energy efficiency assessment, industrial thermal system optimization. Triggers on: "waste heat", "heat recovery", "ORC", "pinch analysis", "heat exchanger", "energy efficiency", "thermal optimization", "industrial heat", "steam system", "condensate recovery".
Handoff Spec
9sidneyswift/skills
Produces a single markdown handoff document for a stateless successor agent (possibly on a different platform or session) to pick up in-progress work with zero conversation context. Combines a stable Goal/Spec section with a point-in-time Handoff Status section covering what's done, out-of-scope work, remaining required work, nice-to-haves, what's live in production, what's merged but not deployed, and what's still in progress. Use when the current agent is running low on usage credits, context, or tokens; when the user says things like "I'm running out of credits/usage", "we need to hand this
Long Running Harness
10Archive228/lab-skills
Operating procedure for agent work that spans many context windows: split the run into a one-time initializer session (init.sh, feature_list.json, claude-progress.txt, initial git commit) and repeated coding sessions that each ship exactly one feature, verify it end-to-end via browser automation, and leave the repo in clean committed state. Trigger whenever a build will outlive a single context window (multi-hour/multi-day autonomous coding, session handoffs, resuming a scaffolded project), or when designing a harness/loop for such work.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.