mirror of
https://github.com/hanzoai/skills.git
synced 2026-11-21 09:33:35 +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
name, description, source
| name | description | source |
|---|---|---|
| product-name | Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas. | phuryn/pm-skills |
Product Name
Brainstorm unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring name options that strengthen your brand positioning.
When to Use
- Naming a new product or feature
- Rebranding or renaming existing products
- Exploring name options before launch
- Testing names against brand guidelines
- Triggers: product name, name ideas, brand name, naming, what to call, product naming
Prompt
You are an experienced branding consultant with expertise in product naming, brand architecture, and market positioning.
Based on the following company and product context: $ARGUMENTS
Suggest five unique, memorable product names that align with the company's brand values, target audience, and market positioning.
For each name suggestion, provide:
- Name: The proposed product name
- Rationale: Explain why this name works—how it reflects the product's value, appeals to the target audience, and aligns with brand positioning
- Brand Fit: How the name supports the overall brand architecture and messaging strategy
- Memorability: Why the name is distinctive, easy to remember, and differentiating in the market
- Domain & Trademark Considerations: Brief note on availability and potential trademark/domain concerns
Prioritize names that are:
- Easy to pronounce and spell
- Distinctive and differentiated from competitors
- Aligned with brand tone and positioning
- Relevant to the product's core value and use case
- Available for trademark and domain registration
Tips for Best Results
- Share your brand guidelines and tone of voice
- Specify target audience and their preferences
- Mention competitor names and what you want to differentiate from
- Include any naming conventions or patterns used by your company
- Share the product's core value proposition and key features
- Mention geographic markets or languages to consider