Textoreal

TextoReal

Purpose

Rewrite Spanish text to reduce AI-generated signals: filler phrases, overly clean symmetry, repetitive connectors, flat cadence, inflated abstraction, and predictable closing formulas.

This skill applies exclusively to texts written in Spanish. Do not apply it to texts in other languages.

Always preserve:

• Exact meaning.
• Data, names, dates, figures, and quotes.
• The register requested by the user.
• The original intent of the text.

Always improve:

• Naturalness.
• Syntactic variety.
• Verbal precision.
• Rhythm.
• Informational density.
• Human voice.

Hard rules (apply without exception)

These corrections are mandatory. Do not skip them regardless of context, register, or how natural the original phrasing seems.

• Em-dashes as incises (—texto—): always replace with commas or rewrite the sentence. No exceptions.
• Em-dashes as connectors (X —Y): replace with a comma, a period, or rewrite. Never keep.
• Serial connectors: cut "Además", "Asimismo", "Por otra parte", "En este sentido", "Por ende", "En consecuencia" unless the logical relationship would be genuinely unclear without them.
• Throat-clearing openers: if the first sentence of a paragraph delivers no real information, cut it or replace it with a direct entry. Always.
• Inflated triads (rápido, eficiente y escalable): reduce to one precise adjective if the three say the same thing.
• "Lo que realmente ocurre es..." / "Lo que pasa es que...": rewrite as a direct statement.
• "Imagina que..." as a rhetorical device: cut or replace with a direct call to action.

---

Core rule

Do not "embellish". Do not make the text longer. Do not make it more solemn. Do not insert gratuitous jargon. Do not replace a human phrase with a "pretty but artificial" one.

Primary criterion:

> Si una persona culta, clara y directa no lo escribiría así de forma espontánea, corrígelo. > (If a cultured, clear, and direct person wouldn't write it that way spontaneously, fix it.)

---

Silent diagnosis

Before rewriting, internally detect which of these patterns the text contains.

1) Throat-clearing openers

Eliminate openings such as:

• "En un mundo donde…"
• "Hoy en día…"
• "Cabe destacar que…"
• "Es importante señalar que…"
• "Sin lugar a dudas…"
• "A lo largo de la historia…"
• "Desde tiempos inmemoriales…"

If the first sentence delivers no real information, cut it or replace it with a direct entry.

2) Over-perfect binary contrasts

Reduce structures such as:

• "No se trata de X, sino de Y."
• "No solo X, sino también Y."
• "Más que X, es Y."
• "No es simplemente X; es Y."

Use them only when they genuinely clarify. If they sound mechanical, replace with plainer phrasing.

3) Inflated triads

Avoid sequences such as:

• "rápido, eficiente y escalable"
• "sólido, robusto e innovador"
• "claro, conciso y preciso"

If three adjectives can be reduced to one good one, do it.

4) Excessive abstraction

Convert hollow nouns into verbs or concrete facts:

• "realizar una implementación" → "implementar"
• "llevar a cabo una optimización" → "optimizar"
• "hacer una evaluación" → "evaluar"

Prefer a strong verb over an abstract noun.

5) Serial connectors

Do not chain:

• "Además" / "Asimismo" / "Por otra parte" / "En este sentido" / "Por ende" / "En consecuencia"

Use them only when the logical relationship is not obvious from the sentence order.

6) Uniform rhythm

Break the monotony of sentences with identical length and cadence. Alternate:

• short sentence,
• medium sentence,
• sentence with subordination when needed.

Do not reduce everything to clipped phrases. Aim for natural rhythm, not telegrams.

7) Unnecessary passive voice

Prefer active when precision is not lost:

• "fue implementado por el equipo" → "el equipo lo implementó"

Keep passive only when the agent is irrelevant or should be concealed.

8) Empty formality

Reduce expressions such as:

• "con el objetivo de" / "a efectos de" / "en el marco de" / "proceder a" / "dar cumplimiento a"

Replace with direct language unless the context demands legal or administrative register.

9) Automatic summary closers

Avoid endings such as:

• "En definitiva…" / "En conclusión…" / "En resumen…" / "En última instancia…"

Keep the closing only if it genuinely organizes the text; otherwise, end on the final idea.

10) Prefabricated intensifiers

Moderate words such as:

• "sumamente" / "verdaderamente" / "realmente" / "increíblemente" / "altamente" (when it measures nothing)

Also eliminate worn-out metaphors used as intensifiers, such as:

• "con precisión quirúrgica" — replace with a concrete description of what was done precisely, or cut it.

Do not inflate; be precise.

11) Generic marketing adjectives

Be suspicious of:

• "innovador" / "transformador" / "revolucionario" / "potente" / "integral" / "de vanguardia"

Replace with a concrete property or remove them.

12) English calques

Naturalize expressions that sound translated:

• "direccionar" → "dirigir" or "orientar"
• "apalancar" → "impulsar" or "aprovechar"
• "disruptivo" → use a more precise alternative when appropriate

13) Redundant explanation

If a sentence repeats the previous idea in different words, keep the better one and cut the other.

14) Weak precision

Replace catch-all verbs:

• "hacer" / "tener" / "poner" / "dar" / "permitir" / "gestionar" (when it specifies nothing)

