Everything you need to create, share, and install agent skills.
Getting Started
Install the CLI, authenticate, and install your first skill in minutes.
Skills & Library
Skills
Types, text and package formats, visibility, versioning, supported platforms, and install methods.
Folders & Access Control
Organize skills into a folder tree and restrict folders to specific teams and members.
Personal Workspaces
Automatically provision a managed private skill workspace for every organization member.
Anonymous Sharing
Share a skill without an account: a pastebin for agent skills, keyed to a local Ed25519 identity.
Developer Tools
CLI Reference
Complete reference for the localskills CLI: install, publish, pull, uninstall, and list commands.
CLI JSON Output
Machine-readable CLI output: typed payloads, structured error codes, and strict non-interactive behavior with -o json.
MCP Server
Connect AI agents directly via the Model Context Protocol. Setup for Claude Code, claude.ai, Cursor, Codex CLI, Windsurf, VS Code, and more.
Managed MCP Servers
Manage your team's MCP servers centrally and install them into any tool with one CLI command.
Teams & Administration
Organizations & Teams
Create an organization, invite members, and group them into role-carrying teams.
Roles & Permissions
Built-in roles plus custom roles with granular permissions across skills, folders, and settings.
Analytics
Track skill downloads by source with privacy-preserving analytics and daily trend breakdowns.
Audit Log
User and organization audit logs with 90-day retention covering all platform actions.
Automation & API
GitHub Sync
Mirror your organization's skill library to a GitHub repository, folder structure included.
CI/CD & OIDC
Publish from GitHub Actions and GitLab CI with OIDC token exchange, no stored secrets.
API Tokens
Generate and manage API tokens for CI/CD pipelines, headless CLI auth, and programmatic access.
API Reference
REST API authentication, endpoints for skills, teams, SSO, SCIM, and CLI auth.
Enterprise & Security
SSO / SAML 2.0
Configure SAML 2.0 Single Sign-On with Okta, Azure AD, Google Workspace, and other identity providers.
SCIM 2.0
Automate user and group provisioning with SCIM 2.0 directory sync from your identity provider.
Security
Rate limiting, security headers, authentication security, and content limits.
Frequently Asked Questions
Install the localskills CLI globally via npm: npm i -g @localskills/cli
(or use pnpm, yarn, or bun: bun add -g @localskills/cli). Then verify
the installation with: localskills --version.
localskills supports 8 AI coding tools: Cursor, Claude Code, Codex CLI, Windsurf, Cline, GitHub Copilot, OpenCode, and Aider. Skills can be installed into any of these tools with a single CLI command.
Run localskills install <slug> to install a skill. The CLI will walk you
through platform selection, scope, and install method. You can skip
prompts with flags: localskills install my-skill --target cursor claude --project --symlink.
A skill provides agent instructions, capabilities, or workflows installed
into your tool’s skill directory. A rule provides governance guidelines or
coding standards. On some platforms like Claude Code, rules are placed in
a separate .claude/rules/ directory.
Run localskills publish [path] with a file or a whole skill folder
(published as a multi-file package). Omit the path to scan for
unpublished skills across all platform directories. You can set visibility
to public, private, or unlisted. Each update creates a new version you can
roll back.
Yes. Organize skills into folders and restrict a folder to specific teams or members with viewer, editor, or manager grants. Restricted folders are hidden from everyone else across the dashboard, API, CLI, and MCP server.
Yes. Configure an OIDC trust policy for your GitHub Actions or GitLab CI
pipeline, then exchange the pipeline’s identity token with
localskills login --oidc-token and publish with localskills push. No
long-lived secret is stored in CI.
Yes. localskills.sh supports SAML 2.0 SSO with any compliant identity provider (Okta, Azure AD, Google Workspace, etc.) and SCIM 2.0 for automated user and group provisioning. SSO configuration requires the organization owner role.