Results for “voice”

Transform articles or scripts into click-driven 16:9 web presentations that look like videos, with optional AI voiceover synthesis.

Review documentation and prose for compliance with writing guidelines, checking style, voice, and tone against a fetched rule set.

Build real-time voice and multimodal AI applications using Pipecat and Daily, covering pipeline architecture, AI service integration, and transport options.

Reference for building real-time voice and multimodal AI applications with Pipecat, covering pipelines, speech services, LLMs, transports, and deployment.

Use to set up or fix quality assurance for voice/phone support, including transcript-based and AI-graded call QA. Trigger for "QA our calls", "score phone conversations", call transcription accuracy for QA, diarisation or speaker attribution problems, word error rate, grading calls from transcripts, or adapting a chat/email QA scorecard to voice.

Write clear, helpful UI copy including microcopy, error messages, empty states, and CTAs that guide users and reinforce product voice.

Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar.

Plan and govern product content: audit existing material, define content models, establish voice and tone, and set ownership workflows.

Write long-form content such as blog posts, guides, tutorials, and newsletters with a distinctive voice derived from supplied examples or brand guidance, ensuring structure, pacing, and credibility.

Collates a movement leader's voice and theme documents into a professionally styled PDF using WeasyPrint.

Embody the voice and methodology of Ai Weiwei to document injustice, make suffering visible, and confront power structures through artistic and documentary strategies.

Collaborates on writing projects by researching topics, structuring outlines, improving hooks, providing section-by-section feedback, and managing citations while preserving the writer's voice.

Transforms chaotic notes, voice dumps, and meeting transcripts into a structured, interlinked knowledge base inside Obsidian by extracting entities, generating wikilinks, and surfacing forgotten context.

Write user-facing copy following Sentry's brand guidelines, covering Plain Speech and Sentry Voice tones for UI text, documentation, and marketing content.

Writes documents in a plain, human voice and removes phrasing that reads as machine-generated, applying a two-pass write-and-audit process to any written artifact meant to be read by a person.

Write clear, developer-friendly documentation — READMEs, API references, code comments, and changelog entries — tailored to the audience and the project's voice. Use when the user says "write docs", "document this API", "update the README", "add code comments", "changelog entry", or "explain this for contributors".

Comprehensive blog writing skill that handles technical blog posts, personal voice writing, brain dump transformation, and category-aware AEO-optimized content. Use when: (1) writing, editing, or proofreading a blog article or post, (2) transforming unstructured brain dumps into polished posts, (3) writing in specific personal voices (Jarad, Nick Nisi), (4) creating category-aware technology/company/product posts, (5) building tutorials, deep dives, postmortems, benchmarks, or architecture posts, (6) writing engineering blogs, dev blogs, programming blogs, coding tutorials, or documentation posts. Triggers: blog post, blog writing, technical blog, dev tutorial, brain dump, article, content writing, developer article, engineering blog, programming blog, coding tutorial, documentation post, technical writing, blog editing, proofreading, developer content

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".

Turn any markdown file into a publication-quality PDF. Proper 1in margins, intelligent page breaks, page numbers, cover pages, running headers, curly quotes and em dashes, clickable TOC, diagonal DRAFT watermark. Not a draft artifact — a finished artifact. Use when asked to "make a PDF", "export to PDF", "turn this markdown into a PDF", or "generate a document". (gstack) Voice triggers (speech-to-text aliases): "make this a pdf", "make it a pdf", "export to pdf", "turn this into a pdf", "turn this markdown into a pdf", "generate a pdf", "make a pdf from", "pdf this markdown".

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".

Prose quality checker for Quarto (.qmd) files, grounded in William Zinsser's *On Writing Well* (30th Anniversary Edition). Checks for clutter, weak verbs, hollow qualifiers, clichés, inflated academic voice, poor leads and endings, pronoun and tense inconsistency, and unclear explanation. Produces a structured markdown report organized by document section — never modifies the source file. Use when asked to improve prose quality, tighten writing, reduce clutter, or apply Zinsser's writing principles to a draft. For grammar and punctuation, use the proofread skill. For APSA style rules, use the apsa-style skill. Supports an optional output-file argument and an optional @sec-label argument to restrict checking to one section.