ReplayAutonomous app testing for teams who ship at AI-speed
Promoted
localskills.sh
AI Skill & MCP server management for teams & enterprises
130 followers
AI Skill & MCP server management for teams & enterprises
130 followers
Create, share, and install reusable agent skills and rules for Cursor, Claude Code, Windsurf, and more. One install command, every tool.
Centralized skill and MCP management feels increasingly necessary for teams. Does localskills support signed provenance, version pinning, approval policies, and rapid rollback when a skill update causes unexpected behavior?
A versioning system for skills would be huge, something like pinning specific versions when installing so updates don't silently break workflows. Maybe a `localskills install owner/skill@1.2.0` syntax with a lockfile would make it way more reliable for team setups.
We publish a few dozen agent skills, so I live on the other side of this. The problem that hurts most isn't install, it's drift: the skill updates, and every agent that loaded the old copy keeps confidently doing the old thing. Does localskills pin versions per team, and can I see which version each agent actually has loaded? That audit view would be the feature that sells me.