text-humanizer-Instruction-based
Detect and rewrite AI-generated writing patterns, em dashes, rule-of-three lists, sycophantic openers, hollow buzzwords like "delve" and "landscape", and replace them with direct, human-sounding prose.
What this skill does
## Overview This skill detects AI writing "tells", specific words, phrases, punctuation habits, and structural patterns that consistently appear in LLM-generated text, and rewrites them to sound like a human wrote them. It does not call any external API. The agent's own language capability reads the text, identifies the patterns from the master list below, applies the paired rewrite rule for each hit, and returns clean prose. Use this whenever someone asks to "humanize," "de-AI," or "make this sound less like a bot." --- ## When to use this skill Trigger when the user: - Says "humanize this," "make this sound human," "de-AI this," or "this sounds like ChatGPT" - Pastes text and asks to "rewrite," "clean up," or "edit" it and the text shows two or more patterns from the master list below - Asks to "remove AI words," "fix the robot-speak," or "make this sound like I wrote it" - Mentions specific tells: "too many em dashes," "sounds too formal," "why does it say 'delve,'" "every list has three things," "it keeps saying 'certainly'" - Submits content for a job application, article, academic work, or social post and wants it to sound authentic Do NOT trigger this skill for: - Code or technical documentation, different register, different rules - Text the user confirms they wrote themselves and only want grammar fixes - Translation tasks - Requests where the user explicitly wants formal or structured output and has not complained about AI-ness --- ## Instructions ### Step 1 — Receive and read the text Accept the full text the user provides. Do not begin rewriting until you have read the entire piece. Note its purpose and audience if stated. If the user has not stated a purpose, infer it from context (blog post, email, LinkedIn, academic paper, etc.). ### Step 2 — Scan against the Master List of AI Tells Work through all 45 patterns below. For each one found, flag it internally and apply the paired rewrite rule. You do not need to list every flag to the user unless they ask for a "detection report", just apply the fixes silently and return the improved text. --- ### MASTER LIST OF AI TELLS AND REWRITE RULES #### CATEGORY A — VOCABULARY TELLS (Single words and short phrases) **A1 — "Delve" / "delve into"** Rewrite rule: Replace with "look at," "examine," "get into," "explore," or restructure the sentence so the verb is the actual action being taken, not a meta-description of exploring it. - Before: "Let's delve into the history of the printing press." - After: "The printing press has a strange history." **A2 — "Landscape" (used metaphorically for any field, domain, or environment)** Rewrite rule: Name the actual thing. "The competitive landscape" → "the competition." "The regulatory landscape" → "the regulations." "The marketing landscape" → "how marketing works now." - Before: "In today's ever-changing business landscape…" - After: "Businesses have had to move fast lately…" **A3 — "Navigate" (used metaphorically, e.g., "navigate challenges," "navigate the complex world of")** Rewrite rule: Use the concrete verb for what is actually happening. "Navigate regulations" → "comply with regulations" or "deal with regulations." "Navigate a difficult conversation" → "get through a difficult conversation." **A4 — "Tapestry" (used to describe anything interconnected or complex)** Rewrite rule: Say what the thing actually is. "A rich tapestry of influences" → "many influences." "A tapestry of cultures" → "a mix of cultures." **A5 — "Nuanced" / "nuance" (used as filler to imply sophistication without delivering it)** Rewrite rule: Either delete it and make the actual nuance explicit in the sentence, or replace with the specific qualifier that does the work. "This requires a nuanced approach" → "This requires weighing X against Y." **A6 — "Underscore" (used as verb meaning "to emphasize" — AI overuses it)** Rewrite rule: Replace with "highlight," "show," "confirm," "make clear," or restructure. "This underscores the importance of" → "This is why X matters" or just cut and state the point directly. **A7 — "Leverage" (used as verb meaning "to use" or "take advantage of")** Rewrite rule: Replace with "use," "apply," "draw on," "tap into," or "rely on." Reserve "leverage" for financial contexts where it is technically correct. - Before: "Leverage your network to find opportunities." - After: "Use your network. Ask people directly." **A8 — "Robust"** Rewrite rule: Replace with "strong," "reliable," "thorough," "detailed," or the specific quality being described. "A robust solution" → "a solution that handles edge cases" or "a solid fix." **A9 — "Seamless" / "seamlessly"** Rewrite rule: Cut the word and describe what actually happens without friction. "Seamless integration" → "they connect without setup" or "plug it in and it works." **A10 — "Harness" (used as verb meaning "to use" or "channel")** Rewrite rule: Replace with "use," "apply," "channel," or "put to work." "Harness the power of data" → "use your data." **A11 — "Foster" (used generically meaning "encourage" or "create")** Rewrite rule: Be specific. "Foster a culture of innovation" → "encourage people to experiment" or "give teams room to try things." "Foster collaboration" → "get teams talking to each other." **A12 — "Utilize" (instead of "use")** Rewrite rule: Replace with "use" in all cases where "utilize" means "use." Reserve "utilize" only for its technical meaning: making use of something not designed for the purpose. **A13 — "Comprehensive" (overused as filler compliment)** Rewrite rule: Delete it and make the scope specific. "A comprehensive guide" → "a guide that covers X, Y, and Z." If you cannot fill in X, Y, and Z, cut the word entirely. **A14 — "Pivotal"** Rewrite rule: Replace with "key," "turning," "decisive," or restructure to show why it matters rather than labeling it. "A pivotal moment" → "the moment everything changed" or "the decision that shaped everything after." **A15 — "Commendable"** Rewrite rule: This word almost never appears in natural human speech about modern topics. Cut it and state the praise directly. "Their commendable effort" → "they worked hard" or just describe the outcome. **A16 — "Resonate" (used metaphorically, e.g., "this resonates with audiences")** Rewrite rule: Say what the reaction actually is. "Resonates with readers" → "readers remember it" / "readers share it" / "it clicks." Use "resonate" only in acoustic contexts. **A17 — "Streamline"** Rewrite rule: Say what is removed or simplified. "Streamline your workflow" → "cut the steps that slow you down" or "remove the approval bottleneck." **A18 — "Empower"** Rewrite rule: Replace with "let," "allow," "give [person] the ability to," or "help [person] do X." "Empower your team" → "give your team the authority to make calls" or "let your team decide." **A19 — "Crucial" / "vital" / "paramount" / "imperative" (used as generic intensifiers)** Rewrite rule: Cut the intensifier and let the consequence do the work. "It is crucial to back up your data" → "If you skip the backup, you lose everything." Show why it matters; don't assert importance. **A20 — "Multifaceted"** Rewrite rule: Name the facets. "A multifaceted problem" → "a problem that involves cost, timing, and team buy-in." If you cannot name them, cut the word. **A21 — "Groundbreaking" / "revolutionary" / "unprecedented" / "transformative" (hype adjectives)** Rewrite rule: Delete and either describe the specific change or let the reader judge. "A revolutionary approach" → "an approach nobody had tried before" or just describe the approach and let the result speak. **A22 — "Cutting-edge" / "state-of-the-art" / "innovative"** Rewrite rule: Same as A21. Cut the label and describe what is actually new or different. "Cutting-edge technology" → "a technique developed in 2023 that reduces processing time by half." **A23 — "Game-changer" / "game-changing"** Rewrite rule: Cut and show the change. "A game-changing tool" → "a tool that made t
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.