autoskills vs skillkit
One command installs your project's AI skill stack: scans package.json/Gradle/configs, detects the tech stack, and pulls matching skills from an audited, hash-verified registry. — versus — Package manager for AI agent skills — install from 400K+ skills across 31 sources, auto-translate between 46 agents' incompatible formats, security-scan on install, sync to every agent at once.
Both end with skills installed in your agent; skillkit is the explicit package manager you drive, autoskills the zero-config detector that decides for you from a smaller audited registry.
| autoskills | skillkit | |
|---|---|---|
| Stars | 6.5k | 1.4k |
| Forks | 597 | 127 |
| Language | Ruby | TypeScript |
| License | NOASSERTION | Apache-2.0 |
| Last activity | 11 days ago | 1 months ago |
| Topics | skills | coding, skills |
| Curated connections | 3 | 11 |
autoskills — the curator's take
The zero-config on-ramp for agent skills: `npx autoskills` detects your stack and installs only the matching skills — and the security model is the standout, a maintainer-synced registry scanned for prompt injection with SHA-256 manifests and a lockfile, instead of live-downloading from random repos. NOT for hand-picking: you get the registry's opinion of what a Next.js or Go project needs, and the registry's coverage is web/mobile-stack-shaped — niche stacks fall through. No standard license file at the time of review; check before corporate adoption.
skillkit — the curator's take
Use it the moment skills must live on more than one agent — you write Claude SKILL.md, a teammate runs Cursor: author once, `skillkit sync` translates and deploys everywhere; the install-time security scan is a real feature now that skill marketplaces are a prompt-injection vector. NOT needed if you're all-in on a single agent — Claude Code's first-party plugin/marketplace flow is simpler and better supported. Format translation is lossy at the edges (agent-specific frontmatter, hooks, tool references), so verify ported skills actually trigger; and treat the optional mesh/messaging/REST extras as experiments, not infrastructure.