write

Enforce academish prose style for non-code output with tone controls.

5|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/humblemuzzu/ghosttyyy --skill write-humblemuzzu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write
Source: https://github.com/humblemuzzu/ghosttyyy/tree/main/pi-setup/config-skills/write
Command: npx skills add https://github.com/humblemuzzu/ghosttyyy --skill write-humblemuzzu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

prose style is often inconsistent and verbose. This skill enforces an academish voice for non-code output, ensuring precise language, proper sourcing, and a clear, skimmable structure across conversations, docs, commits, and PRs.

Core Features & Use Cases

  • Tone controls: lowercase only, terse, anti-sycophancy, critical stance, late millennial slang, esoteric interpretations.
  • Core principles: claims supported, precision over persuasion, no hyperbole, skimmable structure, credit sources, transparent limitations, explain jargon.
  • Use Case: when drafting replies, PR descriptions, or documentation, apply the academish style to improve clarity, credibility, and traceability.

Quick Start

Apply academish prose style to all non-code output, using lowercase, conciseness, and precise language.

Frequently Asked Questions about write

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

FAQPage Schema
How do I enforce an academish prose style for non-code output and documentation?

To enforce an academish prose style for non-code output, apply tone controls like lowercase text, terse phrasing, and anti-sycophancy. This enforces precise language, proper sourcing, and a skimmable structure across conversations, docs, commits, and PRs.

What is academish prose and how does it improve technical communication?

Academish prose is a writing style prioritizing precision over persuasion, ensuring claims are supported without hyperbole. It improves technical communication by applying critical stance, crediting sources, transparently stating limitations, and explaining jargon for clear credibility.

How do I apply concise tone controls to PR descriptions and commit messages?

You apply concise tone controls to PR descriptions and commit messages by enforcing lowercase text, terse phrasing, and anti-sycophancy. This structural guidance ensures clear, skimmable communication with proper citation quality and traceable claims.

Can I use this academish writing style for drafting replies in daily conversations?

Yes, you can use this academish writing style for drafting replies in daily conversations. It enforces an academish voice for non-code output, applying critical stance, late millennial slang, and esoteric interpretations to improve clarity and precision.

Why does my technical documentation lack precision and traceable claims?

Technical documentation lacks precision when style is inconsistent and verbose. Enforcing an academish voice with claims supported, no hyperbole, and source crediting ensures precise language, transparent limitations, and skimmable structure for improved traceability.

What are the limitations of using terse and lowercase prose in professional docs?

Terse and lowercase prose in professional docs intentionally omits persuasive language and hyperbole, adopting a critical stance. While it enhances precision and skimmability, this anti-sycophancy approach may lack conventional persuasive formatting expected in standard corporate communication.