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.8 KiB
2.8 KiB
description, argument-hint, source
| description | argument-hint | source |
|---|---|---|
| Summarize a meeting transcript into structured notes with decisions, action items, and follow-ups | <transcript or meeting notes> | phuryn/pm-skills |
/meeting-notes -- Meeting Summary
Transform a raw meeting transcript or rough notes into clear, structured meeting minutes with decisions captured and action items assigned.
Invocation
/meeting-notes [paste transcript]
/meeting-notes [upload transcript file, audio summary, or notes]
Workflow
Step 1: Accept the Transcript
Accept in any format:
- Full transcript (from Otter, Fireflies, Google Meet, Zoom, etc.)
- Rough notes taken during the meeting
- Audio summary or meeting recap from a transcription tool
- Multiple inputs (e.g., transcript + the user's own notes)
If the input is sparse, work with what's available and flag gaps.
Step 2: Extract and Structure
Apply the summarize-meeting skill:
Parse the content to identify:
- Participants: Who was present (from introductions, speaker labels, or mentions)
- Topics discussed: Major agenda items or conversation threads
- Decisions made: Explicit agreements or conclusions reached
- Action items: Tasks assigned, with owner and deadline if mentioned
- Open questions: Unresolved items that need follow-up
- Key quotes: Important statements worth preserving verbatim
- Context: Meeting type, project, and background
Step 3: Generate Meeting Summary
## Meeting Summary
**Date**: [date if known]
**Participants**: [names/roles]
**Meeting type**: [standup, planning, review, 1:1, stakeholder, etc.]
**Topic**: [primary subject]
### Summary
[3-5 sentence overview of what was discussed and concluded]
### Key Decisions
1. **[Decision]** — [context and rationale]
2. ...
### Action Items
| # | Action | Owner | Deadline | Status |
|---|--------|-------|----------|--------|
### Discussion Highlights
**[Topic 1]**: [key points, different perspectives, conclusion]
**[Topic 2]**: [key points, different perspectives, conclusion]
### Open Questions
- [Question] — needs input from [person/team]
### Next Steps
- [What happens next]
- Next meeting: [if mentioned]
Save as markdown.
Step 4: Offer Follow-ups
- "Want me to email these notes to participants?"
- "Should I create tickets from the action items?"
- "Want me to draft a stakeholder update based on the decisions made?"
Notes
- Decisions are the most valuable output — make sure every decision is captured clearly
- Action items without owners are useless — if no owner was mentioned, flag it
- Keep the summary concise — people who weren't in the meeting should get the gist in 30 seconds
- If the transcript is very long (60+ min meeting), offer a TL;DR before the full summary
- Distinguish between "discussed" and "decided" — many topics are explored without reaching a conclusion