aaron-he-zhu/aaron-marketing-skills
0 qualified needsNo qualified pattern yet
No current Issue clears the demand threshold.
Full project evidenceaaron-he-zhu/aaron-marketing-skills vs mvschwarz/openrig
Compare current project strength and the unmet needs people are actually discussing on GitHub. No paid placement influences this comparison.
mvschwarz/openrig has the stronger current discovery signal, driven by the score components shown below.
aaron-he-zhu/aaron-marketing-skills is categorized as Marketing; mvschwarz/openrig is categorized as Coding. Compare their product descriptions and source repositories before choosing.
| Signal | aaron-he-zhu/aaron-marketing-skills | mvschwarz/openrig |
|---|---|---|
| Radar Score | 80/100 | 95/100 |
| Adoption | 20/25 | 22/25 |
| Maintenance | 20/20 | 20/20 |
| Project quality | 20/20 | 20/20 |
| Agent relevance | 20/20 | 20/20 |
| Demand evidence | 0/10 | 10/10 |
| Observed momentum | 0/5 | 3/5 |
| GitHub stars | 3,012 | 8,147 |
| Category | Marketing | Coding |
| Qualified unmet needs | 0 | 3 |
| Leading problem patterns | No qualified pattern yet | Setup & configuration (2), Product Capability workflows (1) |
mvschwarz/openrig
3 qualified needsSetup & configuration (2), Product Capability workflows (1)
- Daemon event loop saturates at scale: per-seat tmux polling (transcripts, structural, identity) spawns ~300 processes/s; transcript config leaks into seat env15 comments · 0 reactions
- Windows Support13 comments · 0 reactions
- A seat's startup files are frozen as absolute paths at first launch, so added seats, rig changes and upgrades don't reach them12 comments · 0 reactions
aaron-he-zhu/aaron-marketing-skills
120 marketing skills as an AI marketing staff — plugin, portable skills, or an 8-bot team across 7 disciplines (narrative, SEO/GEO, social, email, paid, influencer, launch) on one contract, with 8 auditor gates: TALE · CORE-EEAT · CITE · ECHO · SEND · ROAS · STAR · RAMP.
Full analysismvschwarz/openrig
Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work.
Full analysisTest the need you understand best
A stronger repository is not automatically a stronger business. Open the leading GitHub need, speak to affected users and let behavioral evidence decide.
Transparent scoring
Adoption (25 points) uses stars and forks, maintenance (20) uses code activity, quality (20) checks license and metadata, relevance (20) checks agent focus, demand (10) uses open Issues, and momentum (5) uses star growth.