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.8 KiB
3.8 KiB
description, argument-hint, source
| description | argument-hint | source |
|---|---|---|
| Map stakeholders on a Power × Interest grid and create a tailored communication plan | <project, initiative, or launch> | phuryn/pm-skills |
/stakeholder-map -- Stakeholder Mapping & Communication Plan
Identify all stakeholders for a project, map them by influence and interest, and generate a communication plan that ensures the right people get the right information at the right time.
Invocation
/stakeholder-map New analytics platform launch
/stakeholder-map Pricing model change affecting all customers
/stakeholder-map [upload a project brief or org chart]
Workflow
Step 1: Understand the Initiative
Ask:
- What is the project or initiative?
- What phase is it in? (planning, building, launching, post-launch)
- Who are the obvious stakeholders you already know about?
- Are there any politically sensitive dynamics to be aware of?
Step 2: Identify Stakeholders
Brainstorm stakeholders the user might not have considered:
- Internal: Engineering, Design, QA, Data, Legal, Finance, Marketing, Sales, Support, Leadership
- External: Customers, partners, vendors, regulators, board members
- Often missed: Adjacent teams, on-call engineers, customer success, documentation team
Step 3: Map to Power × Interest Grid
Apply the stakeholder-map skill:
Place each stakeholder in a quadrant:
HIGH INTEREST
│
KEEP SATISFIED │ MANAGE CLOSELY
(High Power, │ (High Power,
Low Interest) │ High Interest)
│
──────────────────────┼──────────────────────
│
MONITOR │ KEEP INFORMED
(Low Power, │ (Low Power,
Low Interest) │ High Interest)
│
LOW INTEREST
Step 4: Generate Communication Plan
## Stakeholder Map: [Initiative]
### Stakeholder Grid
| Stakeholder | Role | Power | Interest | Quadrant | Stance |
|------------|------|-------|----------|----------|--------|
### Communication Plan
#### Manage Closely (High Power, High Interest)
| Stakeholder | Channel | Frequency | Content | Owner |
|------------|---------|-----------|---------|-------|
#### Keep Satisfied (High Power, Low Interest)
| Stakeholder | Channel | Frequency | Content | Owner |
|------------|---------|-----------|---------|-------|
#### Keep Informed (Low Power, High Interest)
| Stakeholder | Channel | Frequency | Content | Owner |
|------------|---------|-----------|---------|-------|
#### Monitor (Low Power, Low Interest)
[Minimal communication — include in broad updates only]
### Potential Conflicts
[Where stakeholder interests may clash — with mitigation strategies]
### Escalation Path
[Who to go to when decisions are blocked]
### RACI Matrix
| Decision Area | Responsible | Accountable | Consulted | Informed |
|--------------|-------------|-------------|-----------|----------|
Save as markdown.
Step 5: Offer Next Steps
- "Want me to draft the first stakeholder update for the 'Manage Closely' group?"
- "Should I create a meeting prep brief for key stakeholder conversations?"
- "Want me to set up a communication cadence as a recurring checklist?"
Notes
- The "Manage Closely" quadrant is where PMs spend most of their political capital — get these relationships right
- "Stance" (supportive, neutral, resistant) helps prioritize where to invest relationship-building effort
- Don't forget downstream stakeholders: support, docs, and sales enablement teams are often surprised by launches
- Update the map as the project evolves — stakeholder interest shifts with project phase