Offer Gravity Lab
by Bani Berisha
Transform messy product notes into rigorous positioning, message maps, and campaign briefs with an evidence-first logic.
- Turn unstructured customer interviews into a structured message hierarchy.
- Audit landing pages for unsupported claims and generic 'fluff' wording.
- Generate three distinct positioning angles for a new product launch.
$20
· or 100 creditsSecure checkout via Stripe
Included in download
- Turn unstructured customer interviews into a structured message hierarchy.
- Audit landing pages for unsupported claims and generic 'fluff' wording.
- terminal automation included
Sample input
Product: A support operations tool that reviews helpdesk tickets, tags churn-risk themes, and creates a weekly executive brief.
Buyer: Head of Support at a 50-300 person B2B SaaS company. Business notes include: managers read too many tickets; teams notice risk too late; the report should help support, product, and customer teams; alternatives are dashboards and manual tagging.
Draft: "AI-powered customer intelligence that transforms your business."
Task: Create the positioning decision header, evidence ledger, positioning kernel, message map, campaign brief, and validation backlog.
Sample output
Positioning Decision Header
Working angle: Ticket themes become an executive risk brief. Buyer: Head of Support at a growing B2B SaaS company. Trigger: Support leaders need to brief other teams before risk themes become visible in account metrics. Core job: Turn scattered ticket patterns into a weekly cross-functional decision brief. Evidence status: Based on supplied product notes only. Unknowns: integrations, customer quotes, accuracy method, and buyer willingness to pay.
Evidence Ledger
| Input | Label | Use | Limit | |---|---|---|---| | Reviews helpdesk tickets | USER_FACT | mechanism | detail needed before public claim | | Tags churn-risk themes | USER_CLAIM | risk angle | examples needed | | Weekly executive brief | USER_FACT | output focus | audience detail missing | | Dashboards/manual tagging | USER_FACT | alternatives | competitor list not supplied |
Positioning Kernel
Category: Support risk briefing tool. For: Heads of Support at B2B SaaS teams. Who struggle with: spotting repeated customer pain across ticket volume before it becomes an escalation. Unlike: dashboards that show counts or manual tagging that takes manager time. This helps by: turning ticket patterns into a weekly brief support, product, and customer teams can act on. Proof needed: sample ticket set, example brief, customer quote, accuracy method, and workflow timing. Not for: teams with no helpdesk data or users who need a full customer data platform.
Message Map
One-liner: Turn recurring support tickets into a weekly risk brief for the teams that can fix them. Homepage hero: See the support themes your next leadership meeting should act on. Pillars: repeated pain; team-ready briefs; clearer weekly view. Proof plan: add an anonymized ticket sample, generated brief, and customer workflow note before stronger public claims.
Campaign Brief
Audience: Support leaders at growing B2B SaaS companies. Situation: weekly reporting is manual and shallow for cross-functional action. Offer angle: "Send one ticket export. Get the support risk brief for your next leadership meeting." Asset set: landing hero, founder post, diagnostic checklist, short demo script. Call to action: "Send a sample ticket export and receive a briefing-format teardown." Handoff note: confirm privacy handling before using real tickets.
Validation Backlog
| Hypothesis | Smallest test | Signal | Falsifier | |---|---|---|---| | Leaders want briefing output more than another dashboard | show sample brief to 5 target buyers | requests for their own ticket example | they ask only for charts | | Manual tagging is the pain to replace | compare against current weekly process | buyer names time or consistency pain | tagging is already automated |
Risk and Repair Notes
Unsupported claims: risk detection, accuracy, and time savings. Safer rewrite: "Turn recurring support tickets into a weekly brief for cross-functional action."
Offer Gravity Lab
by Bani Berisha
Transform messy product notes into rigorous positioning, message maps, and campaign briefs with an evidence-first logic.
$20
· or 100 creditsSecure checkout via Stripe
Included in download
- Turn unstructured customer interviews into a structured message hierarchy.
- Audit landing pages for unsupported claims and generic 'fluff' wording.
- terminal automation included
- Instant install
Sample input
Product: A support operations tool that reviews helpdesk tickets, tags churn-risk themes, and creates a weekly executive brief.
Buyer: Head of Support at a 50-300 person B2B SaaS company. Business notes include: managers read too many tickets; teams notice risk too late; the report should help support, product, and customer teams; alternatives are dashboards and manual tagging.
Draft: "AI-powered customer intelligence that transforms your business."
Task: Create the positioning decision header, evidence ledger, positioning kernel, message map, campaign brief, and validation backlog.
Sample output
Positioning Decision Header
Working angle: Ticket themes become an executive risk brief. Buyer: Head of Support at a growing B2B SaaS company. Trigger: Support leaders need to brief other teams before risk themes become visible in account metrics. Core job: Turn scattered ticket patterns into a weekly cross-functional decision brief. Evidence status: Based on supplied product notes only. Unknowns: integrations, customer quotes, accuracy method, and buyer willingness to pay.
Evidence Ledger
| Input | Label | Use | Limit | |---|---|---|---| | Reviews helpdesk tickets | USER_FACT | mechanism | detail needed before public claim | | Tags churn-risk themes | USER_CLAIM | risk angle | examples needed | | Weekly executive brief | USER_FACT | output focus | audience detail missing | | Dashboards/manual tagging | USER_FACT | alternatives | competitor list not supplied |
Positioning Kernel
Category: Support risk briefing tool. For: Heads of Support at B2B SaaS teams. Who struggle with: spotting repeated customer pain across ticket volume before it becomes an escalation. Unlike: dashboards that show counts or manual tagging that takes manager time. This helps by: turning ticket patterns into a weekly brief support, product, and customer teams can act on. Proof needed: sample ticket set, example brief, customer quote, accuracy method, and workflow timing. Not for: teams with no helpdesk data or users who need a full customer data platform.
Message Map
One-liner: Turn recurring support tickets into a weekly risk brief for the teams that can fix them. Homepage hero: See the support themes your next leadership meeting should act on. Pillars: repeated pain; team-ready briefs; clearer weekly view. Proof plan: add an anonymized ticket sample, generated brief, and customer workflow note before stronger public claims.
Campaign Brief
Audience: Support leaders at growing B2B SaaS companies. Situation: weekly reporting is manual and shallow for cross-functional action. Offer angle: "Send one ticket export. Get the support risk brief for your next leadership meeting." Asset set: landing hero, founder post, diagnostic checklist, short demo script. Call to action: "Send a sample ticket export and receive a briefing-format teardown." Handoff note: confirm privacy handling before using real tickets.
Validation Backlog
| Hypothesis | Smallest test | Signal | Falsifier | |---|---|---|---| | Leaders want briefing output more than another dashboard | show sample brief to 5 target buyers | requests for their own ticket example | they ask only for charts | | Manual tagging is the pain to replace | compare against current weekly process | buyer names time or consistency pain | tagging is already automated |
Risk and Repair Notes
Unsupported claims: risk detection, accuracy, and time savings. Safer rewrite: "Turn recurring support tickets into a weekly brief for cross-functional action."
About This Skill
- List item
- List item
Use Cases
- Turn unstructured customer interviews into a structured message hierarchy.
- Audit landing pages for unsupported claims and generic 'fluff' wording.
- Generate three distinct positioning angles for a new product launch.
- Create a validation backlog to test marketing hypotheses before scaling.
- Draft a campaign brief including audience triggers and specific asset sets.
- Homepage repositioning
- Offer angle selection
- Campaign brief creation
- Agency client strategy
- Founder pitch refinement
Known Limitations
Does not prove demand, future performance, legal status, rights clearance, approval, or channel results. It relies on supplied material.
How to Install
mkdir -p ~/.claude/skills && curl -sL https://www.agensi.io/api/install/offer-gravity-lab -o /tmp/offer-gravity-lab.zip && unzip -o /tmp/offer-gravity-lab.zip -d ~/.claude/skills && rm /tmp/offer-gravity-lab.zipFree skills install directly. Paid skills require purchase - use the download button above after buying.
Reviews
No reviews yet - be the first to share your experience.
Only users who have downloaded or purchased this skill can leave a review.
Early access skill
Be the first to review this skill.
Only users who have downloaded or purchased this skill can leave a review.
Security Scanned
Passed automated security review
Permissions
File Scopes
Read access is only for bundled resources and user-supplied materials. No scripts, network, writes, or environment-variable access.
Tags
Built as a Universal SKILL.md package. Validate on the target agent before agent-specific claims.
Creator
Frequently Asked Questions
Learn More About AI Agent Skills
More Premium Skills
designing-hybrid-context-layers
Architects the right retrieval strategy for every query — teaching your agent when to use RAG, a knowledge graph, or a temporal index instead of defaulting to vector search for everything.
ai-automation-qa-pack
Professional QA & UAT documentation generator for AI automation agencies and complex agent deployments.
Bounty Security Pattern Master Library — 399 Vulnerability Patterns
A premium library of 399 vulnerability patterns and DeFi attack vectors for AI-driven bug hunting and security audits.
Multi-Agent Orchestration Master Library
Transform Claude Code into a coordinated multi-agent system. Battle-tested tmux orchestration patterns, YAML task queues, event-driven communication, and parallel worker management for 8+ agents.