agentleFS
Sign inStart free
CuleotCuleot/content-forge-kit/skills/humanizer/SKILL.md

humanizer

Skill1 starsChanged 3 months agoNo licenceView on GitHub

AI-taste rewriting: diagnose AI-taste (clichés/template sentences/no personal traces) → rewrite into a real human voice → self-check against the checklist. Mandatory for all outward-facing published content. 中文:去 AI 味改写:诊断 AI 味(套话/模板句/无个人痕迹)→ 改写成真人语气 → 对照清单自查。所有对外发布内容强制过审。

188 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 4 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

11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 175 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.

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.

Check your setup, free