asm vs n-skills
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 — Curated skill marketplace for AI coding agents on the universal SKILL.md/AGENTS.md format — write a skill once, install it into Claude Code, Codex, Copilot, Cursor and friends.
Both install and manage agent skills across providers; asm is the scriptable power-tool with audit/dedupe, n-skills the curated storefront on the universal format.
| asm | n-skills | |
|---|---|---|
| Stars | 730 | 1.0k |
| Forks | 61 | 105 |
| Language | TypeScript | TypeScript |
| License | MIT | Apache-2.0 |
| Last activity | 6 days ago | yesterday |
| Topics | coding, skills | skills |
| Curated connections | 5 | 4 |
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.
n-skills — the curator's take
The 'write once, run everywhere' bet applied to agent skills: one curated marketplace on the SKILL.md + AGENTS.md conventions, installed via openskills into whichever agent you drive. Smaller and more opinionated than the mega-registries — curation IS the pitch, every skill is hand-picked. NOT a discovery engine: if you want breadth across hundreds of sources, a package manager with security scanning covers more ground; and it's one person's taste with ~1k stars — check the skills you'd rely on exist before adopting the workflow.