Files
skills/commands/draft-nda.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
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]>
2026-09-15 01:27:26 -07:00

2.0 KiB

description, argument-hint, source
description argument-hint source
Draft a Non-Disclosure Agreement between two parties with jurisdiction-appropriate clauses <parties and context> phuryn/pm-skills

/draft-nda -- NDA Drafting

Draft a professional Non-Disclosure Agreement customized to your situation. Covers information types, jurisdiction, term, and clearly marks clauses that need legal review.

Invocation

/draft-nda Mutual NDA between our startup and a potential enterprise customer
/draft-nda One-way NDA for a freelance contractor accessing our codebase

Workflow

Step 1: Gather Context

Ask:

  • Who are the parties? (company names and roles)
  • Mutual or one-way NDA?
  • What information is being protected? (trade secrets, code, business data, customer data)
  • Jurisdiction? (state/country for governing law)
  • Duration? (how long should confidentiality last)
  • Any specific concerns? (non-compete, non-solicit, IP ownership)

Step 2: Draft the NDA

Apply the draft-nda skill:

Generate a complete NDA covering:

  • Parties and recitals
  • Definition of confidential information (with specific examples)
  • Obligations of the receiving party
  • Exclusions (public knowledge, independent development, etc.)
  • Term and survival
  • Return/destruction of materials
  • Remedies
  • Governing law and jurisdiction
  • Standard boilerplate (severability, entire agreement, amendments)

Step 3: Deliver

## Non-Disclosure Agreement

[Full NDA text with marked sections]

### Clauses Requiring Legal Review
| Clause | Why It Needs Review | Consideration |
|--------|-------------------|--------------|

### Plain-Language Summary
[What this NDA means in simple terms for non-lawyers]

Save as markdown. Offer to export as DOCX for signing.

Notes

  • This is a starting point — always recommend review by qualified legal counsel
  • Mark any clause that involves significant legal risk with a ⚠️ flag
  • Include plain-language annotations so non-lawyers understand what they're agreeing to
  • Mutual NDAs are generally preferred — they're fairer and faster to negotiate