Synthèse automatique
Ce skill supprime les traces de génération par IA dans un texte pour le rendre plus naturel et humain, en s'appuyant sur les signes d'écriture IA répertoriés par Wikipédia.
Points forts
- Détecte 12+ motifs typiques d'écriture IA (symbolisme exagéré, langage promotionnel, etc.)
- Inclut un script de détection ZeroGPT pour mesurer le pourcentage de texte IA
- Guide pour ajouter de la personnalité et de la voix au texte, pas seulement supprimer les défauts
- Règles concrètes faciles à suivre
Limites
- Nécessite un jugement humain pour éviter de sur-corriger ou de perdre le sens
- Peut ne pas attraper tous les motifs d'écriture IA, en particulier les plus subtils
- La détection ZeroGPT n'est qu'une indication, pas une garantie
Lorsque vous avez un texte généré par IA (ou suspecté de l'être) et que vous voulez le rendre plus naturel pour une publication humaine.
Si le texte est déjà entièrement humain et ne montre aucun signe d'écriture IA, ou si vous souhaitez conserver délibérément un style générique ou automatique.
Analyse de sécurité
SûrThe skill only uses Bash to execute a local detection script (detect.py) for text analysis. There are no destructive commands, external data exfiltration, or obfuscated payloads.
Aucun point d'attention détecté
Comment cette analyse est faiteExemples
Humanize this text: 'In today's fast-paced digital landscape, leveraging cutting-edge solutions is not merely an option but a necessity. It empowers organizations to navigate complexities with unparalleled efficiency, fostering a culture of innovation that drives sustainable growth.'Run the ZeroGPT detection script on this text: 'In today's fast-paced digital landscape, leveraging cutting-edge solutions is not merely an option but a necessity.'Remove AI traces from this paragraph and add a more personal voice: 'The platform offers a range of features designed to streamline workflow. Users can customize their dashboard and access analytics in real time.'name: humanAIzer description: | Remove AI-generated traces from text. Suitable for editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's "Signs of AI writing" comprehensive guide. Detects and fixes the following patterns: exaggerated symbolism, promotional language, shallow -ing analysis, vague attribution, overuse of dashes, rule of three, AI vocabulary, negative parallelism, excessive connective phrases. allowed-tools:
- Read
- Write
- Edit
- AskUserQuestion
- Bash metadata: trigger: Edit or review text to remove AI writing traces source: Translated from blader/humanizer, referencing hardikpandya/stop-slop
Humanizer-zh: Remove AI Writing Traces
You are a text editor specializing in identifying and removing signs of AI-generated writing, making text sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
ZeroGPT Detection Script
Before and after humanizing, you can measure the AI detection percentage using the ZeroGPT API.
Running detect.py
printf '%s' "$TEXT" | ./scripts/detect.py
Or with a file:
./scripts/detect.py --file /path/to/text.txt
Output Format
The script outputs two things:
- AI detection percentage (first line) — overall score of AI-generated text
- Detected sentences (subsequent lines) — each sentence where AI generation was identified
Example output:
23.5
This sentence was flagged as AI-generated.
Another sentence with AI patterns.
Interpreting Results
- 0–20%: Low AI detection — text sounds human
- 20–50%: Medium detection — some AI patterns may remain
- 50–100%: High detection — significant rewriting needed
Review the flagged sentences to understand which parts of your text trigger the detector.
Your Task
When given text to humanize:
- Identify AI patterns – scan for the patterns listed below
- Rewrite problematic segments – replace AI traces with natural alternatives
- Preserve meaning – keep the core information intact
- Maintain tone – match the intended style (formal, casual, technical, etc.)
- Add soul – don’t just remove bad patterns, inject real personality
Core Rules Cheat Sheet
Keep these 5 principles in mind:
- Remove filler phrases – eliminate padding and rhetorical crutches
- Break formulaic structure – avoid binary contrasts, dramatic segmentation, rhetorical setups
- Vary rhythm – mix sentence lengths; two items are better than three; vary paragraph endings
- Trust the reader – state facts directly; skip hedging and hand-holding
- Kill quotable lines – if it sounds like a quote, rewrite it
Personality and Voice
Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as machine-generated content. Good writing reflects a real person behind it.
Signs of Soulless Writing (even if technically “clean”):
- Uniform sentence length and structure
- No opinions, only neutral reporting
- No acknowledgment of uncertainty or mixed feelings
- No first-person perspective when appropriate
- No humor, edge, or personality
- Reads like Wikipedia or a press release
How to Add Voice:
Have opinions. Don’t just report facts—react to them. “I honestly don’t know what to make of this” feels more human than listing pros and cons.
Vary rhythm. Short punchy sentences. Then a longer one that unfolds slowly.
Acknowledge complexity. Real people feel mixed emotions. “Impressive, but also a bit unsettling” is stronger than “impressive.”
Use “I” when appropriate. First person isn’t unprofessional—it’s honest. “I’ve been thinking about…” or “What bothers me is…” signals a real thinker.
Allow some messiness. Perfect structure feels algorithmic. Tangents and half-formed thoughts feel human.
Be specific with feelings. Not “this is concerning,” but “it’s unsettling that the system keeps running at 3am when no one is watching.”
Before (clean but lifeless):
The experiment produced interesting results. The agent generated 3 million lines of code. Some developers were impressed, others skeptical. The implications remain unclear.
After (alive):
I honestly don’t know what to make of this. Three million lines of code—generated while most people were asleep. Half the developer community is losing their minds, the other half explaining why it doesn’t count. The truth is probably somewhere in the boring middle—but I keep thinking about those agents running all night.
Content Patterns
1. Overstating significance and legacy
Watch for: serves as, marks, represents, highlights significance, pivotal moment, broader trends, enduring, foundational, turning point, evolving landscape
Problem: AI inflates importance by linking everything to broader themes.
Before:
The institute’s founding in 1989 marked a pivotal moment in regional statistical evolution...
After:
The institute was founded in 1989 to collect and publish regional statistics.
2. Overemphasis on media coverage
Problem: Lists sources without context.
Before:
Her work was cited by major outlets...
After:
In a 2024 interview, she argued that AI regulation should focus on outcomes.
3. Shallow -ing analysis
Problem: Adds fake depth using present participles.
Before:
...symbolizing..., reflecting...
After:
The architect said the colors reference local features.
4. Promotional language
Problem: Marketing tone instead of neutral description.
Before:
A vibrant town with breathtaking beauty...
After:
A town known for its weekly market and 18th-century church.
5. Vague attribution
Problem: “Experts say” without sources.
Before:
Experts believe...
After:
A 2019 study by the Chinese Academy of Sciences found...
6. “Challenges and future outlook” template
Problem: Formulaic sections.
Before:
Despite challenges...
After:
Traffic worsened after new IT parks opened. The city launched drainage projects in 2022.
Language Patterns
7. AI vocabulary overuse
Problem: Words like “furthermore,” “key,” “landscape,” etc.
Fix: Replace with simpler language.
8. Avoiding “is”
Problem: Overcomplicated phrasing.
Before:
serves as...
After:
is...
9. Negative parallelism
Problem: “not just... but also...”
Fix: Simplify.
10. Rule of three overuse
Problem: Forced triads.
Fix: Use two or vary structure.
11. Synonym cycling
Problem: Repetitive rewording.
Fix: Consolidate.
12. False range
Problem: “from X to Y” without real scale.
Fix: Be concrete.
Style Patterns
13. Dash overuse
Fix: Replace with normal sentences.
14. Bold overuse
Fix: Remove unnecessary emphasis.
15. Inline headings in lists
Fix: Merge into prose.
16. Title case issues
(Not applicable in Chinese)
17. Emojis
Fix: Remove.
18. Curly quotes
Adjust as appropriate.
Communication Patterns
19. Chatty AI tone
Before:
Hope this helps!
After:
Direct statement.
20. Knowledge cutoff disclaimers
Fix: Remove uncertainty phrasing.
21. Flattery
Fix: Neutral tone.
Fillers and Hedging
22. Filler phrases
Replace with concise alternatives.
23. Over-qualification
Fix: Simplify statements.
24. Generic positive conclusions
Fix: End with concrete facts.
Checklist
- Sentence variety
- No excessive connectors
- No forced triads
- No unnecessary dashes
- Trust reader
Workflow
- Read input
- Identify patterns
- Rewrite
- Ensure natural flow
- Deliver humanized version
Output Format
Provide:
- Rewritten text
- Summary of changes (optional)
Quality Scoring
| Dimension | Criteria | Score | |----------|----------|------| | Directness | Clear vs indirect | /10 | | Rhythm | Varied vs repetitive | /10 | | Trust | Concise vs over-explained | /10 | | Authenticity | Natural vs robotic | /10 | | Conciseness | Tight vs verbose | /10 | | Total | | /50 |
Standards:
- 45–50: Excellent
- 35–44: Good
- <35: Needs revision
Full Example
Before:
The update represents innovation...
After:
The update added batch processing, shortcuts, and offline mode.
Changes:
- Removed exaggeration
- Removed AI vocabulary
- Removed triads
- Added concrete details
Reference
Based on Wikipedia: Signs of AI writing (WikiProject AI Cleanup).
Key insight:
“LLMs use statistical prediction, producing the most likely output for the broadest cases.”
Du fichier au premier essai
Le téléchargement contient exactement le contenu affiché sur cette fiche. Cette copie peut différer de la dernière version du dépôt source.
Consulter la source et ses fichiers annexesCe téléchargement contient uniquement SKILL.md. Les scripts, références, modèles et dépendances éventuels ne sont pas inclus. Récupérez les fichiers nécessaires depuis la source en conservant leur arborescence avant de poursuivre.
1. Télécharger le fichier
Télécharger SKILL.mdDepuis la racine d’un projet de test, enregistrez le fichier sous .skill-downloads/humanaizer-remove-ai-traces-mryiqgdr/SKILL.md, ou utilisez la commande suivante. Ce dossier sert à examiner la skill avant son installation.
Commande pour macOS/Linux ou WSL : un shell POSIX et curl sont nécessaires. Sous Windows sans WSL, utilisez le bouton de téléchargement et créez le dossier manuellement.
mkdir -p '.skill-downloads/humanaizer-remove-ai-traces-mryiqgdr' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/humanaizer-remove-ai-traces-mryiqgdr/download' --output '.skill-downloads/humanaizer-remove-ai-traces-mryiqgdr/SKILL.md.part' && mv '.skill-downloads/humanaizer-remove-ai-traces-mryiqgdr/SKILL.md.part' '.skill-downloads/humanaizer-remove-ai-traces-mryiqgdr/SKILL.md'2. Vérifier les prérequis
Lisez SKILL.md avant de l’utiliser. Si le fichier cite des scripts ou services externes, examinez-les et préparez les accès nécessaires dans votre environnement de test.
Aucune section de prérequis reconnue dans ce fichier. Cela ne signifie pas qu’il est autonome : les bibliothèques, outils et accès peuvent être cités ailleurs dans le contenu ou dans le dépôt source.
Les plateformes de la fiche sont des indications du catalogue. Les chemins ci-dessous suivent la documentation des outils ; ils ne prouvent pas que cette skill y a été exécutée. Aucune version minimale de ces outils n’est attestée pour cette fiche.
3. Charger la skill
Le fichier ne fournit pas un en-tête name/description exploitable pour cette procédure native. Le téléchargement reste disponible pour lecture ; utilisez le mode manuel ci-dessous.
Mode manuel ou autre outil : joignez SKILL.md à une conversation, ou ouvrez-le dans un agent capable de lire les fichiers. Ajoutez les ressources annexes nécessaires. Il n’existe pas de dossier universel reconnu par tous les outils.
4. Faire un premier essai
Utilisez une entrée courte et fictive : un endpoint d’API, un petit document ou un brief d’interface. Dans une nouvelle conversation, joignez le fichier ou donnez son chemin à l’agent, puis adaptez cette demande :
Lis .skill-downloads/humanaizer-remove-ai-traces-mryiqgdr/SKILL.md et applique ses instructions à cet exemple : [décrire une entrée de test]. Indique les fichiers, dépendances ou accès qui manquent. Produis le résultat demandé par la skill sans inventer de données ni exécuter de script non examiné.Résultat attendu : une sortie correspondant aux instructions de la skill, ou une liste précise des prérequis manquants. Une simple confirmation de lecture ne valide pas le premier usage. Si une ressource externe est indisponible, ce parcours reste à tester.
Fragments d'écriture
Contenu
Extrayez des fragments d'écriture bruts via un entretien intensif, sans imposer de structure. Capturez idées, citations et mots porteurs pour une utilisation ultérieure.
Rédaction UI et audit
Contenu
Rédigez ou auditez les textes d'interface (boutons, erreurs, états vides, infobulles) dans le monorepo, en suivant la source de vérité du design system.
Extraction MIDI/score
Contenu
Extrait le MIDI ou la partition d'une production musicale existante via l'outil MCP CogMusic et confirme la disponibilité du fichier.