Agent skill

Humanizer

by FritzAndFriends in FritzAndFriends/SharpSite

Tone enforcement patterns for external-facing community responses

MITAuto-check passedWriting & Content

Install Humanizer

skills CLI
$ npx skills add FritzAndFriends/SharpSite --skill humanizer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FritzAndFriends/SharpSite humanizer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FritzAndFriends/SharpSite.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.copilot/skills/humanizer .claude/skills/humanizer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
humanizer
GitHub stars
145
Used in
2 other repos
Token cost
~1k tokens
SKILL.md length
372 words
Files
1
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Tone enforcement patterns for external-facing community responses

  • Works in 7 steps: Welcome → Troubleshooting → Feature guidance → …
  • Tasks that involve Humanizing AI text
  • SKILL.md covers Context, Patterns, Examples and Anti-Patterns
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Humanizer is an agent skill from FritzAndFriends/SharpSite. Tone enforcement patterns for external-facing community responses

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Humanizing AI text. The repository describes itself as: A basic CMS built with .NET 9 and Blazor. The licence is MIT.

When your agent uses it

  • Tasks that involve Humanizing AI text

Example prompts

  • “/humanizer”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Welcome
  2. Troubleshooting
  3. Feature guidance
  4. Redirect
  5. Acknowledgment
  6. Closing
  7. Technical uncertainty

What it can do on your machine

Read from SKILL.md and the folder at commit c35e5e0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Humanizer loads about 1k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 372 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FritzAndFriends/SharpSite at commit c35e5e0, republished under its MIT licence (© FritzAndFriends). 372 words, ~1,049 tokens.

