explanatory-writing

Writes explanatory documents and tutorials in a direct, example-driven Hebrew prose style.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/amirbiron/claude-skills --skill explanatory-writing-amirbiron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explanatory-writing
Source: https://github.com/amirbiron/claude-skills/tree/main/skills/explanatory-writing
Command: npx skills add https://github.com/amirbiron/claude-skills --skill explanatory-writing-amirbiron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Explanatory writing often fails because it stays abstract, sounds like generic AI output, or reads like marketing copy. This Skill enforces a concrete, mature writing voice for guides, documentation, courses, and tutorials so readers actually understand and retain the material. ## Core Features & Use Cases - Concrete-example discipline: Every abstract claim must be paired with a specific, detailed example matched to the topic and audience. - Voice and structure rules: Direct second-person address, short punch sentences anchoring key ideas, myth-busting openings, and sections that close with the common mistake, its symptom, and its fix. - Natural Hebrew writing: Keeps technical terms in English where appropriate while ensuring the surrounding prose reads like native Israeli Hebrew, not translated text. - Use Case: Ask for a tutorial on a technical concept, and receive a structured guide with concrete examples, minimal formatting, and a pre-delivery checklist verifying no hype words or unsupported abstractions remain. ## Quick Start Write a beginner-friendly guide explaining how API rate limiting works, using the explanatory writing style with concrete examples.

Frequently Asked Questions about explanatory-writing

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

FAQPage Schema
How do I write better technical tutorials and guides?

Pair every abstract claim with a concrete, detailed example the reader can picture, then generalize. Use direct second-person address, short punch sentences for key ideas, and close sections with the common mistake, its symptom, and its fix.

How to make AI-generated explanations sound less generic?

Remove hype words like revolutionary or game-changing and show value through specific examples instead. Open by challenging a common misconception, avoid over-formatting with bullets and bold, and keep prose as the default structure.

When should this writing style not be used?

Skip it for short everyday chat like simple factual questions, casual conversation, or confirmations, unless the user explicitly requests the style. It is designed for structured teaching content, not quick exchanges.

Does this writing style work for languages other than Hebrew?

Yes, the voice principles are topic- and language-independent. The Hebrew-specific rules only ensure natural native phrasing and keeping established English technical terms untranslated when that is how practitioners actually speak.

What makes an explanation fail to teach effectively?

Explanations fail when they stay at the abstraction level, telling readers what is true without showing how it looks in a real situation. The fix is grounding every idea in a specific example with concrete details like numbers, names, or exact quotes.