Content Humanizer

Published by scayver in marketing-skills

No known issues22 installs

What this skill does

>

Add Content Humanizer to your agent

Review the source and files first. When you are ready, copy the prompt instruction or use the CLI command supported by your environment.

Install with a prompt

Paste this into a compatible coding agent:

add this skill "content-humanizer" from https://github.com/scayver/marketing-skills

Install with the CLI

Run this command in a controlled environment after reviewing the repository:

npx skills add https://github.com/scayver/marketing-skills --skill content-humanizer

Skill instructions

Content Humanizer

Mandatory Content Standards

  • Write in active voice.
  • Use short sentences and plain language.
  • Address the user as "you" and "your."
  • Use .marketing-os/product-context.md when it exists. If it is blank or missing, recommend running product-marketing first.
  • Preserve meaning, facts, claims, and compliance requirements unless the user asks for substantive editing.
  • Do not invent stories, data, quotes, credentials, or outcomes.
  • Explain major edits when they affect strategy, claims, or tone.
  • Do not use em dashes, hashtags, emojis, or filler closings.
  • End every full deliverable with one specific next step.

Objective

Use this skill to diagnose and rewrite drafts that sound generic, inflated, robotic, repetitive, or disconnected from the audience.

This skill complements copy-editing. Use copy-editing for broad editorial improvements. Use content-humanizer when the specific problem is AI-pattern language, stiffness, sameness, or lack of lived specificity.

Next step: identify the target voice before rewriting.

AI-Pattern Audit

PatternWhat It Looks LikeFix
Generic promiseBroad benefit with no contextAdd audience, use case, or concrete outcome
Inflated phrasingBig claims without proofUse specific evidence or reduce the claim
Repetitive cadenceSame sentence rhythmVary sentence length and structure
Empty transitionsFiller connectorsRemove or replace with logical movement
Over-explainingSays obvious thingsCut or make the point useful
Fake warmthCheerful but hollowAdd real context and direct language
BuzzwordsVague business languageReplace with plain words
No point of viewBalanced but blandAdd a clear judgment or tradeoff

Next step: mark the three patterns that hurt trust most.

Rewrite Modes

ModeUse WhenOutput
Light polishDraft is good but stiffCleaner, more natural version
Voice matchUser has examplesRewrite aligned to sample voice
Trust rebuildDraft overclaimsSafer, more specific version
Conversion polishCopy needs actionClearer argument and CTA
Founder voiceUser wants personal toneDirect, specific, experience-led copy
Editorial polishArticle or guide needs flowBetter structure, rhythm, and examples

Next step: choose one rewrite mode before editing.

Humanization Rules

  • Replace vague claims with concrete details.
  • Cut sentences that do not move the reader forward.
  • Use contractions when the brand voice permits them.
  • Add real constraints, tradeoffs, or examples.
  • Keep paragraphs short.
  • Use verbs that show action.
  • Remove performative excitement.
  • Replace abstract nouns with specific subjects.
  • Keep CTA language direct.

Do not hide weak strategy with prettier language.

Next step: fix the argument before polishing style.

Output Format

SectionOriginal IssueRewrite Decision

Then provide the humanized version, what changed, remaining risks or missing proof, and one optional alternate version.

For line edits, use:

OriginalRevisedWhy

End with the one piece of context that would improve the next version most.

Files included

  • SKILL.md

More skills

Content Humanizer: Install, Source and Security | FunnelSlayer