writing

Writes scannable developer documentation, tutorials, proposals, and decision questions with structured formatting rules.

3|Updated Nov 8, 2014
One-click install
npx skills add https://github.com/mintuz/.dotfiles --skill writing-mintuz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing
Source: https://github.com/mintuz/.dotfiles/tree/main/agents/.agents/skills/writing
Command: npx skills add https://github.com/mintuz/.dotfiles --skill writing-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developer-facing content often fails because readers skim before committing, and dense walls of text lose them. This Skill provides a playbook for creating technical documentation, tutorials, proposals, and decision questions that are scannable, honest about risk, and grounded in evidence. ## Core Features & Use Cases - Structured Writing Guidelines: Enforces reader-first principles including scannable headings, short paragraphs, clear payoffs, and consistent voice across technical content. - Decision Question Formatting: Structures questions and multi-option decisions for users with plain-language options, costs, and recommendations stated upfront. - Formatting Reference: Provides detailed rules for titles, headings, paragraphs, lists, intros, and outros via the formatting.md reference file. - Use Case: When drafting a technical proposal, use this Skill to structure the document with problem, evidence, and open questions sections before the recommendation, ensuring reviewers can quickly assess the proposal. ## Quick Start Use the writing skill to draft a tutorial explaining how to set up a local development environment with clear prerequisites and numbered steps.

Frequently Asked Questions about writing

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

FAQPage Schema
How do I write developer documentation that people actually read?▼

Lead with clarity and payoff in the first paragraph, use one concern per heading, keep paragraphs to 3-5 sentences, and state what the reader will achieve before showing how. Break dense information into lists and use headings every 200-250 words.

What structure should a technical proposal follow?▼

Give problem, evidence, and open questions their own headings before the recommendation. Label the target design as a proposal until evidence shows it is implemented, and state every blocker and safety caveat explicitly.

How do I present multiple options to a user for a decision?▼

State the question in one sentence, then list each option with a reply label, what it does, and what it costs in one plain sentence. Omit background detail the choice does not need, and label any recommendation clearly.

When should I apply SEO keyword rules to technical content?▼

Apply SEO keyword placement rules only to public web content such as tutorials and blog posts. Do not apply them to internal docs, proposals, or direct messages to users where natural clarity matters more than search ranking.

What are the limitations of this writing approach?▼

This Skill does not handle commit messages, PR text, or marketing copy. It also requires source facts to ground examples and will not invent APIs, frameworks, or results, so you must supply accurate technical details.