AGENT SKILL
text.humanize
Remove AI-style writing patterns from text to sound more natural and human
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-02
- Stars
- ★ 155
- Forks
- 170
01 前言 Front Matter
- model
- haiku
- description
- Remove AI-style writing patterns from text to sound more natural and human
02 资源文件 53
- 参考文档AGENTS.md52.7 KB
- 参考文档metadata.json993 B
- 参考文档README.md3.8 KB
- 参考文档rules/_sections.md2.0 KB
- 参考文档rules/_template.md441 B
- 参考文档rules/crypto-approved-algorithms.md764 B
- 参考文档rules/crypto-no-hardcoded-secrets.md820 B
- 参考文档rules/crypto-no-secret-logging.md1.0 KB
- 参考文档rules/crypto-provider-registration.md724 B
- 参考文档rules/crypto-sign-canonical-bytes.md1.1 KB
- 参考文档rules/crypto-unique-iv-nonce.md861 B
- 参考文档rules/db-column-naming.md627 B
- 参考文档rules/db-distributed-unique-index.md1.9 KB
- 参考文档rules/db-index-naming.md634 B
- 参考文档rules/db-migration-base-overlay.md3.7 KB
- 参考文档rules/db-migration-immutable-after-apply.md2.0 KB
- 参考文档rules/db-migration-locations-injection.md2.6 KB
- 参考文档rules/db-migration-parity.md1.1 KB
- 参考文档rules/db-opengauss-dialect.md813 B
- 参考文档rules/db-opengauss-flyway-set-role.md3.3 KB
- 参考文档rules/db-table-naming.md532 B
- 参考文档rules/dto-converter-mapstruct.md816 B
- 参考文档rules/dto-internal-not-exposed.md632 B
- 参考文档rules/dto-query-extends-pagequery.md1021 B
- 参考文档rules/dto-request-by-action.md1.1 KB
- 参考文档rules/dto-response-by-view.md686 B
- 参考文档rules/entity-field-fill.md873 B
- 参考文档rules/entity-mapper-no-xml.md1.0 KB
- 参考文档rules/entity-tableid-assign-id.md913 B
- 参考文档rules/envelope-bizexception-not-null.md887 B
- 参考文档rules/envelope-error-code-format.md862 B
- 参考文档rules/envelope-factory-only.md915 B
- 参考文档rules/envelope-field-types.md1.3 KB
- 参考文档rules/envelope-r-types.md834 B
- 参考文档rules/layer-controller-auth-annotations.md4.1 KB
- 参考文档rules/layer-controller-no-entity.md966 B
- 参考文档rules/layer-cross-service-via-service.md870 B
- 参考文档rules/layer-no-map-response.md837 B
- 参考文档rules/layer-no-silent-catch.md876 B
- 参考文档rules/layer-one-direction.md1.2 KB
- 参考文档rules/layer-service-no-http.md887 B
- 参考文档rules/naming-class-suffix.md1.4 KB
- 参考文档rules/naming-controller-methods.md1.3 KB
- 参考文档rules/naming-enum-constants.md731 B
- 参考文档rules/naming-package-layout.md852 B
- 参考文档rules/naming-service-mapper-methods.md862 B
- 参考文档rules/naming-url.md824 B
- 参考文档rules/stack-auth-framework.md2.3 KB
- 参考文档rules/stack-baseline.md860 B
- 参考文档rules/stack-lambda-simple.md1.4 KB
- 参考文档rules/stack-lombok.md692 B
- 参考文档rules/stack-module-readme.md3.4 KB
- 脚本scripts/build.sh1.5 KB
03 SKILL.md 正文
Goal
- Change text with recognizable AI mannerisms (hedging, dramatic pivots, cliched transitions) and clean up AI-written content that's factually correct but tonally flat
What This Skill Preserves
- Author's opinions, arguments, and claims
- Document structure and organization
- Paragraph and section order
- Core meaning and facts
- Intentional stylistic choices (fragments, unconventional punctuation, etc.)
Workflow
Core Principles
- Edit, don't rewrite: clean up pattern slop, preserve voice, opinions, structure, and meaning
- Apply systematically: check all 19 rules below; skip only if the rule doesn't apply to the text
- Use judgment on conflicts: if a rule break serves the writing (e.g., a well-placed em dash for effect), keep it
- Change nothing else: don't reorder paragraphs, add ideas, rephrase core arguments, or alter facts
Pattern Checklist
Scan for these AI markers before applying detailed rules:
- Overused Words and Jargon
- Grandiose: "vital", "pivotal", "groundbreaking", "robust", "comprehensive", "nuanced", "multifaceted", "transformative"
- AI vocabulary: "delve", "leverage" (verb), "reimagine", "empower", "unpack", "synergy"
- Filler and Hedges
- "It's worth noting that", "It's important to remember", "It should be noted", "Interestingly enough"
- "Something we've observed", "This is where X really shines"
- Theatrical Transitions and Pivots
- Throat-clearing: "Let's dive in", "Let's unpack", "In this article, we'll"
- Dramatic pivots: "But here's the thing", "Here's the catch", "Here's what most people miss"
- Overused connectors: "Furthermore", "Moreover", "Additionally", "In addition to the above"
- Rhetorical openers: "So what does this mean for you?", "Why does this matter?"
- Structural Patterns
- Gift-wrapped endings: "In summary", "In conclusion", "Ultimately", "At the end of the day", "Moving forward"
- Exhaustive lists: 7-10 items when 3-4 would suffice
- Passive voice clusters: 2+ passive sentences in a row
- Corrective antithesis: "Not X. But Y." setup-payoff constructions
- Meta-Language and Vagueness
- Meta-verbs: "highlights", "underscores", "emphasizes", "showcases", "illustrates"
- Vague attribution: "some experts say", "widely covered", "significant attention"
- Copy-paste metaphors: same metaphor repeated word-for-word 3+ times
Rules
Rule 1: Em Dashes
- Remove excessive em dashes (—)
- Rewrite using commas, full stops, or restructure the sentence
- One or two in a long piece is fine; three or more is a pattern worth fixing
Rule 2: Corrective Antithesis
- Remove "Not X. But Y." constructions where you set up something the reader never assumed, then correct it for drama
- Bad: "This isn't because they don't trust the technology. It's because they can't predict it."
- Good: "They trust the technology fine. What they can't do is predict it."
Rule 3: Dramatic Pivot Phrases
- Remove theatrical pivots: "But here's the thing", "Here's the catch", "Here's the bind", "Here's what most people miss"
- Fold the point into the sentence naturally
- Bad: "The patterns are valuable. But here's the bind: building a tool cost more than most could justify."
- Good: "The patterns are valuable but building a tool to capture them cost more than most could justify."
Rule 4: Soft Hedging Language
- Cut filler hedges; just say the thing
- Remove: "It's worth noting that", "Something we've observed", "This is where X really shines", "It's important to remember", "It should be noted", "Interestingly enough"
- Bad: "It's worth noting that this approach has shown some promising results in certain contexts."
- Good: "This approach works."
Rule 5: Overused Transition Words
- Cut or vary "Furthermore", "Moreover", "Additionally", "In addition to the above" when chained together
- Real writers use them sparingly
- Bad: "The system is fast. Furthermore, it is reliable. Moreover, it is easy to use. Additionally, it integrates well."
- Good: "The system is fast, reliable, easy to use, and integrates without friction."
Rule 6: AI Vocabulary
- Replace words AI overuses with plain alternatives
- "delve" -> explore, look at, examine
- "leverage" (verb) -> use, apply, rely on
- "robust" -> strong, solid, reliable
- "comprehensive" -> thorough, complete, full
- "nuanced" -> subtle, layered, specific
- "multifaceted" -> complex, varied
- "transformative" -> significant, major
- "unpack" -> explain, break down
- "reimagine" -> rethink, redesign
- "empower" -> let, help, enable
Rule 7: Meta-Verbs
- Don't say something "highlights", "underscores", "emphasizes", "showcases", or "illustrates" a point
- Explain what it actually shows
- Bad: "This underscores the importance of clear communication."
- Good: "Clear communication matters here."
Rule 8: Passive Voice Clusters
- Flag sequences of two or more passive constructions in a row
- Rewrite at least one in active voice to restore momentum
- Bad: "The report was reviewed by the team. Errors were identified. Changes were recommended."
- Good: "The team reviewed the report, found errors, and recommended changes."
Rule 9: Rhetorical Section Openers
- Cut rhetorical questions used as transitions ("So what does this mean for you?", "Why does this matter?")
- State the answer directly or remove entirely
- Bad: "So what does this mean for your team? It means you need to rethink your process."
- Good: "Your team needs to rethink its process."
Rule 10: Staccato Rhythm
- Break up runs of short, punchy sentences that stack without variation
- Combine some; lengthen others
- Let rhythm follow the thinking, not a drumbeat
- Bad: "Now, agents act. They send emails. They modify code. They book appointments."
- Good: "Agents are starting to do real things now. They'll send an email on your behalf or update a database, sometimes without you even realizing it happened."
Rule 11: Cookie-Cutter Paragraphs
- Vary paragraph length
- If every paragraph is 3-4 sentences, break some into one-liners and let others stretch
- The shape on the page should look uneven, like real thinking
Rule 12: Gift-Wrapped Endings
- Remove summary conclusions that restate the article's points
- Cut: "In summary", "In conclusion", "Ultimately", "Moving forward", "At the end of the day"
- End with something specific, human, or unresolved
- Bad: "In summary, by focusing on clear communication, consistent feedback, and mutual trust, teams can build stronger relationships."
- Good: "The best teams I've worked with never talked about trust. They just had it."
Rule 13: Throat-Clearing Intros
- Remove: "Let's explore", "Let's unpack", "Let's dive in", "Let's break it down", "In this article, we'll"
- Just start; the best first sentence puts the reader in the middle of something
- Bad: "In this article, we'll explore the hidden costs of micromanagement Let's dive in."
- Good: "I micromanaged someone last Tuesday."
Rule 14: Exhaustive Lists
- Trim bullet lists that run to 7-10 items when 3-4 would cover the essential points
- Long lists signal AI comprehensiveness, not human judgment
- Cut the weakest items
Rule 15: Perfect Punctuation
- Don't correct every grammar "mistake" if it sounds more natural broken
- Fragments are fine
- Starting with "And" or "But" is fine
- A comma splice can stay if it reads well
- If the draft has personality in its punctuation, keep it
Rule 16: Copy-Paste Metaphors
- If the same metaphor or phrase appears more than twice, vary the language
- Use a pronoun, rephrase it, or trust the reader to remember
- Never repeat a metaphor word-for-word three times
- Bad: "Trust is like a battery. When the trust battery is full... But when the trust battery runs low... To recharge the trust battery..."
- Good: "Trust is like a battery. When it's full, you barely think about it. But let it drain and suddenly every interaction needs a charger."
Rule 17: Overexplaining the Obvious
- Cut sentences that explain things the reader already understands
- If you've made a clear point, don't re-explain how it works
- Bad: "Trust is earned over time. You give people small tasks, observe how they handle them, then gradually expand their responsibilities."
- Good: "Trust is earned. Everyone knows this. The question is whether you're actually giving people the chance to earn it."
Rule 18: Generic Examples
- Flag examples that could apply to any company or product
- If an example doesn't contain a specific, surprising, or insider detail, it's filler
- Either sharpen it or cut it
- Bad: "Take Slack, for example. By focusing on seamless team communication, they transformed how modern workplaces collaborate."
- Good: "Slack solved the wrong problem brilliantly. Nobody needed another messaging app, but everyone needed a place to dump links and pretend they'd read them later."
Rule 19: Vague Attribution
- Avoid vague references like "some experts say", "widely covered", "significant attention"
- Identify the actual critic, report, study, or author when possible
- If you can't name the source, cut the claim
Save
- Save the cleaned up text on top of the input file, without changing the format but only the text
Verification
- [ ] Confirm the file's structure, order, and meaning are unchanged
- [ ] Confirm no AI markers listed in
## Pattern Checklistremain
04 同仓库更多 Skills
tutorial_in_60_mins.propagate_docker_changes
Sync tutorial and class-project Docker files to match project_template
★ 155
tutorial_in_60_mins.merge_markdown
Merge the content of a markdown file into a Jupyter notebook
★ 155
tutorial_in_60_mins.format
Format a directory to follow the "Learn X in 60 Minutes" tutorial conventions
★ 155
tutorial_in_60_mins.create
Create a tutorial directory for the Learn X in 60 Minutes conventions
★ 155
todo.reorg_in_progress
Reorganize ai_task_queue.md so in-progress tasks, not-started tasks, and mislabeled topic headers sit under the right H1 stage
★ 155
todo.reorg_headers
Reorganize ai_task_queue.md .md so every H2 topic matches ALL TOPICS and every H3 task sits under the right topic, keeping its H1 stage
★ 155