CtrlK
BlogDocsLog inGet started
Tessl Logo

lirantal/writing-style-explainer

Gives you writing style instructions for Explainer type articles including tone of voice, writing style, structure, content formatting and more.

55

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files
name:
writing-style-explainer
description:
Gives you writing style instructions for Explainer type articles including tone of voice, writing style, structure, content formatting and more.
metadata:
{"author":"lirantal","version":"1.1.0"}

A writing style definition for Explainer-type articles

See the writing style JSON definition for tone, structure, density, and formatting defaults.

  1. No terminal References section — Do not end the post with ## References, “Further reading” link dumps, or a bibliography block. Satisfy sourcing by placing ≥3 descriptive inline links to canonical docs, specs, or repos in the body where each topic is introduced or justified.
  2. Opening paragraphs — Lead with thesis, problem, and why the topic matters. Do not open with: who the “intended audience” is, assumed reader personas, disclaimers about scope aimed at reader segments, or any mention of the cover/OG/hero image (including AI-generated, Sharp/script-generated, or how the asset was produced). Hero imagery is frontmatter and layout concern only.

All other explainer guidance (trade-off tables, validation commands, FAQ depth, and so on) still applies unless AGENTS.md or the user says otherwise.

Workspace
lirantal
Visibility
Public
Created
Last updated
Publish Source
CLI
Badge
lirantal/writing-style-explainer badge