skills.rest
softspark
softsparkCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

brand-voice

Enforce a direct technical voice and remove generic LLM rhetoric from documentation.

161|21|Updated Mar 26, 2026
Search Tags:#documentation#writing#editing#clarity#voice#style-guide#anti-trope
One-click install
npx skills add https://github.com/softspark/ai-toolkit --skill brand-voice-softspark
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brand-voice
Source: https://github.com/softspark/ai-toolkit/tree/main/app/skills/brand-voice
Command: npx skills add https://github.com/softspark/ai-toolkit --skill brand-voice-softspark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents generic LLM rhetoric, promotional filler, and inconsistent tone in documentation and user-facing content by enforcing a concise, evidence-based technical voice so readers get actionable, reliable information.

Core Features & Use Cases

  • Anti-trope enforcement: Detects and removes banned openings, closing tropes, filler adjectives, and structural padding.
  • Voice principles: Enforces directness, specificity, evidence-backed claims, brevity, active voice, and a technical tone suited for developer audiences.
  • Checklist-driven validation: Uses a before-publishing checklist to confirm no banned phrases, consistent terminology, and removal of weasel words.
  • Use Case: Rewrite a project README, API docs, or help text to replace marketing fluff with specific metrics, concise instructions, and clear outcomes.

Quick Start

Use the brand-voice skill to rewrite the README introduction into concise, technical sentences that remove filler phrases and state measurable outcomes.

Frequently Asked Questions about brand-voice

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

FAQPage Schema
How do I remove AI generated filler text from technical documentation?▼

To remove AI generated filler text from technical documentation, use a checklist-driven validation that detects and replaces banned openings, closing tropes, and filler adjectives with concise, evidence-based phrasing.

How do I enforce a direct writing voice in developer README files?▼

You can enforce a direct writing voice in developer README files by applying active voice, specific claims, and consistent terminology to replace promotional padding with measurable outcomes and clear instructions.

What is anti-trope enforcement for technical writing?▼

Anti-trope enforcement for technical writing is the detection and removal of structural padding, filler adjectives, and generic LLM rhetoric to maintain a concise, reliable, and technical tone for developer audiences.

Does this approach work for editing API docs and changelogs?▼

Yes, this approach works for editing API docs and changelogs by requiring checklist validation to confirm active voice, remove weasel words, and ensure evidence-backed claims suited for user-facing developer materials.

What is the best way to eliminate weasel words from help text?▼

The best way to eliminate weasel words from help text is to run a before-publishing checklist that validates specific claims, active voice, and consistent terminology while removing generic filler and banned phrases.

Related Skills

Explore More Content & Communication Skills→
daniel-heydari-devdaniel-heydari-dev

Documentation

Generate README files, JSDoc, API references, and changelogs.

Community
Intermediate
vib795vib795

devex-review

Quantify developer friction in docs navigation, getting-started flows, and CLI usage.

Community
Advanced
frumu-aifrumu-ai
114

marketing-brand-voice

Creates brand style guides with identity, tone, and content rules.

Official
Intermediate
frankxaifrankxai
6

arcanea-revision-ritual

Revise fiction and narrative prose drafts through seven structured passes.

Community
Advanced