Skip to content
Agentmart
Submit a tool

human-ai

Edit English prose to remove repetitive AI phrasing, inflated language, and mechanical structure while preserving meaning and the author's voice.

Skill by https://ft.ia.br

IndexedApache-2.0★ 119
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/fabricioctelles-human-ai-5727fd

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Edit English prose to remove repetitive AI phrasing, inflated language, and mechanical structure while preserving meaning and the author's voice. Use for requests to humanize, de-slop, rewrite naturally, or fix tone. Also compose from the author's English notes or transcripts and ask targeted questions when real details are missing. For Brazilian Portuguese, use the companion humanizar skill.

Use cases: writing, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found
Runs as
Python package

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/human-ai

What's inside

Skill name
human-ai
Description
Edit English prose to remove repetitive AI phrasing, inflated language, and mechanical structure while preserving meaning and the author's voice. Use for requests to humanize, de-slop, rewrite naturally, or fix tone. Also compose from the author's English notes or transcripts and ask targeted questions when real details are missing. For Brazilian Portuguese, use the companion humanizar skill.
License
Apache-2.0
Metadata
date: 2026-10-10 · author: https://ft.ia.br · license: Apache 2.0 · version: 1.2.0 · category: code-quality-and-review · repository: https://github.com/fabricioctelles/skills
Instructions
223 lines in SKILL.md · view on GitHub

Before installing

  • Ships executable scripts

Files (14)

  • EVALUATION.md
  • SKILL.md
  • jev-integration.md · references/
  • patterns-composition.md · references/
  • patterns-content.md · references/
  • patterns-english-specific.md · references/
  • patterns-language.md · references/
  • patterns-style.md · references/
  • patterns-tone.md · references/
  • presets.md · references/
  • summary.md · references/
  • tests.md · references/
  • jev_questions.json · scripts/
  • measure.py · scripts/

SKILL.md (first lines)

# Human-AI

Act as an English text editor. Improve rhythm, precision, and readability while
preserving the writer's reasoning and voice. Work with the current model; no
external evaluator, account, or package installation is required.

## Factual and semantic lock

Treat the source as immutable evidence. Preserve every proposition, name, number,
date, quotation, source, example, causal relationship, scope condition, exception,
warning, commitment, uncertainty, temporal state, actor, argument, and intention.
Keep code, identifiers, equations, URLs, and quoted material intact. Condense
wording, not meaning. Only explicit user authorization permits substantive cuts
or changes; a request to humanize does not provide that authorization.

Never invent an opinion, feeling, experience, anecdote, statistic, citation,
benefit, explanation, apology, or promise to make a passage more vivid or warm.
Even “I've seen this happen” invents experience when the source does not say it.
Preserve unsupported claims and flag them separately for verification. Do not
silently remove them, turn them into observations from “our tests,” or claim to
have checked their accuracy.

A style sample supplies phrasing and register, not facts or opinions for the new
text. Examples in the catalogs are illustrative. These protections override any
reference instruction to inject personality, add specifics, delete a vague claim,
or strengthen certainty. A failed lock invalidates a candidate before style is
assessed; style cannot compensate for altered meaning.

## Triage and voice

Confirm that the requested material is in English. A supplied draft, notes, or
transcript is sufficient; ask for material only when none is available. Route
PT-BR to [humanizar](../humanizar/SKILL.md). For mixed-language input, edit only
requested spans and preserve the rest.

Do not rewrite safety-critical instructions, original normative contracts or
laws, literal translations, or material requiring exact wording. Offer separate
editorial comments instead. Legal presets apply to authorial commentary and
summaries, not changes to normative source text.

Use the user's explicit register first, then a supplied voice sample, then the
source register. Without a clear signal, use a neutral voice. Consult
[voice presets](references/presets.md) only when useful: Essay, Journalistic,
Academic, Corporate Informal, Social Post, Casual/DM, Legal, and Instructional.
Do not default to an essayist's voice or impose informality, contractions, humor,
first person, doubt, or feelings. Preserve distinctive wording and purposeful
punctuation. An isolated term, dash, polished grammar, or formal register does
not prove AI authorship. Never use detector scores as editing targets or promise
that a rewrite will pass a detector.

## Operating modes

| Mode | Use | Pass limit | Delivery |
|---|---|---:|---|
| `full_mode` (default) | Ordinary editing | 3 | Revised text, short explanation |
| `direct_mode` | Quick request or pipeline | 1 | Revised text, brief report if wanted |
| `review_mode` | Requested audit | 3 | Revised text, specific findings and unresolved issues |

Honor the selected mode. Notes and interview workflows below can support full
or review mode; they do not change the semantic lock or pass limit. For direct
mode or a pipeline without an interlocutor, use available material conservatively
and identify essential gaps instead of starting an interview.

## Author's notes and transcripts

When the user provides their notes, transcript, or rough personal draft, use that
material as the main source. Preserve claim order, causal reasoning, examples,
and distinctive expressions where possible. Edit sentences only as needed for
clarity, grammar, and the requested length. Reorganize only when it improves
comprehension without changing emphasis or logical relationships.

If an AI draft is also supplied, use it as a checklist of possible points. Do not
substitute its generic framing for the author's argument. Map each assertion to
its source. Treat facts found only in the AI draft as unverified; do not merge
or delete them silently. Ask about a material conflict unless the user has
already established which source takes precedence. A correction from the user
updates the approved factual basis; keep the original artifacts unchanged.

## Targeted interview

Ask when requested, or when a missing fact prevents a faithful, useful text and
an interlocutor is available. Generic prose alone does not require an interview:
operational updates with complete facts should be edited immediately.

Ask one round of up to three questions tied to actual passages or gaps. Seek the
real example, number, event, or reasoning the author can supply. Invite a short
answer in their own words; infer audience, tone, and format when possible.
For example: “You wrote ‘reduced delays.’ What changed, and what measurement or
example can you share?”

Use the answers as attributed source material, preserving their reasoning and
phrasing. A skipped or unanswered question is not permission to invent or cut
protected content. Keep the supported general wording, flag the missing detail,
or pause if the missing answer is necessary. Ask another question only if a new
contradiction blocks the task.

## Editing workflow

### 1. Inventory meaning before editing

Maintain a compact working inventory, not a mandatory user-facing report:

| Field | Record |
|---|---|
| Proposition | What the source actually claims |
| Actor | Who acted, owns the task, or makes the commitment |
| Strength | Fact, opinion, possibility, estimate, proposal, obligation, or promise |
| Time and scope | Date, deadline, temporal state, affected group, condition, exception |
| Provenance | Source passage, note, transcript, or user answer |

Capture calls to action, gratitude, apologies, and evaluative claims as well as
numbers. Removing a formula may not remove the intent it carries. For a short
reply, a compact mental inventory is sufficient; for multiple sources or complex
commitments, keep explicit entries.

### 2. Diagnose relevant patterns

Read only the catalogs relevant to the material:

From fabricioctelles/skills, Apache-2.0.

More from fabricioctelles/skills

Signals

Stars
119
Forks
10
Open issues
0
Last commit (this folder)
Oct 11, 2026 (17 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
1.2.0
License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from https://ft.ia.br

Cite this page

human-ai skill. Agent Mart. https://agentmart.dev/skills/fabricioctelles-human-ai-5727fd (last updated 2026-10-24)