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.5 KiB
2.5 KiB
description, argument-hint, source
| description | argument-hint | source |
|---|---|---|
| Tailor a PM resume to a specific job description — keyword alignment, experience reframing, and strategic optimization | <resume> + <job description> | phuryn/pm-skills |
/tailor-resume -- Resume-to-JD Optimization
Take your resume and a target job description, then strategically align your experience to maximize interview chances. Keyword optimization, bullet point rewriting, and gap analysis.
Invocation
/tailor-resume [upload resume] Here's the JD: [paste job description]
/tailor-resume [upload both resume and JD as files]
Workflow
Step 1: Accept Both Documents
Need two inputs:
- The resume (text, PDF, or DOCX)
- The target job description (text, URL, or file)
If only one is provided, ask for the other.
Step 2: Analyze the Job Description
Extract:
- Required qualifications and skills
- Preferred qualifications
- Key responsibilities
- Industry and domain signals
- Seniority level indicators
- Cultural and team signals
Step 3: Tailor the Resume
Apply the review-resume skill:
- Keyword alignment: Map JD keywords to resume content, add missing keywords naturally
- Bullet point rewriting: Reframe experience to emphasize JD-relevant accomplishments using XYZ+S formula
- Section reordering: Prioritize the most relevant experience
- Summary/objective: Rewrite to directly address the role
- Skills section: Align with JD requirements
Step 4: Generate Tailored Resume + Analysis
## Resume Tailoring: [Job Title] at [Company]
### Alignment Score: [X/10]
### Keyword Gap Analysis
| JD Keyword | In Resume? | Recommendation |
|-----------|-----------|---------------|
### Changes Made
1. **[Section]**: [what changed and why]
2. ...
### Tailored Resume
[Full rewritten resume text]
### Gap Analysis
**Strong matches**: [where your experience directly aligns]
**Reframed matches**: [where experience was repositioned to fit]
**Gaps**: [JD requirements you don't clearly address — with suggestions]
### Cover Letter Talking Points
[3-4 points to emphasize in a cover letter that bridge remaining gaps]
Save tailored resume as markdown.
Notes
- Never fabricate experience — reframe truthfully, don't invent
- The summary/objective is the highest-ROI section to customize per application
- Match the JD's language exactly where possible (if they say "cross-functional," use "cross-functional")
- For senior roles, emphasize scale and strategic impact; for IC roles, emphasize hands-on execution