Use more exact verbs when they exist.

15) Artificial typography and punctuation

Em-dashes used as idea separators: Do not use em-dashes (—) as separators, artificial incises, or structures copied from English. In standard Spanish, prefer well-constructed commas, parentheses when genuinely needed, separate sentences, or natural subordination.

| Avoid | Use instead | |---|---| | "El sistema —que ya estaba en producción— falló." | "El sistema, que ya estaba en producción, falló." | | "No buscaban velocidad —buscaban estabilidad." | "No buscaban velocidad, buscaban estabilidad." |

Graphic symbols inside paragraphs: Do not use → ⇒ ✓ ✗ emojis or decorative ASCII inside prose. Avoid visually exaggerated lists or slide-style writing. Text must read as written for real reading, not for a productivity interface.

Emojis: Do not add emojis unless the user explicitly requests them or the register clearly calls for them. By default: remove decorative emojis, remove artificial visual emphasis, keep only verbal information.

Excessive Markdown: Reduce unnecessary bold, redundant headings, fragmented blocks, and lists where a clear paragraph would suffice. Do not convert normal text into a pseudo-presentation.

---

Rewriting method

Apply in this order:

1. Preserve factual content.
2. Cut filler.
3. Replace abstraction with action.
4. Break repetitive patterns.
5. Adjust tone and rhythm.
6. Re-read as if it were published human prose.
7. Touch only the minimum necessary.

Priority hierarchy

When in doubt, follow this order:

1. Fidelity to meaning.
2. Genuine naturalness.
3. Clarity.
4. Brevity.
5. Elegance.

Never sacrifice meaning for style.

---

Tone

Default: clear, sober, natural neutral Spanish.

Avoid: grandiloquence, automatic sales tone, excessive solemnity, artificial friendliness, feigned enthusiasm.

If the user requests a specific register, adapt accordingly: académico / técnico / corporativo / periodístico / marketing / divulgativo / jurídico

---

Constraints

Do not:

• Add data not present in the original.
• Invent examples.
• Change figures, names, dates, or references.
• Make text colloquial if the register is formal.
• Introduce regional expressions unless the user requests them.
• Rewrite to the point of erasing the author's own voice.
• "Humanize" by introducing deliberate errors.

---

When to intervene minimally

If the text already sounds human and clean:

• preserve the structure,
• correct only minor repetitions,
• do not redo everything just to demonstrate skill.

The best edit is sometimes minimal.

---

Default output

Return only the final rewritten text, with no additional explanation.

Optional output (when the user requests a diagnosis)

Use this format:

### Patrones detectados
- ...
- ...

### Versión revisada
[texto]

### Cambios clave
- ...
- ...

---

Examples

Example 1 — Throat-clearing opener + abstract noun + empty formality

Input: > Es importante señalar que la implementación de esta solución permite llevar a cabo una optimización de los procesos con el objetivo de maximizar la eficiencia operativa.

Output: > Esta solución simplifica los procesos y hace que el equipo trabaje mejor.

---

Example 2 — Serial connectors + uniform rhythm

Input: > El sistema es rápido. Además, es eficiente. Asimismo, permite escalar sin problemas. Por otra parte, su configuración es sencilla. En este sentido, resulta ideal para equipos pequeños.

Output: > El sistema es rápido, escala sin problemas y no requiere configuraciones complejas. Para equipos pequeños, es una opción sólida.

---

Example 3 — Em-dash + inflated triad + automatic closer

Input: > La plataforma —diseñada desde cero— ofrece una experiencia clara, concisa y precisa. En definitiva, estamos ante una solución verdaderamente transformadora.

Output: > La plataforma, diseñada desde cero, ofrece una experiencia precisa. Es una solución que resuelve el problema sin adornos.

---

Example 4 — English calque + generic marketing adjective + redundant explanation

Input: > Buscamos apalancar nuestras capacidades disruptivas para direccionar los esfuerzos hacia un modelo innovador que genere valor. En otras palabras, queremos hacer las cosas de forma diferente para obtener mejores resultados.

Output: > Queremos aprovechar lo que ya sabemos hacer para construir un modelo que genere valor real.

---

Example 5 — Minimal intervention (text that already sounds human)

Input: > Llevamos tres semanas probando el sistema en producción. Los resultados son buenos, aunque todavía hay un par de cosas por ajustar en la parte de reportes.

Output: > Llevamos tres semanas probando el sistema en producción. Los resultados son buenos, aunque quedan un par de ajustes pendientes en los reportes.

(Minimal change: "cosas por ajustar en la parte de" compressed to "ajustes pendientes en los".)

---

Final control check

Before delivering, verify mentally:

• ¿Quité relleno?
• ¿Se mantiene el sentido?
• ¿Suena escrito por una persona real?
• ¿Hay variedad de ritmo?
• ¿Cada adjetivo aporta algo?
• ¿Cada conector era necesario?
• ¿Quedó alguna frase "demasiado perfecta" o demasiado simétrica?
• ¿El cierre termina en una idea, no en una plantilla?

If anything still sounds generic, rewrite it once more.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: alfredcertain
• Source: alfredcertain/claude-skills
• License: Apache-2.0

Install and usage instructions live in the source repository linked above.