mirror of
https://github.com/hanzoai/skills.git
synced 2026-11-19 00:47:36 +00:00
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]>
2.2 KiB
2.2 KiB
Content Refresh Editing
Copy editing isn't just for new content. Existing pages and posts decay over time — outdated stats, stale examples, drifted brand voice, and missed SEO opportunities. A content refresh applies the same editing rigor to content that's already published.
When to Refresh
- Traffic declining on a page that used to perform well
- Stats or data are more than 12 months old
- Product has changed — features, pricing, or positioning no longer match
- Competitors updated their version of the same content
- AI search visibility matters — outdated content gets cited less (see ai-seo skill)
Content Refresh Checklist
- Freshness pass — Update all dates, stats, and examples. Replace "in 2024" with current data. Remove references to deprecated features or tools.
- Accuracy pass — Verify all claims are still true. Check that linked resources still exist. Confirm pricing and feature descriptions match current state.
- Voice pass — Does the tone match your current brand voice? Older content often reflects an earlier stage of the company.
- SEO pass — Has search intent shifted for this topic? Are there new keywords or questions to address? Add "Last updated: [date]" prominently.
- Proof pass — Can you add newer testimonials, case studies, or data points that didn't exist when this was first published?
- Structure pass — Add comparison tables, FAQ sections, or other scannable formats that make the content easier to consume.
Refresh vs. Rewrite
| Signal | Action |
|---|---|
| Core message still valid, details outdated | Refresh (update facts, stats, examples) |
| Brand voice has evolved significantly | Refresh + voice rewrite |
| Topic angle or audience has shifted | Full rewrite |
| Page structure doesn't match current search intent | Full rewrite |
| Just needs updated stats and links | Light refresh |
Refresh Cadence
- Pricing and product pages: Every quarter, or when pricing/features change
- High-traffic blog posts: Every 6 months
- Comparison and alternatives pages: Every 3-6 months (competitors change fast)
- Evergreen guides: Annually, unless traffic drops sooner
- Low-traffic pages: Only when traffic data suggests an opportunity