localskills.sh icon

localskills.sh

localskills.sh helps teams create, share, and install reusable agent skills and rules across coding tools, with publishing, versioning, access control, SSO, analytics, and audit logs.

localskills.sh

Share agent skills across a team

localskills.sh is a platform for creating, sharing, and installing reusable agent skills and rules across a team. It is positioned for people using tools such as Cursor, Claude Code, Windsurf, and other supported coding agents.

The product centers on team distribution and control: skills can be published, versioned, and installed from a single command or API workflow, while organizations can apply roles, SSO, SCIM, folder access controls, analytics, and audit logs. The pricing page states that all features are included for teams under 10 seats, with larger teams moved to custom pricing.

Core features

Publish and version skills

Publish skills from the CLI, REST API, or web editor. The CLI can scan a project for rules files and turn them into a published skill in one step, with a new version created on every update.

Folder-based packaging and rollback

Package a folder as a single versioned artifact, with support for multi-file package skills, up to 500 files or 1 MB per version, and one-click rollback to earlier versions.

Install across eight tools

Install skills into Cursor, Claude Code, Windsurf, Cline, Copilot, Codex, OpenCode, and Aider using one CLI, with symlink, copy, or embedded section installs.

Roles and folder access control

Control access with four built-in roles, custom roles, and folder-level ACLs. The platform says permissions do not escalate beyond a member's role.

Enterprise identity management

Use SAML 2.0 SSO and SCIM 2.0 directory sync with group-to-team mapping, plus email-domain enforcement for organization sign-in.

Integrations, analytics, and auditability

Track installs by source, keep a 90-day audit log, mirror your skill tree to GitHub, and use API tokens or the MCP server for programmatic access.

Common use cases

  • Version-controlled team knowledge

    A team can publish a shared skill once, keep version history, and roll back if an update does not work as intended.

  • Cross-tool installation

    An organization can distribute the same skill set to developers using different AI coding tools without rewriting the workflow for each app.

  • Centralized access control

    Admins can restrict who can publish or view specific folders, while keeping access aligned to roles and team membership.

  • Enterprise identity setup

    Teams using SSO or directory sync can connect identity providers, map groups to teams, and enforce organization sign-in by email domain.

  • Automation and observability

    Engineering teams can install skills in CI/CD or automated workflows using API tokens or the MCP server, while tracking source-based install analytics.

Pros and Cons

Pros

  • Supports publishing from the CLI, REST API, or web editor.
  • Installs work across eight named tools from one CLI.
  • Includes team controls such as roles, folder ACLs, SAML SSO, and SCIM.
  • Tracks installs and retains audit logs for 90 days.
  • Free for teams under 10 seats with no feature gates on the listed platform features.

Cons

  • The public material does not provide a detailed comparison matrix for each supported tool or install strategy.
  • Security auditing is listed as coming soon rather than available now.
  • Teams with 10 or more seats need to contact the company for custom pricing instead of self-serve checkout.

FAQ

How do you publish a skill?

You create a workspace, then publish skills from the CLI, REST API, or web editor. The site says the CLI can scan your project for rules files and publish them in one step.

Which tools can install skills?

The site lists Cursor, Claude Code, Windsurf, Cline, Copilot, Codex, OpenCode, and Aider. It also says one CLI can install across those tools using symlink, copy, or embedded install strategies.

What counts as a seat?

Every member of your organization counts as a seat, including owners, admins, members, view-only users, and custom roles. SCIM-provisioned accounts also count.

Is the free tier limited?

No. The pricing page says the free plan includes all features for teams under 10 seats, including private skills, custom roles, folder ACLs, SAML SSO, SCIM provisioning, audit logs, the GitHub mirror, the MCP server, and the full REST API.

What happens when we reach 10 seats?

The pricing page says to contact the team once you reach 10 seats. They will set up per-seat pricing, onboarding, and terms, and the workspace keeps working while that is arranged.

Quick Facts

Category
Developer tool
Primary use
Create, share, and install agent skills and rules
Supported tools
Cursor, Claude Code, Windsurf, Cline, Copilot, Codex, OpenCode, Aider
Pricing shape
Free up to 9 seats; custom pricing for 10+ seats
Domain
localskills.sh
Public access
Public, private, and unlisted skills