Escrita e Conteúdo

Evaluate a shared AI skill or skill repository before installing or copying patterns.

Writing guideline for long-form content — trigger on drafting, editing, or polishing any extended prose (articles, essays, op-eds, features, profiles, longform, blogs, newsletters), including NYT/AP-style or "in the style of" major-newspaper requests, unless another style is specified.

Weekly newsletter — the parent piece of the week. ~600-1200 words. Drafted Sunday. Spawns 5-7 derivative short-form pieces for X / LinkedIn / Threads via /write Phase 5. The recurring Sunday default.

Adaptive summarization — output length scales with input length for comfortable reading. Triggers: "summarize", "summarize this", "tldr", "too long", "sum up", "key points", "give me summary", "eli5", "explain like I'm 5", "explain simply". NOT FOR: translation (just ask), content creation (use content-humanizer). Produces: summary at optimal compression ratio based on input length.

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.

Monthly devlog — longer, more reflective recap. ~1200-2000 words. Stitches together the month's work, names the pattern, draws a non-obvious lesson. Goes deeper than a weekly recap.

Core principles for technical communication such as commits, PR descriptions, branch names, and technical documentation. Use when writing or refining engineering-facing messaging and when other skills need a shared communication baseline.

Maintain the Zensical-powered documentation site — nav ordering in zensical.toml, the docs GitHub Pages workflow, CSS and JS assets, and link/anchor integrity across docs/**/*.md. Sibling of /techne:docsync (which only verifies prose claims against code). Use when the user wants the site itself audited — config, deploy pipeline, theming, assets, cross-page links — rather than content accuracy.

Use when repository documentation is stale and the user asks to refresh docs to match the current codebase and workflows.

Esta skill processa currículos ou materiais de carreira brutos (como notas de experiência, descrições de projetos ou anotações) para criar um currículo de candidatura a emprego para o mercado dos EUA. É acionada por pedidos como "ajude-me a reescrever meu currículo" ou "estruture minhas anotações em um currículo".

Use when creating a new pulse skill, editing an existing pulse skill, or verifying a skill works under pressure before deploying. Use when you need an agent skill to be bulletproof against rationalization. Do NOT use for project-specific AGENTS.md conventions or one-off solutions.

Generate properly formatted Markdown from unstructured notes, scratch text, transcripts, or rough drafts. Use when the user wants content rewritten into cleaner Markdown without inventing new information.