product-messaging

Generates landing page copy from ICP, problem, outcome, and differentiation inputs.

1|Updated Aug 17, 2026
One-click install
npx skills add https://github.com/NalinDalal/skillset --skill product-messaging-nalindalal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-messaging
Source: https://github.com/NalinDalal/skillset/tree/main/skills/ui/product-messaging
Command: npx skills add https://github.com/NalinDalal/skillset --skill product-messaging-nalindalal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Landing pages often ship with polished layouts but generic, forgettable copy like "AI-powered platform for modern teams." This Skill derives messaging from real product inputs and produces actual ready-to-paste copy instead of placeholder text or vague direction. ## Core Features & Use Cases - Messaging Derivation: Establishes the five inputs (product, ICP, painful problem, desired outcome, differentiator) before any copy is written, asking short direct questions when inputs are missing. - Section-by-Section Hierarchy: Maps a messaging hierarchy (value prop, proof, differentiation) to a landing page section sequence where each section answers one specific visitor question. - Real Copy Output: Delivers literal headlines, subheads, CTAs, and proof lines per section, with a hard avoid-list of generic phrases and a self-check against the "so what?" test. - Use Case: A founder says "write my landing page for a deploy tool for solo devs." The Skill asks about the ICP's specific pain, derives the value prop, and returns hero, problem, demo, and CTA copy ready for a UI skill to style. ## Quick Start Ask the agent to write the landing page copy for your product, describing what it does, who it is for, and what outcome it delivers.

Frequently Asked Questions about product-messaging

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

FAQPage Schema
How do I write landing page copy that converts?▼

Start by deriving five inputs: the product in one sentence, a narrow ICP, the specific painful problem, the desired outcome in the visitor's terms, and the differentiator. Then write a value prop as an outcome, not a feature list, and map copy to sections that each answer one visitor question.

What makes a good hero headline for a SaaS product?▼

A good hero headline states a concrete outcome and survives the "so what?" test. Formulas that hold up include outcome-first ("[Outcome] without [the usual pain]"), mechanism-first for technical audiences, and direct address naming the ICP explicitly.

Why does my landing page read as generic or AI-written?▼

Generic copy relies on vague confident phrases like "empowering," "seamless," or "the future of X" that are equally true of competitors. The fix is specificity: a concrete number, a named use case, or a real mechanism rather than a punchier adjective.

Can I use this with a UI or theme design skill?▼

Yes, it pairs with ui-theme-picker: this Skill decides what the page says while the theme skill decides how it looks. The output is copy mapped to sections, ready for a UI skill to lay out and style.

What if my product has no real proof or customer numbers yet?▼

Do not fabricate scale. The Skill recommends a placeholder proof strategy such as an early-access count, founder credibility, or one strong specific testimonial, and flags the proof as needing real data rather than presenting it as real.