SkillMeat for Individual Developers¶

Is this you?¶

You maintain skills, commands, agents, and configuration for one or more coding agents — Claude Code, Codex, Gemini, or a mix — across one or more repos. Every new project means deciding which artifacts to bring over and copy-pasting .claude/, .codex/, or .gemini/ folders between them. There's no version history, no easy way to pull in an update, and no single place to see what you actually have.

What you get¶

One CLI-driven workflow takes you from nothing to a working artifact in a project:

skillmeat init                       # create your personal collection
skillmeat add skill some/artifact    # add from GitHub or local disk
skillmeat deploy some-artifact       # deploy into a project's agent-config folder

This is the git-like command surface SkillMeat ships today — init, add, list, search, deploy, sync, scaffold, template — with atomic filesystem operations and validation before anything is installed. Every artifact you add is versioned and tracked in your collection, so the next project just reuses what you already built instead of starting from a blank folder.

Your collection also covers all 21 shipped artifact types across 4 tiers — skills, commands, agents, hooks, MCP servers, rules, workflows, and more — with the same add/deploy/sync flow for every one of them.

See it work¶

Terminal capture — coming soon

A recorded skillmeat init → add → deploy walkthrough is planned for this page as part of the site's media rollout. In the meantime, the CLI demos below show the same flow today.

Real, recorded demos of this flow:

Collection Initialization (CLI) — list, add, and verify artifacts from the terminal.
Deploy Artifacts (CLI) — deploy from your collection into a project's agent-config folder.
Import from GitHub (CLI) — add artifacts directly from GitHub repos with version pins.

Get started¶

Install SkillMeat

The Quickstart Guide covers installation (pip, uv, or a virtual environment), your first skillmeat init, and deploying your first artifact — about 15 minutes end to end.

Go deeper¶

New Project Developer Walkthrough — the full, step-by-step version of this flow, prerequisites through verification.
Existing Project Migrant Walkthrough — already have a .claude/ (or .codex//.gemini/) directory full of artifacts? Scan and import them instead of starting fresh.
Adding Artifacts Guide — every way to add artifacts: marketplace, GitHub, or local files.
Deploying Artifacts Guide — deployment options, including Git PR workflows.
CLI Command Reference — the full command surface.

Next: growing beyond solo use¶

Once you're sharing artifacts with teammates, see SkillMeat for Team Leads / Architects.