agentleFS
tuanductrantuanductran/hr-skills/.agents/skills/humanizer/SKILL.md

humanizer

Skill58 starsChanged 2 months agoMITView on GitHub

Edit and rewrite SKILL.md prose to reduce signs of AI-generation and improve clarity, tone, and inclusivity. Useful for polishing skill descriptions and prompts.

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use economy-mode, personal-voice and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    economy-mode

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

    Also in 5 projects that use this

  • petermuirurithuoSkill

    personal-voice

    Captures the user's personality, communication style, and values. Use this skill whenever responding to the user, drafting anything on their behalf (emails, CVs, messages, opinions, explanations), or whenever tone, word choice, or how an opinion is delivered matters. Apply it by default for any prompt, not only when the user explicitly asks for "my style" or "my voice.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    architectural-proposals

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

    Also in 3 projects that use this

  • +9 more from Azure

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ensure blank lines before lists and headings per repo rules

    line 16
  2. Very specific:

    Always run bun run lint:md after rewrites to enforce markdown rules

    line 47
  3. Very specific:

    Keep example prompts short and use [placeholders] consistently

    line 48
  4. Very specific:

    Use this skill as a final pass before opening PRs to dev

    line 50

“Common” is measured: kept by at least 6 in 10 of the 174 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Humanizer

Supported tasks

  • Rewrite SKILL.md sections to sound natural and human-authored
  • Fix grammar, inclusive language, and remove AI artifacts
  • Shorten long descriptions to fit trigger thresholds
  • Ensure blank lines before lists and headings per repo rules
  • Normalize phrasing for trigger phrases and placeholders
  • Provide multiple tone variants (formal, friendly, concise)
  • Generate reviewer-friendly diffs highlighting changes
  • Produce suggestions for improving prompt clarity

Key prompts

Rewrite tasks

  • "Rewrite this SKILL.md description to sound natural and clear: [text]."
  • "Shorten and sharpen the description while keeping every trigger phrase and staying above the 50-character minimum — real descriptions in this repo run 250-700+ characters, so don't over-trim."
  • "Convert this list of prompts into a consistent style and tone."
  • "Generate three tone variants for the Tips section: formal, friendly, concise."

Quality enforcement

  • "Check this file for missing blank lines between headings and lists per repo rules."
  • "Flag inclusive language issues and suggest neutral replacements."
  • "Provide a one-paragraph summary of changes suitable for a PR body."
  • "Highlight any placeholders that don't follow [placeholders] convention."

Tone and examples

  • "Provide short example rewrites for this Tips section in a friendly tone: [text]."
  • "Convert these technical examples into beginner-friendly language while preserving accuracy."
  • "Generate three alternative opening lines for the SKILL description with different formality levels."
  • "Suggest 4 sample prompt phrasings that follow the repo's [placeholders] pattern."

Tips

  • Always run bun run lint:md after rewrites to enforce markdown rules
  • Keep example prompts short and use [placeholders] consistently
  • Preserve technical accuracy when simplifying prose for non-technical readers
  • Use this skill as a final pass before opening PRs to dev

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.