Messaging

Community

matteotitta

messaging

Builds a product messaging library from your positioning, your website and customer evidence: a description, the status quo and alternatives, pain points with their knock-on consequences, capabilities, functional, emotional and social benefits, branded features, the cost of doing nothing, common objections with responses, and core messaging blocks (tagline, elevator pitch, value props, proof, per-audience lines). Every claim sourced. Triggers: "product messaging", "messaging library", "messaging framework", "value props", "capabilities and benefits", "what are our differentiators in words". Run after /positioning. Not for choosing the position itself (use /positioning).

Overview

Publisher	matteotitta
Repository	`repo-structure-in-house`
Skill name	`messaging`
Stars	70
Forks	21
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by matteotitta on GitHub. Read the source before you install it.

Installation

Install the Messaging AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/matteotitta/repo-structure-in-house/tree/main/.claude/skills/messaging
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/matteotitta/repo-structure-in-house/tree/main/.claude/skills/messaging

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/matteotitta/repo-structure-in-house.git /tmp/repo-structure-in-house
mkdir -p .claude/skills
cp -r /tmp/repo-structure-in-house/.claude/skills/messaging .claude/skills/messaging

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Messaging in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Messaging on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Messaging is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Messaging

Turn the position into the words people will actually use: on the website, in sales calls, in emails and ads. The library links each pain to a capability, each capability to a benefit, and each benefit to proof, so any writer can pull a line and know it holds up.

When to use it

Right after /positioning is agreed.
Before rewriting the website, a sales deck or a launch.
When sales, marketing and product describe the product three different ways.

Don't use it to choose the position (/positioning), or for a single-feature question you can answer directly.

Inputs

Required: the website URL and the exact product name. Confirm the name if it's ambiguous.

Recommended: read these first if they exist:

context/positioning/, the primary input, which frames everything
context/icp/ for pains and voice of customer
context/competitors/ for the status quo and contrasts
context/win-loss/ for real objections
context/brand/ for tone of voice

Also useful: internal docs and customer quotes. If positioning is missing, say so and offer /positioning first.

Paths. Write to context/messaging/MMYY-messaging.md. Agency or consultant? Swap context/ for clients/<client>/context/ throughout.

Tools. Page fetching for the site; web search for reviews, testimonials and comparison pages. Exa or Firecrawl if you have them.

Steps

Validate inputs and load the upstream context.
Research. Fetch at least five core pages (home, features, pricing, customers, about) with URLs and dates. Search reviews and testimonials. Record branded feature names exactly as the company writes them.
Extract the ten components, in order:
1. Description. What it is, in one or two sentences, using the positioning.
2. Status quo and alternatives. Doing it by hand, plus at least one named alternative.
3. Pain points. Each with a consequence chain: the first-order problem, what it causes, what that costs the business.
4. Capabilities. What the product does about each pain.
5. Functional benefits. The outcome, each backed by a verbatim customer quote or marked "not available".
6. Emotional and social benefits. Two of each: how the buyer feels, and how they look to their boss and team.
7. Features. The branded names that deliver each capability.
8. Cost of inaction. What not acting costs per week or month, in numbers where you can.
9. Objections. 3 to 5, each with its root cause and a response that acknowledges, reframes and gives evidence.
10. Core messaging blocks. A tagline of 7 words or fewer, a one-sentence elevator pitch, a 3-bullet value prop, a lead proof point, and one line per audience segment.
Link it up. Every pain points to a capability, every capability to a feature and a benefit.
Verify. Check each claim against its source. Quotes are verbatim. Tag confidence [VERIFIED], [INFERRED], [ESTIMATED] or [UNAVAILABLE]. For a client-facing library, aim for at least 60% verified and no more than 10% estimated.
Write the data gaps and how to fill each one.
Hand off to /funnel-strategy, and to any copy work.

Output shape

Title it # Product messaging library: [Product]. Open with a TLDR and one block of open questions. Then the ten components in order, a data gaps section, and a source list with URLs and access dates.

What good looks like

All ten components present, or marked "not available" with a reason.
No pain point stops at the first-order problem.
The cost of inaction has a number, not an adjective.
The tagline and pitch match the agreed position. If they don't, flag it rather than drifting.
A seller could answer the top three objections using only this file.

Mistakes to avoid

Feature lists dressed up as benefits.
Invented customer quotes or made-up metrics.
Messaging that contradicts the positioning because a line sounded better.
Buzzwords where a plain verb would do.
Repeating the same caveat in every component. Say it once.

Chain

Part of the free five-skill chain: /icp-research → /competitor-research → /tov-guidelines → /positioning → messaging. The other six context skills (company context, win-loss, founder POV, brand kit, funnel and goals) are in the paid context plugin ($19.99, link in the README).

Frequently asked questions

What does the Messaging AI skill do?

Why use Messaging on TypingMind?

Because you install it once and use it with any model. Messaging is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Messaging in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/matteotitta/repo-structure-in-house/tree/main/.claude/skills/messaging. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Messaging?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Messaging?

As many as you like. As long as a model supports skills, you can use Messaging with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Messaging AI skill free?

Yes. It is published on GitHub by matteotitta under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Last30days

nexu-io

OrganizationPopular

Recent community and social trend research over the last 30 days. Use when the brief asks what people are saying now, recent sentiment, community reactions, social proof, launch reaction, trend scan,…

Swarm Advanced

Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows

Dcf Valuation

Discounted cash flow valuation and intrinsic value analysis for public companies. Use when the brief asks for DCF, fair value, intrinsic value, price target, undervalued or overvalued analysis, or…

Magazine Web Ppt

For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query "annual-marketing-plan", with GTM strategy lead judgment,…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Messaging

When to use it

Inputs

Steps

Output shape

What good looks like

Mistakes to avoid

Chain

Frequently asked questions

Related AI Skills

Set up your own AI workspace now