alex-writing-at-work

Standardize writing in Alex's work voice across Notion, Slack, and task trackers.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/kurko/private-prompts --skill alex-writing-at-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alex-writing-at-work
Source: https://github.com/kurko/private-prompts/tree/main/skills/alex-writing-at-work
Command: npx skills add https://github.com/kurko/private-prompts --skill alex-writing-at-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting content across Notion, Slack, and task trackers often yields inconsistent tone and style, slowing collaboration and increasing review cycles. This skill provides a unified voice guide to streamline writing.

Core Features & Use Cases

  • Voice and tone rules for senior-engineer style, focusing on clarity, empathy, and directness.
  • Vocabulary guidance to avoid jargon and keep communication cohesive across Notion pages, Slack messages, and proposals.
  • Framing and structure guidance for briefs, technical docs, and team updates, with concrete examples.

Quick Start

Provide a draft and ask me to rewrite it in Alex's work voice for Notion, Slack, or task trackers.

Frequently Asked Questions about alex-writing-at-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize writing tone and voice for team communication across Notion and Slack?

Standardizing writing tone and voice for team communication involves applying a consistent style guide to drafts in Notion and Slack. This process enforces specific voice rules, vocabulary guidance, and framing to ensure your team's style remains cohesive across platforms.

What's the best way to rewrite technical docs and proposals to match a senior-engineer style?

To rewrite technical docs and proposals in a senior-engineer style, apply framing guidelines that prioritize clarity, empathy, and directness. This approach adjusts vocabulary to avoid unnecessary jargon while maintaining a professional, straightforward tone suitable for engineering documentation.

How do I keep my Notion pages and Slack messages consistent without repeating style edits?

Keeping Notion pages and Slack messages consistent requires applying a unified voice guide to your drafting process. By checking drafts against established anti-patterns and vocabulary rules, you prevent tone drift and reduce the need for repeated manual style edits.

Can I use a predefined voice guide for drafting briefs and team updates across task trackers?

Yes, you can apply a predefined voice guide to drafting briefs and team updates across task trackers. The guide provides structural framing and concrete examples tailored for task trackers, ensuring your communication remains direct and clear regardless of the platform used.

Why does my team communication tone drift when moving between Slack messages and Notion docs?

Team communication tone drifts between Slack messages and Notion docs because each platform encourages different formatting habits. Applying a unified voice guide with anti-pattern checks corrects these inconsistencies, ensuring your tone and style remain aligned across different workspaces.

When should I not use a standardized voice guide for team communication?

You should avoid using a standardized voice guide for team communication when drafting highly sensitive or personalized messages that require an individual's unique tone. The guide enforces a specific senior-engineer style, which may not be appropriate for every interpersonal context.