Claude Skill Manager
a14a-org/claudeskill-manager
Sincronize skills do Claude entre dispositivos com criptografia ponta-a-ponta
Ver no GitHubGerenciador de skills do Claude com sincronização entre dispositivos usando criptografia de conhecimento-zero. Permite compartilhar skills com times, fazer self-hosting e oferece CLI simples para gerenciar suas automações e extensões do Claude.
Instalação
npx convez-ai a14a-org/claudeskill-manager1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Sincronizar skills personalizadas do Claude entre múltiplos computadores
- Compartilhar automações e extensões com equipes mantendo privacidade
- Fazer self-hosting de um servidor próprio para controle total dos dados
Veredito

Solução sólida para quem trabalha com múltiplos skills do Claude e precisa sincronizá-los com segurança. A arquitetura de criptografia zero-knowledge é robusta; o suporte a self-hosting agrega valor real para usuários com requisitos de privacidade rígidos.
README
A tradução para o português deste README ainda está na fila.
Claude Skill Sync
Sync your Claude Code skills across devices with zero-knowledge encryption.
Features
- Zero-knowledge encryption - Your skills are encrypted client-side. The server never sees your content.
- Cross-device sync - Access your skills from any device
- Team sharing - Share encrypted skills with colleagues using per-member key envelopes
- Self-host option - Run your own server for complete control
- Simple CLI - Easy to use command-line interface
Quick Start
Using the CLI
# Install globally
npm install -g @claudeskill/cli
# Run setup
claudeskill
# Or try without installing
npx @claudeskill/cli
CLI Commands
claudeskill # Interactive menu (recommended)
claudeskill status # Show sync status
claudeskill list # List all skills
claudeskill list --tree # Show dependency graph
claudeskill push # Push local skills to cloud
claudeskill pull # Pull skills from cloud
claudeskill login # Login to existing account
claudeskill logout # Logout and clear credentials
claudeskill team list # List your teams
claudeskill team create <name> # Create a team workspace
claudeskill --help # Show all commands
Development Setup
Prerequisites
- Node.js 20.6+ (for server, uses --env-file flag)
- Node.js 18+ (for CLI only)
- Yarn
Install Dependencies
yarn install
Build All Packages
yarn build
Run in Development
# Terminal 1: Start the server
cp .env.example .env
# Edit .env with your settings
yarn dev:server
# Terminal 2: Run the CLI
yarn dev:cli
Project Structure
claudeskill/
├── packages/
│ ├── core/ # Shared encryption & skill parsing
│ ├── cli/ # Command-line interface
│ └── server/ # API server
├── .env.example # Environment variables template
├── docker-compose.yaml # Self-hosting setup
└── packages/server/drizzle/prod/20260311_team_share_incremental.sql
Self-Hosting
With Docker
# Copy and configure environment
cp .env.example .env
# Edit .env - set JWT_SECRET and optionally RESEND_API_KEY
# Start the server
docker compose up -d
Manual Setup
# Build
yarn install
yarn build
# Configure
cp .env.example .env
# Edit .env with your settings
# Run
node packages/server/dist/index.js
Environment Variables
| Variable | Required | Description |
|---|---|---|
PORT | No | Server port (default: 3001) |
DATABASE_URL | Yes | PostgreSQL connection string |
ENABLE_TEAM_SHARING | No | Exposes /teams when set to true |
JWT_SECRET | Yes | Secret for JWT signing. Generate with node -e "console.log(require('crypto').randomBytes(32).toString('hex'))" |
RESEND_API_KEY | No | Resend API key for OTP emails. Leave empty in dev (codes logged to console) |
FROM_EMAIL | No | From address for emails (default: noreply@claudeskill.io) |
ADMIN_EMAILS | No | Comma-separated list of admin emails for reviewing public skills |
Production Rollout
For an already-live server, use the manual incremental migration instead of the generated Drizzle baseline:
psql "$DATABASE_URL" -f packages/server/drizzle/prod/20260311_team_share_incremental.sql
Recommended order:
- Back up production Postgres.
- Apply
packages/server/drizzle/prod/20260311_team_share_incremental.sql. - Deploy the server with
ENABLE_TEAM_SHARING=false. - Verify existing personal sync still works.
- Redeploy with
ENABLE_TEAM_SHARING=true. - Smoke test team create, invite, accept, key distribution, and member removal.
- Publish the CLI update after that.
How It Works
Encryption
- You create a passphrase (never sent to server)
- A master key is generated and encrypted with your passphrase
- Your skills are encrypted with the master key using AES-256-GCM
- Only encrypted blobs are stored on the server
Authentication
- Enter your email
- Receive a 6-digit OTP code
- Verify the code to get access tokens
- No passwords stored - just email + encryption passphrase
Recovery
- A recovery key (8 words) is generated during setup
- Store it safely - it's the only way to recover if you forget your passphrase
- We cannot recover your data without it
API Endpoints
Authentication
POST /auth/otp/request Request OTP code
POST /auth/otp/verify Verify OTP and get tokens
POST /auth/refresh Refresh access token
POST /auth/logout Invalidate refresh token
Blobs (Encrypted Skills)
GET /blobs List all blobs
GET /blobs/:id Get a blob
POST /blobs Create a blob
PUT /blobs/:id Update a blob
DELETE /blobs/:id Delete a blob
Skills (Versioned)
GET /skills List all skills
GET /skills/:skillKey Get current version of a skill
POST /skills/:skillKey/versions Push a new version
GET /skills/:skillKey/versions Get version history
DELETE /skills/:skillKey Delete skill and all versions
Public Skills
Share skills publicly with the community (content is stored unencrypted).
# Public endpoints (no auth required)
GET /public/skills List approved public skills
GET /public/skills/:slug Get a public skill by slug
# Authenticated endpoints
POST /skills/:key/publish Submit skill for review
GET /skills/public List your public skills (all statuses)
DELETE /skills/public/:id Unpublish a skill
Admin (Review Workflow)
Admin users (configured via ADMIN_EMAILS env var) can approve/reject submissions.
GET /admin/stats Get pending/approved counts
GET /admin/pending List skills pending review
GET /admin/pending/:id Get single pending skill
POST /admin/skills/:id/approve Approve a skill
POST /admin/skills/:id/reject Reject with reason
Account
GET /account Get account info
GET /account/salt Get salt for key derivation
PUT /account/salt Set salt (first time)
GET /account/recovery Get recovery blob
PUT /account/recovery Set recovery blob
DELETE /account Delete account and all data
Public Skills
Share your skills with the community through our public skills directory.
How It Works
- Publish: Users submit skills for review via the dashboard or API
- Review: Admins review submissions for quality and security
- Approve/Reject: Approved skills appear in the public directory
- Install: Anyone can install public skills via the CLI
Publishing Flow
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ User clicks │ │ Passphrase │ │ Decrypt skill │
│ "Publish" │ ──▶ │ Modal opens │ ──▶ │ locally in │
│ │ │ │ │ browser │
└─────────────────┘ └─────────────────┘ └────────┬────────┘
│
▼
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ Shows in │ │ Admin reviews │ │ Send PLAIN │
│ public dir │ ◀── │ & approves │ ◀── │ content to API │
│ (if approved) │ │ │ │ (status=pending)│
└─────────────────┘ └─────────────────┘ └─────────────────┘
Important Notes
- Public skills are NOT encrypted - content is stored in plaintext
- Users must explicitly choose to publish (requires passphrase entry)
- All submissions go through manual review before becoming visible
- Authors can unpublish their skills at any time
Security
- All encryption happens client-side using AES-256-GCM
- Key derivation uses Argon2id (memory-hard, resistant to GPU attacks)
- Server only stores encrypted blobs - zero knowledge of content
- OTP codes expire after 10 minutes
- Access tokens expire after 1 hour
- Refresh tokens expire after 30 days
License
MIT