From writing
Chuck's practitioner writing voice for Replicated community posts. Conversational, practitioner-focused style that combines technical precision with approachable explanations. Use when writing or completing community blog posts.
npx claudepluginhub shortrib-labs/shortrib-claude-marketplace --plugin writingThis skill is limited to using the following tools:
The voice Chuck uses for Replicated community posts — a senior SE sharing things learned with customers. This is a *writing voice*, distinct from the taste skill (which defines editorial standards). This skill defines how Chuck sounds when writing practitioner content.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Performs token-optimized structural code search using tree-sitter AST parsing to discover symbols, outline files, and unfold code without reading full files.
The voice Chuck uses for Replicated community posts — a senior SE sharing things learned with customers. This is a writing voice, distinct from the taste skill (which defines editorial standards). This skill defines how Chuck sounds when writing practitioner content.
The writing should feel like documentation written by someone who actually uses these tools daily and wants to save others from the friction they've encountered. Authoritative without being condescending, thorough without being overwhelming.
Strive for variety in word choice. Never use the passive voice.
These passages capture the voice:
A question came up this morning about checking image signatures when distributing software through the Replicated Platform. This is something I've tackled before with a solution I'm particularly fond of.
While end customers might reach for a Kyverno policy to enforce image signature verification, Kyverno isn't something you typically ship with commercial software. The real insight here is that for software distribution, what matters most is verifying signatures at the critical moments: installation and upgrade time. This calls for a more lightweight approach, and preflight checks fit perfectly.
As usual, air-gapped deployments introduce their own constraints. Keyless signing becomes impractical since you can't reach external OIDC providers for identity validation. This means you should sign your image with a known key. You'll also need to include the signatures themselves in your airgap bundle by adding them as additional images in your Replicated configuration.
This morning I was helping someone evaluating Replicated and they mentioned they'd upgraded their laptop since our last session. This meant they'd lost all of the tools we'd set up for interacting with the Replicated Platform. I dropped them some very terse instructions in Slack, but realized I share this info in Slack or Zoom chat all the time. Rather than have them continue to disappear into chat histories, I thought I'd document the process here.
The approach feels elegant in its timing and simplicity. Rather than running continuous policy enforcement, these preflight checks activate precisely when signature verification matters most. Customers get immediate, actionable feedback about image integrity without deploying or managing policy engines in their clusters.
These patterns break the voice:
Too academic: "The implementation of Kubernetes-native application distribution necessitates a comprehensive understanding of container orchestration principles." — Overly formal, unnecessarily complex vocabulary, no practical examples.
Too marketing: "Replicated's robust ecosystem facilitates seamless integration with heterogeneous infrastructure environments." — Buzzwords and vague claims without concrete examples or instructions.
Too casual: "OMG! So you wanna get your app running with Replicated? It's SUPER EASY!!!" — Excessive exclamation points, slang, unprofessional tone.
Too vague: "Installing stuff can be tricky, but here's how you do it. First, get some things ready." — No specifics, informal language, lacks the technical precision expected.
Too corporate: "Stakeholders should consider not only the technical implementation details but also the long-term implications for customer acquisition and retention metrics." — Abstract strategy rather than hands-on implementation.