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]>
5.9 KiB
5.9 KiB
Apple App Store — Official Specs & Guidelines
All data from developer.apple.com as of March 2026.
Character Limits
| Field | Limit | Indexed for Search? | Notes |
|---|---|---|---|
| App Name | 30 chars (min 2) | Yes | Must be unique; no trademarks, competitor names, pricing |
| Subtitle | 30 chars | Yes | No unverifiable claims |
| Keywords | 100 bytes | Yes (hidden) | Commas, no spaces between terms |
| Description | 4,000 chars | No | Plain text only, no HTML |
| Promotional Text | 170 chars | No (Apple confirmed) | Updatable without new version |
| What's New | 4,000 chars | No | Required for all versions after first |
| IAP Name | 35 chars | Yes | Appears in search |
| IAP Description | 55 chars | No | |
| In-App Event Name | 30 chars | Yes | Title case required |
| In-App Event Short Desc | 50 chars | Yes | Sentence case |
| In-App Event Long Desc | 120 chars | No | Sentence case |
Keywords field is 100 bytes, not 100 characters. Non-Latin scripts (Arabic, Chinese, Japanese, Korean) use 2-3 bytes per character, reducing effective keyword count significantly.
Screenshot Specs
| Device | Required? | Count | Dimensions (portrait) |
|---|---|---|---|
| 6.9" iPhone | Required | 1-10 | 1260 x 2736 |
| 13" iPad | Required | 1-10 | 2064 x 2752 |
| Mac | If applicable | 1-10 | Up to 2880 x 1800 (16:10) |
| Apple Watch | If applicable | 1-10 | Varies by model |
| Apple TV | If applicable | 1-10 | 1920 x 1080 or 3840 x 2160 |
| Apple Vision Pro | If applicable | 1-10 | 3840 x 2160 |
- Formats: JPEG, PNG
- Apple auto-scales from required base sizes to smaller devices
App Preview Video Specs
- Count: Up to 3 per app
- Duration: 15-30 seconds
- Max file size: 500 MB
- Codecs: H.264 (10-12 Mbps, up to 30fps) or ProRes 422 HQ
- Audio: Stereo, 256 kbps AAC or PCM, 44.1/48 kHz
- Formats: .mov, .m4v, .mp4
- Behavior: Autoplays muted on product page (iOS 11+)
Custom Product Pages (CPPs)
- Max: 70 additional pages (plus 1 default)
- Customizable: Screenshots, promotional text, app previews, deep links (iOS 18+)
- Keywords: Each keyword combo must be unique to a single CPP
- Review: Submitted to App Review independently of app updates
- Organic search: CPPs appear in organic search results since July 2025
- Performance: +2.5 percentage points higher conversion on average vs default
Product Page Optimization (A/B Testing)
- Treatments: Up to 3 vs original
- Testable: App icons, screenshots, app preview videos
- NOT testable: Title, subtitle, description, keywords
- Concurrent tests: 1 per app
- Max duration: 90 days
- Icon constraint: All icon variants must be in the published app binary
- Confidence: Apple recommends 90% threshold (Bayesian method)
- Cannot modify a test once started
In-App Events
- Max approved: 15 in App Store Connect at once
- Max published: 10 on App Store simultaneously
- Max duration: 31 days per event
- Pre-event promotion: Up to 14 days before start
- Badge types: Challenge, Competition, Live Event, Major Update, New Season, Premiere, Special Event
Event card image: 16:9, min 1920x1080, max 3840x2160 Event details image: 9:16, min 1080x1920, max 2160x3840
Not suitable: Repetitive daily tasks, price promotions without new content, general awareness campaigns.
Ratings & Reviews
- SKStoreReviewController: Max 3 prompts per 365-day period
- System controls display frequency (may show fewer than 3)
- Do not use custom buttons to request reviews
- Developers can respond to all reviews in App Store Connect
- Summary rating is territory-specific
Metadata Rejection Triggers (App Review Guidelines)
| Guideline | Rejection Trigger |
|---|---|
| 2.3.1 | Hidden features, misleading marketing, false pricing |
| 2.3.2 | Not disclosing IAPs in description/screenshots |
| 2.3.3 | Screenshots that don't show app in use (only splash/login) |
| 2.3.4 | Preview videos using non-app content |
| 2.3.5 | Wrong category selected |
| 2.3.7 | Keyword stuffing: trademarks, competitor names, pricing, irrelevant terms |
| 2.3.8 | Metadata not appropriate for all audiences (must be 4+ rated) |
| 2.3.10 | Other platform names/imagery (Android, etc.) in metadata |
| 2.3.12 | Generic What's New for significant changes |
| 2.3.13 | Inaccurate in-app event metadata |
Sources: developer.apple.com/app-store/product-page/, developer.apple.com/app-store/search/, developer.apple.com/app-store/review/guidelines/