Explorar skills

Short-form (X / LinkedIn) comparison of how something is done today vs how it will be done in 1–5 years. Strong for tech / AI / tooling takes. Use when the user wants to frame a directional bet, a tooling shift, or an obsolescence call — anything where the punchline is "this is the present; here's the future".

Detection pass for AI-generated patterns and clichés. Final check before publishing. Returns a list of detected issues with severity and fix suggestions.

Esta habilidad finaliza el empaquetado para el lanzamiento en YouTube de episodios explicativos en pizarra, generando un UPLOAD.md listo para copiar y pegar con títulos A/B, descripción SEO, comentario fijado y etiquetas VIDIQ, junto con tres miniaturas principales y un MP4 4K listo para subir preparado con ffmpeg. Soporta los canales Your Channel y Your Second Channel.

Master writing skill. Orchestrates the full pipeline (seed → draft → edit → slop-check → optional repurpose) for any post type — long-form (long-form-weekly-newsletter, long-form-monthly-devlog, long-form-hot-take, long-form-how-to, long-form-launch-retro, long-form-manifesto) or short-form (short-form-x-vs-y, short-form-listicle, short-form-observation, short-form-motivational, short-form-present

Publishes a `status: ready` draft from the weekly calendar to its configured target (Astro blog collection) and archives social derivatives. Reads scribetronic/publish-config.yaml. Updates calendar history and per-week plan. Optionally archives completed weeks. Does NOT push to social platforms (out of scope v1).

The shared style guide every long-form and short-form post inherits. Reference for tone, structure, sentence rhythm, signature moves, and anti-patterns. Always loaded by drafting and editing skills. This is the only skill that should be personalized — every other skill stays format-only.

Short-form comparison post (X / LinkedIn / Threads). Two things contrasted to reveal a non-obvious preference. Use when the user wants to publish an "X vs Y" take — tools, approaches, mindsets, frameworks — and stake a side. Pairs well after a hot-take or how-to long-form piece.

Short-form motivational post within your niche (X / LinkedIn / Threads). WARNING — easiest format to slide into AI slop / coach-speak. Use when you have a personal-stakes statement or hard truth tied to a specific moment in your work — never as generic inspiration. Hard quota: 1-2 per month max.

Propone deltas concretos a `scribetronic/style/writing-style.md` (la guía de voz personalizada del usuario) a partir del historial real de edición del usuario (draft vs publicado). No reescribe automáticamente — genera un documento de propuestas con evidencia textual obligatoria. Invocar tras 3+ piezas publicadas o cuando el usuario sienta drift de voz.

Destila una guía de estilo de escritura desde 3-5 muestras de referencia y 1-2 textos propios. Genera `scribetronic/style/writing-style.md` con las 8 secciones (voice, structure, sentence-level, signature moves, anti-patterns, ejemplos +, ejemplos -, revision checklist). Usar cuando el usuario quiera crear o refrescar la guía de estilo de su blog/newsletter.

Vision/strategy piece (~1500-3000 words). Rare format — once or twice a year. Names what you're building, why it matters, and how you'll get there. Use to plant a flag, reset direction, or invite people into a longer-term mission.

Arrange a project's README and GitHub Pages documentation into a consistent user-first layout: short README that links out, just-the-docs Jekyll site with a user-facing index, one page per user-facing feature (split into child pages when long), and a developer guide with technical sub-pages. TRIGGER when: setting up docs/ for a new project, adding a GitHub Pages site, writing or restructuring a RE