Files
skills/public/content-types.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.5 KiB

AI SEO by Content Type

Tactical guidance for optimizing specific content types for AI search citation. These tactics work for non-Google AI engines (ChatGPT, Claude, Perplexity, Copilot) and don't hurt Google AI Overviews / AI Mode.

For the cross-cutting strategy, see SKILL.md.


SaaS Product Pages

Goal: Get cited in "What is [category]?" and "Best [category]" queries.

Optimize:

  • Clear product description in first paragraph (what it does, who it's for)
  • Feature comparison tables (you vs. category, not just competitors)
  • Specific metrics ("processes 10,000 transactions/sec" not "blazing fast")
  • Customer count or social proof with numbers
  • Pricing transparency (AI cites pages with visible pricing) — add a /pricing.md file so AI agents can parse your plans without rendering your page (see "Machine-Readable Files" in the main skill)
  • FAQ section addressing common buyer questions

Blog Content

Goal: Get cited as an authoritative source on topics in your space.

Optimize:

  • One clear target query per post (match heading to query)
  • Definition in first paragraph for "What is" queries
  • Original data, research, or expert quotes
  • "Last updated" date visible
  • Author bio with relevant credentials
  • Internal links to related product/feature pages

Comparison / Alternative Pages

Goal: Get cited in "[X] vs [Y]" and "Best [X] alternatives" queries.

Optimize:

  • Structured comparison tables (not just prose)
  • Fair and balanced (AI penalizes obviously biased comparisons)
  • Specific criteria with ratings or scores
  • Updated pricing and feature data
  • Cite the competitors skill for building these pages

Documentation / Help Content

Goal: Get cited in "How to [X] with [your product]" queries.

Optimize:

  • Step-by-step format with numbered lists
  • Code examples where relevant
  • HowTo schema markup
  • Screenshots with descriptive alt text
  • Clear prerequisites and expected outcomes

Local Business / Ecom (Google emphasis)

Google's AI features pull from product feeds and business profiles for local + ecom queries. Optimize:

  • Merchant Center feeds kept current with accurate inventory, pricing, attributes
  • Google Business Profile complete with hours, services, photos, posts, Q&A answered
  • Reviews — recent + sufficient volume; respond to reviews to signal active management
  • Service area schema for local services
  • Business Agent (where available) for conversational customer engagement