SkillMeat Quickstart Guide¶
Get started with SkillMeat in 5 minutes. This guide covers the essentials to create your first collection and deploy artifacts.
This guide uses zero-auth local mode — the default with no authentication required. For team or production deployments, see Authentication Setup and Server Setup after completing this quickstart.
Collection Scope¶
By default, SkillMeat operates in personal scope — all artifacts you create and manage belong to your personal collection. This is a security boundary, not a convenience feature.
If your instance has team or enterprise features enabled, you can switch scopes using:
# View your current scope
skillmeat collection scope show
# Switch to a team collection (if you have access)
skillmeat collection scope use team:<team-name>
# Note: Personal scope (the default) sends no extra parameters —
# it's zero behavior change for existing users
For most users, personal scope is all you need. A dedicated collection-scope guide does not exist yet.
Installation¶
Via pip (Recommended)¶
Via uv (Fast)¶
Via pipx¶
Recommended: Virtual Environment¶
Using a virtual environment avoids permission issues and keeps your system Python clean:
Add activation to your shell profile to persist across sessions:
From Source (Development)¶
First Steps¶
1. Initialize Your Collection¶
Create a default collection to store your Claude artifacts:
This creates ~/.skillmeat/collections/default/ with an empty collection.
Output:
2. Add Your First Artifact¶
Add a skill from GitHub using the add skill subcommand:
You'll be prompted with a security warning. Review and confirm to proceed.
Output:
3. View Your Collection¶
List all artifacts in your collection:
Output:
Artifacts (1)
┌────────┬────────┬────────┐
│ Name │ Type │ Origin │
├────────┼────────┼────────┤
│ canvas │ skill │ github │
└────────┴────────┴────────┘
4. Deploy to a Project¶
Deploy artifacts to your current project:
Output:
The artifact is now available in your project's .claude/ directory!
Common Workflows¶
Add from Local Path¶
Add a custom artifact you've created:
Add Multiple Artifacts¶
skillmeat add skill anthropics/skills/python
skillmeat add command user/repo/commands/review
skillmeat add agent user/repo/agents/code-reviewer
Note: Use the skill, command, and agent subcommands to specify artifact type.
Deploy Multiple Artifacts¶
Check for Updates¶
Create a Backup¶
Before making changes, create a snapshot:
Keeping Deployed Artifacts Current¶
Deploying copies an artifact from your collection into a project. That copy can drift — either because you changed the artifact in your collection, or because the project's copy was edited locally. Drift is detected, not silent: SkillMeat compares the deployed copy against your collection and reports the difference rather than overwriting either side.
You don't need to manage this during the quickstart — just know that if a deployed artifact and your collection disagree later, that's expected and there's a workflow for it:
- Syncing Changes — pull upstream changes and reconcile a drifted copy
- Sync Quick Reference — drift-detection states and merge strategies at a glance
Next Steps¶
- Server Setup Guide — Configure database, production deployment, and feature flags
- Authentication Setup Guide — Enable auth for teams or production (Clerk JWT, API keys, enterprise PAT)
- Commands Reference — All available CLI commands
- Examples — Real-world workflows
Configuration¶
Set GitHub Token (for private repos)¶
Set Default Collection¶
View All Settings¶
Directory Structure¶
After following this quickstart, you'll have:
~/.skillmeat/
├── config.toml # Global configuration
└── collections/
└── default/
├── collection.toml # Collection manifest
├── collection.lock # Version lock file
├── skills/
│ └── canvas/ # Installed skill
│ └── SKILL.md
├── commands/ # Command artifacts (if added)
└── agents/ # Agent artifacts (if added)
/path/to/your/project/
└── .claude/
├── .skillmeat-deployed.toml # Deployment tracking
└── skills/
└── canvas/ # Deployed skill
└── SKILL.md
Collections organize artifacts by type into separate directories (skills, commands, agents).
Getting Help¶
- View command help:
skillmeat --help - View specific command help:
skillmeat deploy --help - Check version:
skillmeat --version
Troubleshooting¶
Collection already exists¶
# List collections
skillmeat collection list
# Use existing collection
skillmeat collection use default
GitHub rate limits¶
Set a GitHub token to increase rate limits:
Artifact not found¶
Make sure you're using the correct GitHub path format:
Examples:
- anthropics/skills/canvas (latest)
- user/repo/skill@v1.0.0 (specific version)
- user/repo/path/to/skill@abc123 (specific commit)
Web Interface (Optional)¶
Manage your collection visually with the web UI.
Prerequisites: Node.js 18+ must be installed on the system.
# Install frontend dependencies (first time only)
WEB_DIR=$(python -c "from pathlib import Path; import skillmeat; print(Path(skillmeat.__file__).parent / 'web')")
cd "$WEB_DIR" && npx pnpm@8.15.0 install --frozen-lockfile && cd -
# Start both servers
skillmeat web dev
This starts both the FastAPI backend and Next.js frontend on:
- Frontend: http://localhost:3000
- Backend API: http://localhost:8080
For more options (custom ports, hosts, etc.), see the CLI Reference.
Other web commands:
skillmeat web build- Build for productionskillmeat web start- Start production serversskillmeat web doctor- Diagnose environment issues
What's Next?¶
You now know how to: - Initialize a collection - Add artifacts from GitHub and local paths - Deploy artifacts to projects - View and manage your collection - Create snapshots for backup - Access the web UI for visual management
Continue Learning¶
- Server Setup Guide — Local vs enterprise deployment, database configuration
- Authentication Setup Guide — Enable authentication for teams or production
- CLI Authentication Guide — Device code flow and PATs for CLI
- Commands Reference — Complete list of all CLI commands
- Web Interface Guide — Using the visual interface
- Integration Examples — Real-world workflows