Documentation
Everything you need to create, share, and install agent skills.
Getting Started
Install the CLI, authenticate, and install your first skill in minutes.
CLI Reference
Complete reference for the localskills CLI — install, publish, pull, uninstall, and list commands.
MCP Server
Connect AI agents directly via the Model Context Protocol. Search, read, create, and publish skills from Claude Code, Cursor, and more.
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.
Anonymous Sharing
Share a skill without an account — a pastebin for agent skills, keyed to a local Ed25519 identity.
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.
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.
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.
API Tokens
Generate and manage API tokens for CI/CD pipelines, headless CLI auth, and programmatic access.
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.
API Reference
REST API authentication, endpoints for skills, teams, SSO, SCIM, and CLI auth.
Security
Rate limiting, security headers, authentication security, and content limits.
Frequently Asked Questions
How do I install the localskills CLI?
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.
What AI coding tools does localskills support?
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.
How do I install a skill with localskills?
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.
What is the difference between a skill and a rule?
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.
How do I publish a skill to localskills.sh?
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.
Can I restrict which team members see a skill?
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.
Can CI pipelines publish skills without stored secrets?
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.
Does localskills support SSO and SCIM?
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.