offer-signal-snapshot

name	offer-signal-snapshot
description	Use when a user wants to turn pasted, anonymized audience or client signal into one beginner-safe AI service product idea. The skill works from comments, DMs, emails, reviews, FAQs, sales notes, or client notes and should produce a signal table, offer options, a recommended offer sentence, proof asset, and what not to build yet.

Offer Signal Snapshot

Use this skill to help non-technical builders choose one AI service product idea from real signal.

Inputs To Request

Ask for missing inputs only when they materially change the offer recommendation:

• What the user does.
• Who they serve.
• 5-20 anonymized signals from comments, DMs, emails, reviews, FAQs, sales notes, or client conversations.
• Any known offer constraints, such as time, tools, niche, budget, or delivery boundaries.

If the user has no audience, ask for past client notes, competitor reviews, forum posts, or three real conversations instead.

Safety Rules

• Prefer pasted and anonymized text.
• Do not browse, open inboxes, inspect private accounts, post, reply, send, delete, label, publish, charge money, or change settings unless the user explicitly asks.
• Do not invent demand.
• Do not overstate confidence.
• Remove or ignore secrets, credentials, payment details, private links, and sensitive personal information.
• If the signal is weak, say so and explain what signal would improve the recommendation.
• Favor manually deliverable services before software, automation, or connected-account workflows.

Analysis Workflow

1. Summarize the signal in plain English.
2. Separate repeated signal from one-off noise.
3. Classify each useful item as pain, question, objection, desired outcome, exact wording, or proof clue.
4. Identify likely buyers and their current state.
5. Generate three AI service product ideas.
6. Pick the strongest first offer using these criteria:
   • specific buyer
   • painful current state
   • clear outcome
   • simple Codex-assisted mechanism
   • can be delivered manually first
   • can produce a visible proof asset
7. Flag what not to build yet.

Output Format

Return these sections:

1. Signal Summary
2. Signal Table
3. Top 3 Offer Ideas
4. Recommended First Offer
5. Week 1 Proof Sentence
6. First Proof Asset
7. What Not To Build Yet
8. Open Questions Before Selling

Use this proof sentence:

I help [buyer] get [outcome] using [AI/Codex mechanism].

For the signal table, use these columns:

• Source
• Audience wording
• Type
• Likely buyer
• Pain or desired outcome
• Possible offer
• Confidence

Repair Moves

If the output is too broad, narrow the buyer.

If the idea requires software, turn it into a manual service.

If there is no proof path, suggest a sample audit, before-after, workflow screenshot, demo, or mini case study.

If confidence is low, ask for more signal instead of pretending the idea is validated.