verbal-language-system

Builds a canonical verbal-system.md governing brand voice, tone, claims, and child-skill copy routing.

2|Updated Jun 19, 2025
One-click install
npx skills add https://github.com/Prat05devs/dapper-city-threads --skill verbal-language-system-prat05devs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verbal-language-system
Source: https://github.com/Prat05devs/dapper-city-threads/tree/main/.agent/skills/verbal-language-system
Command: npx skills add https://github.com/Prat05devs/dapper-city-threads --skill verbal-language-system-prat05devs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Brand communication often drifts across channels, uses unsupported claims, or sounds generic. This Skill establishes a single canonical verbal identity file (verbal-system.md) so every LinkedIn post, website page, campaign, press release, presentation, and video script stays consistent, audience-appropriate, and factually safe to publish. ## Core Features & Use Cases - Canonical verbal identity file: Creates or updates verbal-system.md with voice principles, adaptive tone dimensions, messaging architecture, brand dictionary, CTA patterns, proof language, and claim governance. - Claim-safety governance: Classifies claims as safe-public, approval-required, internal-only, or prohibited, and rewrites unsupported statements into goals, proposals, or observations. - Child-skill routing: Routes surface-specific work to child skills such as linkedin-post-system, website-copy-system, campaign-messaging-system, public-relations-copy-system, and video-script-system using the shared verbal-system.md context. - Use Case: A founder preparing a product launch asks for a LinkedIn announcement, landing page copy, and a press note. The Skill first builds verbal-system.md from context.md and design.md, then routes each asset to the right child skill so all three outputs share one message core with channel-appropriate execution. ## Quick Start Use the verbal-language-system skill to build a verbal-system.md from my context.md and design.md, then draft a launch announcement for LinkedIn.

Frequently Asked Questions about verbal-language-system

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

FAQPage Schema
How do I create a consistent brand voice across multiple channels?▼

Use this Skill to generate a canonical verbal-system.md file containing voice principles, tone dimensions, and messaging architecture. Child skills for LinkedIn, website, social, PR, and video then inherit that file so every channel stays aligned.

What is the difference between voice and tone in brand copy?▼

Voice is the stable verbal character of the brand that stays recognizable across surfaces. Tone is the contextual expression of that voice, adjusted through dimensions like formality, warmth, urgency, and technical depth based on audience, risk, and situation.

How does the Skill handle unsupported marketing claims?▼

It classifies claims as safe-public, approval-required, internal-only, evidence-missing, or prohibited. Unsupported claims are removed, qualified, converted into goals or proposals, attributed to approved sources, or flagged for user confirmation before publishing.

Can I use this Skill for a one-off LinkedIn post without building the full system?▼

Yes, but only when explicitly requested as a one-off draft. By default the Skill creates or updates verbal-system.md first, then routes to the linkedin-post-system child skill so the post inherits approved voice, claims, and terminology.

What input files does the verbal language system need?▼

It prefers an existing verbal-system.md plus context.md, design.md, brand-architecture.md, source-register.md, and public-claim-rules.md. When context is missing or contradictory, it asks targeted questions rather than inventing brand strategy.

When should I not use this parent Skill directly?▼

Do not use it for surface-specific execution details like LinkedIn formatting or slide structure; those belong to child skills. Also avoid it when core brand facts such as purpose, audience, or offering are undefined, since it will not fabricate strategy from weak context.