asm vs OpenSpace
Scriptable skill manager for AI coding agents — install, search, dedupe-audit and security-scan skills across 19 providers, with --json/--yes on every command so agents and CI can drive it. — versus — HKUDS's skill lifecycle layer for agents: retrieve the right skill per task, evaluate which ones actually work from real outcomes, share across agents and teammates, evolve with every run.
Both manage agent skills across many hosts, split by ambition: asm is the scriptable package manager (install, search, dedupe, security-scan, --json for CI); OpenSpace adds the lifecycle — outcome evaluation and evolution — on top of retrieval.
| asm | OpenSpace | |
|---|---|---|
| Stars | 752 | 7.1k |
| Forks | 63 | 858 |
| Language | TypeScript | Python |
| License | MIT | MIT |
| Last activity | 5 days ago | today |
| Topics | coding, skills | skills |
| Curated connections | 6 | 2 |
asm — the curator's take
Pick it when the CLI consumer is a machine: every command is non-interactive and JSON-emitting, so your agent or CI pipeline can inventory, install, and dedupe skills without a human — that plus `asm audit` (finds duplicate/stale skills scattered across 19 providers' hidden dirs) is the differentiator. NOT the breadth play: ~4.3K curated skills vs skillkit's 400K firehose, and no format translation between agent dialects. Solo-maintainer project — fine for personal/team tooling, but if you need org-level reproducibility and governance, apm's manifest+policy model is the grown-up answer.
OpenSpace — the curator's take
The missing half of the skill ecosystem: everyone ships installers, almost nobody closes the loop on whether a skill WORKED. OpenSpace's bet is lifecycle — retrieval at task time, evaluation from real run outcomes, and evolution instead of repeat failures — across Claude Code, Codex, OpenClaw and friends. If your skill folder has become a junk drawer, this is the category to watch. NOT yet the standard: young v2, outcome-evaluation quality depends on how honestly your runs are scored, and the Feishu/WeChat-first community signals where the early adopters are. For plain install/audit needs, a simpler skill manager does less, more predictably.