Communitygithub.com

AhmedKishki/agent-skills

name: humaniser

Qu'est-ce que agent-skills ?

agent-skills is a Claude Code agent skill that name: humaniser.

Compatible avec~Claude Code~Codex CLI~Cursor
npx skills add AhmedKishki/agent-skills

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

Documentation

Humaniser

Authority

The user is the author. Preserve their meaning, voice, claims, evidence, qualifications, citations, terminology, and deliberate choices. Never invent content or connections.

Without further approval, only correct clear spelling, grammar, tense, and punctuation errors, consolidate genuine repetition, and cut clear filler, tangents, announcements, or empty list items identified in Stage 1. Consolidate by moving or cutting existing wording while preserving distinct support. Anything requiring new wording, interpretation, or restructuring needs explicit consent.

User instructions, comments, answers, and approved wording are authoritative. The user may break these rules. The agent may not. Diagnosis, silence, or “continue” is not consent.

Describe AI-associated tendencies only as concrete writing problems. Never claim AI authorship.

Workflow

Keep the stages separate unless the user overrides them. A new or materially changed draft returns to Stage 1.

1. Diagnose

Return a report only. Map, in order:

  1. the overall narrative arc;
  2. each section's arc;
  3. each paragraph's contribution;
  4. every sentence's function.

Identify repetition at article, section, paragraph, sentence, and phrase levels. Identify filler, tangents, empty list items, announcements, repeated or premature conclusions, vague referents, invalid comparisons, missing logical links, overloaded or empty sentences, and metaphorical, meta, formulaic, inflated, or generic wording.

For each issue, quote the passage and state the problem, its effect, the action needed, and whether Stage 2 may apply it automatically. End with a consolidation and removal plan, a collaborative rewriting queue, and a direct next-step question. Ask whenever the thesis, meaning, or voice is unclear.

2. Apply general changes

Enter after the user asks to proceed. Apply their specified changes. If none are specified, apply only authorised corrections, consolidations, and clear removals. Leave unresolved wording unchanged. Do not add wording, infer connections, change emphasis, or reorder material without approval.

Return the new draft version, its separate change log, and the unresolved queue.

3. Rewrite together

Take one unresolved passage at a time unless the user requests a batch. Quote it, explain the problem, ask for the user's meaning or wording, offer one concise suggestion in their established voice, and offer to keep the original. Apply nothing until the user approves exact wording or supplies their own. Their wording is authoritative apart from authorised mechanical corrections.

Editing rules

  • Every part supports the thesis or governing purpose. Every paragraph contributes one step and every sentence advances it.
  • State claims directly. Remove filler, announcements, meta-commentary, and repeated conclusions. Put conclusions after their support.
  • Prefer concrete actors, actions, relations, mechanisms, consequences, and referents. Noun and verb pairs must make literal or conventional sense.
  • Lists contain only distinct, relevant, compatible items. Transitions express a real relation.
  • Prefer positive formulations. Negate only a relevant claim worth rejecting. Use not X but Y only when X is a real common view that the argument displaces.
  • Introduce no metaphor unless the user supplies or approves it.
  • Keep prose direct, conversational, precise, and recognisably the user's. Preserve necessary technical language and purposeful repetition.
  • Prefer full stops. Introduce no semicolons or em dashes without approval.

Versions and change log

Preserve the user's version system. Otherwise call the source Draft v1 and increment every delivered revision containing changes. Reports and unapproved suggestions do not change the version.

Keep the change log outside the draft. Record every change with its location, exact before and after wording or cut text, reason, and authority. Verification is read-only. Queue newly found issues instead of silently fixing them.

Apply the same method in any language.

Skills associés