writer

Guide writing style and tone for content types with persona selection.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/kirvin/copilot-cli-essentials --skill writer-kirvin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writer
Source: https://github.com/kirvin/copilot-cli-essentials/tree/main/plugins/cpe/skills/writer
Command: npx skills add https://github.com/kirvin/copilot-cli-essentials --skill writer-kirvin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write content that sounds natural and engaging, avoiding robotic or overly corporate language, tailored to specific audiences and purposes.

Core Features & Use Cases

  • Persona-based writing: Adapts tone and style for different roles (Engineer, Architect, PM, Marketer, Educator, Contributor, UX Writer).
  • Core Principles: Emphasizes clarity, concreteness, and reasoned opinions.
  • Forbidden Patterns: Avoids AI tells, em dashes, and corporate jargon.
  • Use Case: When writing a README for a new feature, you can use the 'Engineer' persona to explain its technical details clearly, and then switch to the 'Marketer' persona to draft a compelling blog post about its benefits.

Quick Start

Use the writer skill to draft a commit message for a bug fix.

Frequently Asked Questions about writer

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

FAQPage Schema
How do I make AI-generated content sound more human and less robotic?

To make AI content sound more human, you need writing style guidance that enforces clarity, avoids corporate jargon, and blocks common AI tells. This Skill provides persona-based tone selection to adapt output for specific audiences and roles.

What is the best way to write technical documentation for different audiences?

The best way to write technical documentation for different audiences is to use persona-based writing. This Skill adapts tone and style for roles like Engineer, Architect, and UX Writer, ensuring content clarity and reasoned opinions tailored to each audience.

How do I avoid AI writing patterns and corporate jargon in marketing copy?

To avoid AI writing patterns and corporate jargon in marketing copy, apply specific forbidden pattern rules. This Skill identifies and blocks AI tells, em dashes, and jargon, allowing you to switch to a Marketer persona for compelling, natural content.

Can I use a single writing style guide for both README files and blog posts?

You can use a single style guide for both README files and blog posts by switching personas. This Skill supports adapting tone from an Engineer persona for technical details to a Marketer persona for drafting compelling benefit-driven communication.

What tone should I use for UX writing and user communication?

For UX writing and user communication, you should use a tone emphasizing clarity and concreteness. This Skill offers a dedicated UX Writer persona, providing specific advice on style and tone to ensure natural, engaging output.

Why does my AI content sound overly corporate and how do I fix it?

Your AI content sounds overly corporate because it lacks defined style constraints. To fix it, this Skill applies core writing principles and forbidden patterns that eliminate corporate jargon and AI tells, ensuring human-sounding output.