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]>
3.2 KiB
3.2 KiB
name, description, source
| name | description | source |
|---|---|---|
| showcase-before-after | Before/After UI showcase — split-screen wipe reveal comparing two product states, UI redesigns, or workflow improvements. Routed from remotion-pro orchestrator. | melgarafael/growthOS |
Showcase: Before/After UI
Status: Stub — Full implementation in Wave 3
This showcase is planned for Wave 3 development. The stub reserves the skill slot, documents the specification, and displays the correct response to users who request it.
Overview
The Before/After UI showcase creates a compelling comparison video that reveals a transformation using a split-screen wipe effect. Shows two states side-by-side or sequentially — old vs new, manual vs automated, before vs after your product. Ideal for redesigns, productivity gains, and transformation narratives.
Best for: UI redesigns, workflow comparisons, productivity improvements, A/B test results, product transformations.
Components Used
| Component | Purpose |
|---|---|
SplitScreenWipe |
Animated wipe that reveals the "after" state from the "before" |
ScreenshotOverlay |
Layers and transitions between the two screen states |
BrowserFrame |
Optionally wraps both screens in browser frames |
AnimatedText |
Labels ("Before", "After"), stats, and result callouts |
Scene Flow
Hook (2-3s)
└── Problem statement or "before" label fades in
Before Screen (3-5s)
└── "Before" screenshot appears in BrowserFrame
AnimatedText labels it clearly
Wipe Reveal (2-3s)
└── SplitScreenWipe sweeps across (left-to-right or center-out)
Both states briefly visible simultaneously
After Screen (3-5s)
└── "After" state revealed
AnimatedText highlights key improvements
Result (2-3s)
└── Stat or outcome callout (e.g., "60% faster")
CTA (3-4s)
└── Branded CTA with product name or URL
Total Duration: 15–30 seconds
Required Config
# From video-profile.yaml or briefing
before:
screenshot: "assets/screenshots/before.png"
label: "Before"
caption: "Manual process — 2 hours"
after:
screenshot: "assets/screenshots/after.png"
label: "After"
caption: "With our tool — 5 minutes"
wipe_direction: left-to-right | right-to-left | center-out
result_stat: "95% time saved"
device_frame: browser | none
cta_text: "Start your free trial"
primary_color: "#7C3AED"
Stub Response
When a user requests this showcase, display:
⚡ BEFORE/AFTER UI SHOWCASE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
This showcase is coming in Wave 3 of a video pipeline.
What it will produce:
• Split-screen wipe reveal comparison
• Before and after screenshots with device frames
• Result stat callout (e.g., "95% faster")
• Branded CTA closing sequence
• Duration: 15–30 seconds
To be notified when this is ready, check the
changelog or watch the remotion/ directory for updates.
In the meantime, you can use the existing remotion-video skill
for general Remotion composition work.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━