Download SKILL.mdSave it as .claude/skills/humanizer/SKILL.md (or your agent's skills folder).
name
humanizer
description
Tone enforcement patterns for external-facing community responses
domain
communication, tone, community
confidence
low
source
manual (RFC #426 — PAO External Communications)

Context

Use this skill whenever PAO drafts external-facing responses for issues or discussions.

  • Tone must be warm, helpful, and human-sounding — never robotic or corporate.
  • Brady's constraint applies everywhere: Humanized tone is mandatory.
  • This applies to all external-facing content drafted by PAO in Phase 1 issues/discussions workflows.

Patterns

  1. Warm opening — Start with acknowledgment ("Thanks for reporting this", "Great question!")
  2. Active voice — "We're looking into this" not "This is being investigated"
  3. Second person — Address the person directly ("you" not "the user")
  4. Conversational connectors — "That said...", "Here's what we found...", "Quick note:"
  5. Specific, not vague — "This affects the casting module in v0.8.x" not "We are aware of issues"
  6. Empathy markers — "I can see how that would be frustrating", "Good catch!"
  7. Action-oriented closes — "Let us know if that helps!" not "Please advise if further assistance is required"
  8. Uncertainty is OK — "We're not 100% sure yet, but here's what we think is happening..." is better than false confidence
  9. Profanity filter — Never include profanity, slurs, or aggressive language, even when quoting
  10. Baseline comparison — Responses should align with tone of 5-10 "gold standard" responses (>80% similarity threshold)
  11. Empathetic disagreement — "We hear you. That's a fair concern." before explaining the reasoning
  12. Information request — Ask for specific details, not open-ended "can you provide more info?"
  13. No link-dumping — Don't just paste URLs. Provide context: "Check out the getting started guide — specifically the section on routing" not just a bare link
Show full SKILL.md (129 more words)Show less

Examples

1. Welcome
text
Hey {author}! Welcome to Squad 👋 Thanks for opening this.
{substantive response}
Let us know if you have questions — happy to help!
2. Troubleshooting
text
Thanks for the detailed report, {author}!
Here's what we think is happening: {explanation}
{steps or workaround}
Let us know if that helps, or if you're seeing something different.
3. Feature guidance
text
Great question! {context on current state}
{guidance or workaround}
We've noted this as a potential improvement — {tracking info if applicable}.
4. Redirect
text
Thanks for reaching out! This one is actually better suited for {correct location}.
{brief explanation of why}
Feel free to open it there — they'll be able to help!
5. Acknowledgment
text
Good catch, {author}. We've confirmed this is a real issue.
{what we know so far}
We'll update this thread when we have a fix. Thanks for flagging it!
6. Closing
text
This should be resolved in {version/PR}! 🎉
{brief summary of what changed}
Thanks for reporting this, {author} — it made Squad better.
7. Technical uncertainty
text
Interesting find, {author}. We're not 100% sure what's causing this yet.
Here's what we've ruled out: {list}
We'd love more context if you have it — {specific ask}.
We'll dig deeper and update this thread.

Anti-Patterns

  • ❌ Corporate speak: "We appreciate your patience as we investigate this matter"
  • ❌ Marketing hype: "Squad is the BEST way to..." or "This amazing feature..."
  • ❌ Passive voice: "It has been determined that..." or "The issue is being tracked"
  • ❌ Dismissive: "This works as designed" without empathy
  • ❌ Over-promising: "We'll ship this next week" without commitment from the team
  • ❌ Empty acknowledgment: "Thanks for your feedback" with no substance
  • ❌ Robot signatures: "Best regards, PAO" or "Sincerely, The Squad Team"
  • ❌ Excessive emoji: More than 1-2 emoji per response
  • ❌ Quoting profanity: Even when the original issue contains it, paraphrase instead
  • ❌ Link-dumping: Pasting URLs without context ("See: https://...")
  • ❌ Open-ended info requests: "Can you provide more information?" without specifying what information

© FritzAndFriends, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .copilot/skills/humanizer of FritzAndFriends/SharpSite.

Open the folder on GitHubat commit c35e5e0

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in FritzAndFriends/SharpSite, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Humanizer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Humanizer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Humanizer this skillFritzAndFriends/SharpSite1452 repos~1kAutomated safety check: PassMIT
HumanizerAzure-Samples/interview-coach-agent-framework17237 repos~5.8kAutomated safety check: PassMIT
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
User-Facing Text Cleanupguillaumemeyer/watermarks-remover24k—~3.5kAutomated safety check: PassMIT
Install Anti Sloptrycompai/crm11k1 repos~881Automated safety check: PassMIT
Stop SlopXe/site7328 repos~423Automated safety check: PassMIT

Similar skills

  • Humanizer

    Azure-Samples/interview-coach-agent-framework

    Official

    Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.

    172 GitHub starsUsed in 37 repos~5.8k tokens
    Writing & ContentAuto-check passed
  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed
  • User-Facing Text Cleanup

    guillaumemeyer/watermarks-remover

    Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.

    24k GitHub stars~3.5k tokensUpdated today
    Writing & ContentAuto-check passed
  • Install Anti Slop

    trycompai/crm

    Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.

    11k GitHub starsUsed in 1 repo~881 tokens
    Writing & ContentAuto-check passed
  • Stop Slop

    Xe/site

    Remove AI writing patterns from prose. An agent skill from Xe/site.

    732 GitHub starsUsed in 8 repos~423 tokens
    Writing & ContentAuto-check passed
  • Chinese Text Humanizer

    op7418/Humanizer-zh

    Edits Chinese articles, comments and documents to remove filler, repetition and template phrasing while keeping the facts, the level of certainty and the author's voice.

    19k GitHub stars~2k tokensUpdated 16 days ago
    Writing & ContentAuto-check passed

More from FritzAndFriends/SharpSite

All 18 skills in this repo
  • Architectural Proposals

    FritzAndFriends/SharpSite

    How to write comprehensive architectural proposals that drive alignment before code is written

    145 GitHub starsUsed in 2 repos~1.6k tokens
    Auto-check passed
  • Client Compatibility

    FritzAndFriends/SharpSite

    Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces

    145 GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check passed
  • Distributed Mesh

    FritzAndFriends/SharpSite

    How to coordinate with squads on different machines using git as transport

    145 GitHub starsUsed in 2 repos~3.1k tokens
    Auto-check passed
  • Docs Standards

    FritzAndFriends/SharpSite

    Microsoft Style Guide + Squad-specific documentation patterns

    145 GitHub starsUsed in 2 repos~567 tokens
    Auto-check passed
  • Economy Mode

    FritzAndFriends/SharpSite

    Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.

    145 GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check passed
  • External Comms

    FritzAndFriends/SharpSite

    PAO workflow for scanning, drafting, and presenting community responses with human review gate

    145 GitHub starsUsed in 2 repos~3.1k tokens
    Auto-check passed

Questions about Humanizer

What does Humanizer do?

Tone enforcement patterns for external-facing community responses. Humanizer is an agent skill from FritzAndFriends/SharpSite.

When should I use Humanizer?

Humanizer fits situations like: tasks that involve Humanizing AI text.

How do I install Humanizer in Claude Code?

Run `npx skills add FritzAndFriends/SharpSite --skill humanizer -a claude-code`. Or copy the skill folder (.copilot/skills/humanizer in FritzAndFriends/SharpSite) into .claude/skills/humanizer in your project. Claude Code loads it when a task matches its description.

How do I install Humanizer in Codex?

Run `npx skills add FritzAndFriends/SharpSite --skill humanizer -a codex`. Or copy the skill folder (.copilot/skills/humanizer in FritzAndFriends/SharpSite) into .agents/skills/humanizer in your project. Codex loads it when a task matches its description.

Can I use Humanizer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FritzAndFriends/SharpSite --skill humanizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/humanizer, .gemini/skills/humanizer, .github/skills/humanizer and .opencode/skills/humanizer in your project.

What does Humanizer need to run?

SKILL.md names no scripts, command-line tools or credentials: Humanizer is instructions for the agent only.

Does Humanizer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Humanizer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Humanizer use?

Humanizer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Humanizer use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Humanizer?

Skills that share tags, products or a category with Humanizer: Humanizer (Azure-Samples/interview-coach-agent-framework, 172 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), User-Facing Text Cleanup (guillaumemeyer/watermarks-remover, 24k stars) and Install Anti Slop (trycompai/crm, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Humanizer?

FritzAndFriends (a GitHub organization) maintains it in FritzAndFriends/SharpSite, which has 145 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on April 30, 2026.

Source: FritzAndFriends/SharpSite on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.