Use Cases¶
SkillMeat is a local-first control plane for agentic artifacts — skills, commands, agents, MCP
servers, and workflow assets — across .claude, .codex, .gemini, and beyond. How you use it
depends on where you sit: working solo, standardizing a team, running a governed platform, or
sharing artifacts with others. Pick the page below that matches your situation.
Find Your Use Case¶
| Persona | Situation | Core Proof | Primary CTA |
|---|---|---|---|
| Individual Developer | You manage agent skills and configuration across one or more repos, on one or more agent platforms. | One CLI-driven flow — init → add → deploy — shipped and scriptable. |
Install SkillMeat |
| Team Lead / Architect | Your team needs a standardized, versioned "Golden Path" of artifacts instead of copy-pasted config folders. | Bundles/deployment sets plus three-scope diff comparison to see where deployed projects have drifted. | Read the docs |
| Enterprise Platform Owner | You need multi-tenant governance — RBAC, audit, and artifact provenance — for a controlled pilot. | PostgreSQL-backed multi-tenant storage, RBAC admin console, and real Ed25519 signed attestation. | See enterprise |
| Artifact Creator | You want to share a skill, command, or workflow bundle with your team or the community. | An authenticated publish flow with metadata, versioning, and lifecycle management. | Learn how to publish |
Looking for a Step-by-Step Walkthrough Instead?¶
This section describes why each persona reaches for SkillMeat and where to start. If you want a detailed, click-by-click walkthrough of a specific setup, see Scenarios — onboarding paths for new projects, existing-project migration, team/enterprise admin setup, and more.
Where to Go Next¶
- New to SkillMeat? Start with the Quickstart Guide.
- Want the full capability list? Browse User Guides.
- Want to see it before you install it? Check the Demos gallery.