Markbase vs. a Git repository of skills: Keep skill distribution manageable across your team.
A versioned repository may be all you need when your team already maintains installation and update routines.
[ Which fits? ]
Start with the work you need to do.
When a Git repository of skills fits
Choose a repository when review and distribution through your existing Git workflow fit your team.
When Markbase fits
Choose Markbase when you want published sets, notify or auto sync, required sets, lint, rollback, and a fleet view alongside shared project memory.
[ Side by side ]
Markbase vs. a Git repository of skills, side by side.
| What matters | a Git repository of skills | Markbase |
|---|---|---|
| Operating the workflow | Clone or pull the repository and maintain each tool’s installation workflow. | Publish the set and use mb to track and sync it across machines. |
| Agent usage | Check the agent provider’s terms and billing for your setup. | Your existing agent subscription or API key pays for execution; Markbase does not host the agents. |
[ Pricing ]
Compare the whole operating cost.
Shared memory, team skills, and Dispatch are included on every Markbase plan. Your agent provider bills execution separately. Include your own runner infrastructure and the time spent maintaining the workflow in the comparison.
Markbase Free
$0a month
One person
3 workspaces, 200 documents each. 500 MB of storage.
Markbase Pro
$20a month
or $192 a year
Includes 5 seats
25 workspaces, 1,000 documents each. 25 GB of storage.
Markbase Team
$40a month
or $384 a year
Includes 10 seats, then $5 each
100 workspaces, 5,000 documents each. 250 GB of storage.
Markbase prices are USD before tax. Team’s extra seats are $5 each per month or $48 each per year, up to 100 members total. Enterprise and private deployments are quoted separately. Coding agents and model usage are not included. Full plans and limits
[ In practice ]
Try it on one real workflow.
The starting point
Choose a task your team already repeats and note how you distribute context, instructions, and follow-up work.
With a shared workspace
Choose Markbase when you want published sets, notify or auto sync, required sets, lint, rollback, and a fleet view alongside shared project memory.
Compare your actual setup. Capabilities vary by installer, marketplace, pipeline, and agent provider.
Read the skills guide[ Getting started ]
Try it with one piece of work.
- 01
Choose one skill set or agent job.
- 02
Set it up on one machine.
- 03
Review the result and the ongoing maintenance before expanding.
[ Questions ]
A few practical questions.
- Can we use both?
- Yes. Keep the repository, CI workflows, and tool integrations that already serve your team. Add shared memory, skills, or Dispatch where they reduce repeated coordination.
[ More comparisons ]