Skip to content
Skills Library
Marketing & content · Analysis

aprender

/aprender

Learn from each delivered video so the next edit fits the user better. Runs automatically at the end of /revisar when a video is delivered, or when the user types /aprender or gives feedback about their style ("I don't like…", "more effects", "always…").

Licence
MIT
Last repository change
27.10.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Learn from each delivered video so the next edit fits the user better. Runs automatically at the end of /revisar when a video is delivered, or when the user types /aprender or gives feedback about their style ("I don't like…", "more effects", "always…").

Triggers from the description

I donmore effectsalways…
Original author description

Learn from each delivered video so the next edit fits the user better. Runs automatically at the end of /revisar when a video is delivered, or when the user types /aprender or gives feedback about their style ("I don't like…", "more effects", "always…").

How it works

SKILL.md has no level-two headings · 15 lines, 207 words

SKILL.md preview
---
name: aprender
description: Learn from each delivered video so the next edit fits the user better. Runs automatically at the end of /revisar when a video is delivered, or when the user types /aprender or gives feedback about their style ("I don't like…", "more effects", "always…").
---

# /aprender

The guide `estilos/<style>.guia.md` is the user's living editing guide. Read it at the start of every /editar and follow it.

1. Look at what the user changed during this edit compared with your first proposal (hook, cards, effects density, caption position, cuts) and what they said about the result.
2. Ask ONE short question: "¿Qué cambiarías de este vídeo para los próximos?" (in their language). If they answer "nada", that's fine.
3. Update the guide sections by hand, short bullets with the date:
   - **Le gusta / No le gusta**: concrete and reusable ("cards in sentence case, never ALL CAPS", "fewer whooshes").
   - **Ganchos que funcionaron**: the hook used and its category, when the user liked it.
   If a bullet already exists, add `(×2)`, `(×3)` instead of repeating it.
4. Run `npm run aprender -- --proyecto <id> --nota "<their answer, short>"` to save the numbers (history and «Tus números»). Put the hook category in `decisiones.json` → `gancho.categoria` before running it.
5. When a preference reaches `(×3)` and maps to a style field (font, colors, `efectos.densidad`, `ritmo.maxPlanoMs`, `subtitulos.maxPalabras`…), propose changing the style and apply it only with their yes (via /estilo).
Keep the guide under ~60 lines: merge similar bullets, delete what the user later contradicted.

Versions

The database has no other skills named aprender.

Database snapshot: 13.11.2026 · package version 90e551e2ab93 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 86learn
    Study a technique or topic, with curated references first and then practice problems of that technique from easy to hard. Use when the student names a topic they want to learn or practice ("I want to learn about stacks", "teach me dynamic programming", "problems about binary…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.