Files
skills/reference/voice/offers/_SCHEMA.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

2.9 KiB

Product/Offer Knowledge Schema

Template for documenting any product or offer. This file is consumed by the Sales Page System during the Discovery phase. If a matching offer file exists, the system loads it and asks the user for confirmation before proceeding.


How to Use

  1. Copy this template to {product-slug}.md in this directory
  2. Fill in all sections (the discovery skill will guide you interactively)
  3. The system will load this file automatically in future sales page builds

---
name: "{Product Name}"
slug: "{product-slug}"
version: 1
created: YYYY-MM-DD
updated: YYYY-MM-DD
status: draft | validated | active
---

# {Product Name}

## Promise
<!-- What transformation does this product deliver? One sentence. -->
**Core Promise:** 

<!-- What is the before/after? -->
**Before:** 
**After:** 

## Deliverables
<!-- What exactly does the person receive? Be specific. -->

### Core Deliverables
- [ ] 

### Bonus / Additional
- [ ] 

### Access Details
- **Format:** [course | community | software | service | hybrid]
- **Duration:** [lifetime | X months | subscription]
- **Platform:** 

## Benefits
<!-- What changes in their life? Think functional, emotional, social. -->

### Functional Benefits (what it does)
- 

### Emotional Benefits (how it makes them feel)
- 

### Social Benefits (how others perceive them)
- 

## Guarantees
<!-- What reduces perceived risk? -->

### Primary Guarantee
- **Type:** [money-back | trial | result-guarantee | satisfaction]
- **Duration:** 
- **Conditions:** 

### Secondary Trust Signals
- 

## Target Audience

### Primary Persona
- **Who:** 
- **Age Range:** 
- **Pain Level:** [1-10]
- **Awareness Level:** [unaware | problem-aware | solution-aware | product-aware | most-aware]
- **Budget Sensitivity:** [low | medium | high]

### Secondary Persona
- **Who:** 
- **Difference from primary:** 

## Objections
<!-- What stops people from buying? List the top objections and how to handle each. -->

| # | Objection | Response Strategy |
|---|-----------|-------------------|
| 1 | | |
| 2 | | |
| 3 | | |
| 4 | | |
| 5 | | |

## Competitors
<!-- Who/what are they comparing you to? -->

| Competitor | Their Promise | Our Advantage |
|-----------|---------------|---------------|
| | | |

## Pricing
- **Main Price:** 
- **Installments:** 
- **Anchor Price:** [optional — "was $X, now $Y"]
- **Payment Methods:** 

## USP (Unique Selling Proposition)
<!-- Why should they buy THIS, from YOU, RIGHT NOW? -->
**In one sentence:** 

## Social Proof Available
- [ ] Testimonials (count: )
- [ ] Case studies (count: )
- [ ] Media mentions
- [ ] Certifications
- [ ] User count / metrics
- [ ] Before/after results

## Voice & Tone for This Product
<!-- Override brand defaults if needed -->
- **Tone:** [same as brand | override: ...]
- **Formality:** [casual | professional | mix]
- **Urgency Level:** [low | medium | high]

## Notes
<!-- Anything else the sales page should know -->