Numbered Testimonial Slider
Prueba que se puede escanear: un número, una cita, un resultado.
Convierte tu IA en un creador de secciones de testimonios: convierte un conjunto de citas de clientes en un deslizador numerado donde cada diapositiva lleva un punto de prueba numerado, una cita y un resultado, para que los visitantes escaneen la evidencia en lugar de vadear un muro de elogios.

Instálala en 3 pasos
Sin registro. Sin herramientas CLI. Elige tu IA, copia una línea y pégala.
¿Prefieres hacerlo tú mismo? Compra la habilidad ($4.99), descarga el ZIP desde la confirmación de compra, descomprímelo en el directorio que se muestra arriba y reinicia tu sesión de IA — el mismo resultado. ¿Ya la compraste? Tu asistente de IA puede descargarla por ti.
Qué incluye
Un SKILL.md (la guía paso a paso) + una plantilla inicial. Una vista previa:
Numbered Testimonial Slider
When to use
- Your landing page has a wall of undifferentiated quotes and visitors scroll past all of them
- You have three to eight strong customer quotes and want each one to land as its own proof point instead of blurring together
- A sales page needs social proof near the price or the call to action, but a static grid of quotes eats too much vertical space
- Your testimonials currently read as vague praise ("Great product!") with no outcome a buyer can picture
- You want a testimonial section that works as well for a skimmer (numbers + outcomes) as for a careful reader (full quotes)
Workflow
- Collect and rank the quotes (input: raw testimonials → output: a ranked shortlist)
Gather every testimonial you have — quotes, review snippets, email praise, support threads — and keep only ones with three parts: who said it (name, role, company or context), what changed (a concrete outcome), and the words in their voice. Rank them by how specific the outcome is, not by how enthusiastic the praise is. "We cut onboarding from two weeks to three days" beats "Absolutely love it!" every time. Pick three to eight; fewer than three is not a slider, more than eight is a chore. - Number for the argument, not the order (input: shortlist → output: numbered proof points)
Assign each slide a number, then decide what the number means: it can be the sequence of a story (01 the problem, 02 the switch, 03 the result), or simply the count of proof points ("01 of 06"). Write a short proof label for each number — the outcome in six words or fewer, e.g. "01 — Onboarding in three days." The number is a scanning device: a visitor who reads only the numbers should still get the shape of the argument. If the numbers add nothing, the slider is decoration. - Write one slide per quote (input: numbered proof points → output: slide drafts)
Each slide carries exactly four elements: the number, the proof label, the quote in the customer's own words (trimmed to one or two sentences, never rewritten into marketing speak), and the attribution (name, role, and one line of context). Trim quotes by cutting filler, never by inventing words — if you must shorten, use an ellipsis and keep the meaning intact. One slide, one quote, one outcome: if a quote contains two outcomes, split it or pick the stronger one. - Design the slider mechanics (input: slide drafts → output: slider spec)
Specify how the slider behaves: one slide visible at a time on mobile, one large slide with a peek of the next on desktop; auto-advance off by default (auto-rotating quotes train visitors to ignore them); previous/next controls plus visible dots or a "02 / 06" counter; keyboard arrows and swipe support; pause any motion when the visitor interacts. The active slide's number is large and prominent; inactive slides are hinted, not hidden entirely, so visitors sense there is more evidence. Every slide must be reachable without JavaScript for the no-JS fallback — the slider degrades to a stacked list, not a blank box. - Place it where the doubt lives (input: slider spec → output: placed section)
Put the slider immediately after the claim it supports: after a pricing block if the doubt is "is it worth it," after a feature list if the doubt is "does it actually work," near the final call to action if the doubt is "should I trust this." Add a one-line heading above the slider that frames the evidence ("What changed for teams like yours") — never "What our customers say," which frames it as praise instead of proof. Below the slider, keep one quiet link ("Read more stories") rather than a second wall of quotes.
Vista previa de la plantilla
Numbered Testimonial Slider — Brief Template
One slider = 3–8 proof points. Fill this in before building the section.
Heading (frames evidence, not praise)
> {e.g. "What changed for teams like yours"}
Placed after: {pricing block / feature list / final call to action} — the claim it supports: {claim}
Slides
Slide 01 — {proof label, ≤6 words}
> "{quote, 1–2 sentences, customer's own words}"
Attribution: {name}, {role}, {company or context} Permission to publish: [ ] Confirmed
Slide 02 — {proof label, ≤6 words}
> "{quote}"
Attribution: {name}, {role}, {company or context} Permission to publish: [ ] Confirmed
El paquete de la habilidad (SKILL.md + plantilla) está escrito en inglés.


