Files
skills/public/positioning-variations.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

9.1 KiB
Raw Permalink Blame History

Positioning Variations Library

Directory audiences respond to different framings. Never copy-paste the same description everywhere — AI engines penalize duplicate content, and each directory type rewards a different opener.

Use this library to generate per-tier variants. Swap [product], [category], [competitors], [use-case], and [audience] with the real values.


Framework: Lead Sentence Varies by Tier

Tier Lead sentence pattern Why
Startup / launch "[Product] is the easiest way to [outcome] for [audience]." Founders scan for outcome clarity.
SaaS directory "[Product] is the [differentiator] alternative to [competitors]." Catches "[competitor] alternative" search intent.
AI directory "[Product] uses [AI capability] to [outcome]." TAAFT/Futurepedia audiences explicitly want AI.
Agent / MCP "[Product] is an MCP-native / agent-native [category]." Niche but high-intent. Ruling-out competitors.
No-code "[Product] lets you build [output] without code." Audience values speed, not technical depth.
Dev tool "[Product] is a [technical category] with [differentiator]." Devs want substance upfront.
B2B review "[Product] helps [audience] [measurable business outcome]." Reviewers want ROI language.

Template: Startup / Launch Directories

Target: Product Hunt, BetaList, Fazier, Uneed, DevHunt, Microlaunch, OpenHunts, LaunchVault, Firsto, PitchWall

Tagline (under 10 words):

The [differentiator] way to [outcome] for [audience].

Short description (60 chars):

[Outcome-focused one-liner with product name]

Long description (150 words):

[Product] is the easiest way to [outcome] for [audience]. Built for teams who [pain point], [product] removes [friction] by [how].

Unlike [competitor category], [product] [key differentiator 1] and [key differentiator 2]. You can [action 1] in under [timeframe], [action 2] without [limitation], and [action 3] that would normally require [cost or technical skill].

We built [product] because [founder origin story in one sentence]. It's now used by [audience examples] to [use case examples].

Try it free at [url]. No credit card, no setup.

Tags: [product category], [audience type], [use case 1], [use case 2], [differentiator], [tech]


Template: SaaS / Software Directories

Target: AlternativeTo, SaaSHub, G2, Capterra, GetApp, SourceForge, Slashdot, Startup Stash, F6S

Tagline:

The [differentiator] alternative to [top competitors].

Long description:

