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]>
9.7 KiB
description: Discover and activate relevant skills from the library argument-hint: [category|search-term] (optional)
Skills Discovery Assistant
You are helping the user discover and activate relevant skills from their skills library.
Your Task
User's Request: $ARGUMENTS
Follow these steps:
1. Read Skills Catalog
Read the master catalog:
cat skills/README.md
2. Detect Project Context
Analyze the current directory to understand the project:
# List files to detect project type
ls -la | head -30
# Check for language/framework indicators
ls *.{json,md,go,py,rs,swift,zig,toml,yaml,yml} 2>/dev/null | head -20
Technology Detection → Skill Mapping:
package.json→ frontend (React, Next.js, TypeScript)go.mod→ engineering (Go), may also need apirequirements.txt,pyproject.toml,uv.lock→ engineering (Python), ml if ML workCargo.toml→ engineering (Rust), wasm if WASMbuild.zig→ Zig skills at root level*.swift,*.xcodeproj→ mobile (iOS/Swift)Dockerfile,docker-compose.yml→ containers.beads/→ Beads workflow skills (root level)tests/,__tests__/→ testing- Database files → database
3. Analyze Conversation Context
Review the current conversation for:
- Technologies mentioned (frameworks, tools, databases)
- Problems discussed (performance, debugging, deployment)
- Explicit skill requests
- Work phase (planning, implementation, testing, deployment)
Map to skill keywords:
- "REST API" → api
- "GraphQL" → api
- "Postgres", "MongoDB", "Redis" → database
- "Docker", "Kubernetes" → containers
- "CI/CD", "GitHub Actions" → cicd
- "observability", "logging", "metrics" → observability
- "caching", "CDN" → caching
- "debugging", "GDB", "profiling" → debugging
- "build", "Make", "CMake" → build-systems-systems
- "ML", "model", "training" → ml
- "math", "linear algebra" → math
- "compiler", "parser", "AST" → plt
- "diagram", "flowchart", "Mermaid", "visualization" → diagrams
4. Provide Contextual Recommendations
Based on the argument provided:
If NO ARGUMENT (default view):
Display in this format:
━━━ SKILLS DISCOVERY ━━━
RECOMMENDED FOR THIS PROJECT:
→ [skill]
Keywords: [key topics]
cat skills/[skill]/SKILL.md
→ [skill]
Keywords: [key topics]
cat skills/[skill]/SKILL.md
SKILLS (61):
Frontend (8) | Database (8) | API (7) | Testing (6) | Diagrams (8) | ML (30)
Math (19) | Debugging (14) | Build Systems (8) | Caching (7) | Observability (8)
Containers (5) | CI/CD (4) | PLT (13) | Formal (10) | Cloud (13)
COMMANDS:
/skills api - View API skills
/skills frontend - View frontend skills
/skills postgres - Search for 'postgres'
/skills list - Show all categories
Recommend 2-4 skills that match:
- Detected technologies in the current directory
- Topics discussed in conversation
- Common workflows for the project type
If ARGUMENT = category name:
A) If the skill exists:
━━━ {CATEGORY} SKILLS (N total) ━━━
Keywords: [comma-separated keywords]
KEY SKILLS:
→ [skill-name] - [one-line description]
→ [skill-name] - [one-line description]
→ [skill-name] - [one-line description]
LOAD SKILL:
cat skills/{skill}/SKILL.md # what it covers, and the files beside it
LOAD FULL INDEX:
cat skills/{category}/INDEX.md # All skills with details
LOAD SPECIFIC SKILL:
cat skills/{category}/[skill-name].md # Individual skill
B) If searching root-level skills: Check for skills like:
skill-*.md(meta skills)beads-*.md(workflow skills)- Root-level technology skills
Display similarly but note they're at root level.
Example for /skills api:
━━━ API SKILLS (7 total) ━━━
Keywords: REST, GraphQL, authentication, authorization, rate limiting
KEY SKILLS:
→ rest-api-design - RESTful resource modeling, HTTP semantics
→ graphql-schema-design - GraphQL types, resolvers, N+1 prevention
→ api-authentication - JWT, OAuth 2.0, API keys, sessions
→ api-authorization - RBAC, ABAC, policy engines
→ api-rate-limiting - Token bucket, sliding window algorithms
→ api-versioning - API versioning, deprecation, compatibility
→ api-error-handling - RFC 7807, validation errors
LOAD:
cat skills/api/SKILL.md # Skill overview
cat skills/api/INDEX.md # Full details
cat skills/api/rest-api-design.md # Specific skill
If ARGUMENT = search term:
Search across:
- skill descriptions (*/SKILL.md)
- Category INDEX.md files
- skills/README.md catalog
- Root-level skill filenames
Display matching skill categories FIRST, then specific skills:
━━━ SEARCH: 'postgres' ━━━
SKILL:
→ database
Keywords: PostgreSQL, MongoDB, Redis, query optimization
cat skills/database/SKILL.md
MATCHING SKILLS:
→ postgres-query-optimization.md - Database/Performance
Debug slow queries, EXPLAIN plans, index design
cat skills/database/postgres-query-optimization.md
→ postgres-migrations.md - Database/Schema
Schema changes, zero-downtime deployments
cat skills/database/postgres-migrations.md
→ postgres-schema-design.md - Database/Design
Designing schemas, relationships, data types
cat skills/database/postgres-schema-design.md
RELATED SKILLS:
observability, caching, debugging
[Refine search: /skills postgres optimization]
[View category: /skills database]
If ARGUMENT = "list":
Show all 28 skill categories:
━━━ ALL SKILLS (61) ━━━
BACKEND & DATA:
api (7) - REST, GraphQL, auth, rate limiting
database (8) - Postgres, MongoDB, Redis, optimization
data (5) - ETL, streaming, batch processing
caching (7) - Redis, CDN, HTTP caching, invalidation
FRONTEND & MOBILE:
frontend (8) - React, Next.js, state management, a11y
mobile (4) - iOS, Swift, SwiftUI, concurrency
TESTING & DOCUMENTATION:
testing (6) - Unit, integration, e2e, TDD, coverage
diagrams (8) - Mermaid flowcharts, sequence, ER, architecture, Gantt
INFRASTRUCTURE:
containers (5) - Docker, Kubernetes, security
cicd (4) - GitHub Actions, pipelines
cloud (13) - Modal, AWS, GCP, serverless
infrastructure (6) - Terraform, IaC, Cloudflare Workers
observability (8) - Logging, metrics, tracing, alerts
debugging (14) - GDB, LLDB, profiling, memory leaks
build-systems-systems (8) - Make, CMake, Gradle, Maven, Bazel
deployment (6) - Netlify, Heroku, platforms
realtime (4) - WebSockets, SSE, pub/sub
SPECIALIZED:
ml (30) - Training, RAG, embeddings, evaluation
math (19) - Linear algebra, topology, category theory
plt (13) - Compilers, type systems, verification
formal (10) - SAT/SMT, Z3, Lean, theorem proving
wasm (4) - WebAssembly fundamentals, Rust to WASM
ebpf (4) - eBPF tracing, networking, security
ir (5) - LLVM IR, compiler optimizations
modal (2) - Modal functions, scheduling
engineering (4) - Code review, documentation, leadership
product (4) - Product strategy, roadmaps
collaboration (5) - Collaboration, code review, pair programming
AGENT SKILLS (Root):
elegant-design - UI/UX design, accessibility, design systems
anti-slop - Detect/eliminate AI-generated patterns
typed-holes-refactor - Systematic TDD-based refactoring
META SKILLS (Root):
skill-*.md - Discovery and creation
beads-*.md - Workflow and task management
[View category: /skills api]
[Search: /skills postgres]
5. Output Requirements
Format Guidelines:
- Use Unicode box drawing (━ ─ │) for section headers
- Use
→for list items - Keep output under 30 lines for default view
- Include clear, copy-paste commands
- Group related items logically
- Show only relevant categories/skills for the context
Tone:
- Direct and helpful
- Low noise, high signal
- Focus on what the user needs now
- Don't explain the system unless asked
DO NOT:
- Modify any skill files
- Create new skills
- Change README.md or INDEX files
- Make assumptions about skills you haven't read
- Display full skill contents (only summaries)
- Reference _INDEX.md (it's archived)
6. Graceful Fallbacks
If skills/README.md not found:
━━━ ERROR ━━━
Skills catalog not found at skills/README.md
Expected structure:
skills/
├── README.md (Master catalog)
├── <name>/SKILL.md (one skill, one directory)
└── {category}/INDEX.md (Category indexes)
Is your repository in a different location?
If no matches for search:
━━━ NO RESULTS: '$ARGUMENTS' ━━━
No skills found matching your search.
TRY:
→ Broader search term
→ View all skills: /skills list
→ Browse full catalog: cat skills/README.md
→ Check a category: /skills api
If empty project directory:
━━━ SKILLS DISCOVERY ━━━
No project files detected in current directory.
GENERAL-PURPOSE SKILLS:
→ collaboration - Collaboration, documentation, CodeTour walkthroughs
cat skills/collaboration/SKILL.md
ROOT-LEVEL SKILLS:
→ beads-workflow.md - Multi-session task management
→ skill-creation.md - Creating new atomic skills
→ skill-repo-discovery.md - Discover skills for repositories
[View all: /skills list]
[Browse catalog: cat skills/README.md]
Remember
- Read skills/README.md to get accurate information (NOT _INDEX.md - that's archived)
- Recommend skills first, then specific skills
- Match skills to project context when possible
- Keep output concise and actionable
- Never modify the skills library
- Provide clear, copy-paste commands
- Use Unicode box drawing for visual clarity
- The catalog has: 61 skills, one directory each