Gh brand voice

Skill aymandakirgh/ghclaudetoolkit/skills/gh-brand-voice

Use when writing or editing any GrowthHackers (GH) content and the user asks about tone of voice, brand voice, how something should sound, whether copy is on-brand, or to rewrite copy in GH's voice. Triggers on "is this on brand", "GH voice", "make this sound like us", "tone of voice", "brand tone", "rewrite in our voice", "benefit-first copy", "no how-to", "what's our CTA", "review this copy for brand", "banned words". Enforces EN for public / IT for internal, benefit-first messaging with no how-to detail, the CTA "lo gestiamo noi", banned hype words (synergy, 10x, game-changer), real numbers only, and Ayman positioned as a builder not a founder.From its SKILL.md

Install

npx -y skills add aymandakirgh/ghclaudetoolkit --skill gh-brand-voice

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.2 KB, as published. Nobody here has run it

gh-brand-voice

The tone contract for GrowthHackers content. Apply it whenever producing or reviewing GH-branded copy. This skill is the voice foundation that gh-launch-post and gh-kb-note build on.

Language policy

Public content → English. Anything outward-facing (site, product, launch, social, OSS).
Internal content → Italian. Knowledge-base notes, internal docs, team-facing prose.
When in doubt about audience, ask; do not mix languages within one artifact.

Voice principles

Benefit-first, not feature-first. Lead with the outcome the reader gets, not the mechanism.
No how-to. GH content states what changes for the customer and the result — it does not teach the method or expose the playbook. The promise is "lo gestiamo noi" (we handle it).
Concrete and earned. Use real numbers only. Never invent metrics, percentages, or results. If a number isn't verified, leave it out (internal drafts may flag it #da-validare).
Plain and direct. Short sentences. Active voice. No filler, no throat-clearing intros.
Ayman = builder. When attribution matters, Ayman is a builder shipping at GH — not a founder, not the CEO. (See gh-agent-org for the full org chart.)

Standard CTA

The default call to action for GH brand content is "lo gestiamo noi" — the customer doesn't have to learn or do the work; GH handles it. Adapt the surrounding sentence to context, but keep that promise intact.

Banned words (hard stops)

Never ship these or their close variants:

synergy
10x (and "10×", "ten times the…" as hype)
game-changer / game changing

Also avoid generic hype that says nothing: "revolutionary", "next-gen", "cutting-edge", "seamless" (when it just means "works"). If a sentence survives deleting the hype word, delete it.

Review checklist

When asked "is this on brand?", check each line:

Right language for the audience (EN public / IT internal)?
Benefit-first, no how-to leaking the method?
Any banned or hype words? Remove them.
Every number real and verifiable? Strip or #da-validare the rest.
CTA present and equivalent to "lo gestiamo noi" where a CTA belongs?
Attribution correct (Ayman = builder, org chart respected)?

Return the corrected copy plus a short list of what you changed and why.

Scope boundary

This skill governs tone and framing. For launch-format mechanics (threads, Show HN, cadence) use gh-launch-post; for KB structure and wikilinks use gh-kb-note.