[Product] is a [differentiator] alternative to [competitor 1], [competitor 2], and [competitor 3] — built for [audience] who need [gap the competitors don't fill].

Where [competitor 1] [limitation 1] and [competitor 2] [limitation 2], [product] [solves]. You get [feature 1], [feature 2], and [feature 3] in a single workspace, at [pricing relative to competitors].

Key features: • [Feature 1] — [benefit] • [Feature 2] — [benefit] • [Feature 3] — [benefit] • [Feature 4] — [benefit] • [Integration 1], [Integration 2], [Integration 3] integrations

Trusted by [audience examples]. Start free at [url].

Tags: [competitor] alternative, [category], [audience], [differentiator], [top 3 features]


Template: AI Directories

Target: TAAFT, Futurepedia, Toolify, Future Tools, aitools.inc, AIStage, LogicBalls, SaasAITools

Tagline:

AI-powered [category] for [audience].

Long description:

[Product] is an AI-powered [category] that [core AI capability]. It uses [specific models / techniques] to [outcome] — so [audience] can [job to be done] in a fraction of the time.

What makes it AI-first: • [AI feature 1] — [what it does] using [model/approach] • [AI feature 2] — [what it does] • [AI feature 3] — [what it does] • [AI feature 4] — [what it does]

[Product] is built on [tech stack] and supports [models/providers]. Use cases: [use case 1], [use case 2], [use case 3], [use case 4].

Free tier available. No API keys required to start.

Tags: AI [category], [AI capability 1], [AI capability 2], AI for [audience], [use case 1], [use case 2], [LLM provider], [differentiator]


Template: Agent / MCP Registries

Target: Glama, APITracker, Linux Foundation MCP Registry, AI Agents List, AI Agent Store, AgentHunter

Tagline:

MCP-native [category] for AI agents.

Long description:

[Product] is an MCP-native [category] that lets AI agents [capability]. It exposes [MCP server capabilities] via the Model Context Protocol, so agents in Claude, ChatGPT, Cursor, and any MCP-compatible client can [actions].

MCP capabilities: • [Tool 1] — [what the agent can do] • [Tool 2] — [what the agent can do] • [Tool 3] — [what the agent can do] • [Resource 1] — [context surfaced] • [Prompt 1] — [pre-built prompt]

Authentication: [auth method]. Transports: stdio, HTTP, SSE. Security: [security posture].

Installation: [one-line install command]. Docs: [docs URL].

Tags: MCP, MCP server, AI agent, agent [category], Claude integration, Model Context Protocol, [domain], [auth type]


Template: No-Code Directories

Target: NoCodeFinder, No Code MBA Tools Directory, We Are No Code, NoCode.Tech

Tagline:

Build [output] without code.

Long description:

[Product] lets you build [output] without writing code. Drag, drop, or describe what you want and [product] handles the rest — [technical concept 1] and [technical concept 2] are automatic.

What you can build: • [Example project 1] — built in [timeframe] • [Example project 2] — built in [timeframe] • [Example project 3] — built in [timeframe]

No-code friendly features: • [Visual feature 1] • [Visual feature 2] • [AI-assisted feature] • [Pre-built templates]

Start free. No credit card. Templates included.

Tags: no code, no-code [category], visual [tool], drag and drop, [output type], [audience type]


Template: Dev / Technical Directories

Target: DevHunt, Stackshare, GitHub, Dev.to, Hacker News Show HN

Tagline:

[Technical category] with [technical differentiator].

Long description:

[Product] is a [technical category] built on [tech stack]. It solves [technical problem] by [technical approach].

Architecture: • [Component 1] — [tech used] • [Component 2] — [tech used] • [Component 3] — [tech used]

Why it's different: [technical insight or novel approach]. We chose [trade-off] because [reason].

Open source: [yes/no/partial]. Self-hostable: [yes/no]. License: [license].

API: [REST / GraphQL / MCP / gRPC]. SDKs: [languages]. Docs: [url].

Tags: [language], [framework], [category], open source, API, [tech stack component], [architecture approach]


Template: B2B Review Platforms

Target: G2, Capterra, TrustRadius, GetApp, Gartner Digital Markets, Crozdesk

Tagline:

[Business outcome] for [audience].

Long description:

[Product] helps [audience] [achieve measurable business outcome]. Teams use it to [use case 1], [use case 2], and [use case 3] — reducing [metric] by [percentage] and increasing [metric] by [percentage].

Key benefits: • [Business benefit 1] with [how measured] • [Business benefit 2] with [how measured] • [Business benefit 3] with [how measured]

Integrations: [enterprise integrations — HubSpot, Salesforce, Slack, etc.]

Security: [SOC 2 / GDPR / compliance posture]. Support: [support tier]. Pricing: [pricing range].

Trusted by [customer logos / company size]. Case studies at [url].

Tags: [business use case], [vertical], [audience role], [compliance], enterprise [category], [integration 1]


Category Tag Library

Pull 5–8 tags per submission from the relevant sections. Never repeat the exact same tag set across two directories in the same tier.

Universal

[category], [audience], [differentiator], [use case], AI, no-code, SaaS, [tech stack]

Industry

B2B, B2C, DTC, ecommerce, fintech, edtech, healthtech, martech, devtools, productivity, creator tools, agency tools

Job-to-be-done

lead generation, lead qualification, customer onboarding, product recommendation, sales enablement, marketing automation, survey, assessment, calculator, quiz, intake form

AI-specific

AI agent, LLM, generative AI, conversational AI, RAG, MCP, agent framework, AI form, AI quiz, AI assistant, AI automation

Technical

open source, self-hosted, API-first, webhook, Zapier, no-code, low-code, embeddable, white-label, multi-tenant, SSO, SAML


Do / Don't Quick Reference

DO:

  • Vary the opening sentence across tiers
  • Use real numbers and specific differentiators
  • Match tone to audience (technical for devs, business for G2, excited for PH)
  • Include a founder/origin angle in startup directories
  • Lead with the AI-first angle in AI directories

DON'T:

  • Copy-paste the same 150-word description everywhere
  • Use vague claims ("blazing fast", "game-changing")
  • Mention every feature — pick 3–5 per tier and rotate them
  • Lie about competitor features (AI engines cross-reference and de-rank)
  • Skip the tag list — it's how moderators route you to the right category