One markdown folder for your team and its agents
# Add to your Claude Code skills
git clone https://github.com/Markbase-Team/MarkbaseGuides for using ai agents skills like Markbase.
See how Markbase compares with popular alternatives.
Markbase is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Markbase-Team. One markdown folder for your team and its agents. It has 66 GitHub stars.
Markbase's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/Markbase-Team/Markbase" and add it to your Claude Code skills directory (see the Installation section above).
Markbase is primarily written in TypeScript. It is open-source under Markbase-Team on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh Markbase against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM lists this project for discovery and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Markbase is a folder of markdown that syncs. You and your team edit the files
in the folder, in the browser, in the desktop app, or through the agents you
already run, and everyone reads one version. Comments, history and sharing sit
on top of plain .md files, so nothing is locked in: the folder is yours, and
it keeps working without us.
A vault is a set of documents in the cloud and, on each machine that mounts it, one folder that mirrors them. A background sync keeps the two in step, both ways, and merges concurrent edits instead of overwriting them — git without push and pull.
npx @markbase/cli mcp install connects
Claude Desktop, Claude Code, Codex and Cursor, and so does Settings in the
desktop app — plus an HTTP API and a skill
(skills/markbase).The same build serves the hosted app and every self-hosted instance. An instance that is not markbase.so is invite-only: the first account created on it is the admin, and teammates join through a link from Settings.
apps/web/ The web app and the HTTP API (Next.js). What markbase.so and a
self-hosted instance both run.
apps/app/ The desktop app (Electron): the same documents, plus the sync
that mirrors a vault to a folder.
apps/markbase/ The `markbase` CLI (@markbase/cli): sign in, mount a vault,
run the sync as a background service.
packages/core/ What everything is built on
protocol/ Isomorphic types, the API client, pure logic. Runs in a
browser, a server and a daemon alike.
vault/ The local vault: watcher, lock, registry, file sync.
flows/ Steps every client shares (sign in, mount a vault), written
once against an operator that asks the questions.
node/ registry/ ui/ runner/ agent/ llm/ browser-agent/
packages/features/ Things that live in the kernel
docs/ The collaborative document engine: CRDT, markdown,
comments, history, the vault's file contents. Released.
agents/ attention/ diary/ email/ projects/ reader/ skills/ terms/ today/
In the repository, not in the released product. A build
ships them only when MARKBASE_FEATURES names them.
supabase/ Migrations and database tests. The schema is built from these.
docs/ Design notes: the shared vault, the workspace layout, how
features plug in, and how to add an API endpoint so agents
get it as a tool (docs/adding-an-endpoint.md).
The vault is core and documents are a feature, so the dependency points from
docs to vault, not the other way: the vault says what it needs from a
synced file and docs implements it.
packages/core/protocol/test/package-boundary.test.ts fails if an edge is
added back.
From a fresh clone to a running app, in order. You need Node.js 22 or later and Docker (the local database runs in it).
npm install # at the repo root; one install for every workspace
Markbase runs on Supabase — auth, realtime, storage and Postgres — so this comes before the app: without a project to talk to, no page renders. The local stack is a full Supabase on your machine:
npx supabase@2 start
The first start pulls the images and applies everything in
supabase/migrations, so the schema is ready when it finishes. Use @2: the
repository targets the Supabase CLI 2 line.
One local-only fix, once after every fresh start or db reset: the local
image leaves the API's role without access to the tables the migrations
created, and the app answers 42501 until it is granted.
docker exec "$(docker ps --format '{{.Names}}' | grep '^supabase_db_')" psql -U postgres -d postgres -c "grant all on all tables in schema public to service_role; grant all on all sequences in schema public to service_role;"
npx supabase@2 status
prints the stack's addresses and keys. Put four of them, plus a key of your
own, in apps/web/.env.local:
NEXT_PUBLIC_SUPABASE_URL=http://127.0.0.1:54321 # API_URL
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY=sb_publishable_... # PUBLISHABLE_KEY
SUPABASE_SECRET_KEY=sb_secret_... # SECRET_KEY
APP_URL=http://localhost:3000
SECRETS_ENCRYPTION_KEY= # openssl rand -base64 32
These are the same names as .env.example, which describes
each one and lists the optional ones.
npm run dev # → http://localhost:3000
Because APP_URL is not markbase.so, this is a team instance, and it has no
accounts yet: the first page is Set up localhost:3000, and the account you
create there is its admin. After that, sign-up needs an invite from Settings.
Mail from the local stack (there is none in this flow) lands in Mailpit at
http://127.0.0.1:54324; the database UI is at http://127.0.0.1:54323.
npm run typecheck # every workspace — what CI runs
npm test # every workspace's tests
npx supabase@2 test db # the database's own tests, after a migration change
Both talk to the web app from step 4, so start that first.
cd apps/markbase && npm run build && npm link
markbase login --app-url http://localhost:3000 # browser sign-in, installs the sync service
markbase vault mount "Team notes" ~/Code/my-app/docs
cd apps/app && npm run build && npx electron . # a dev run of the desktop app
npm run dist in apps/app packages a DMG; from a fresh checkout that has
two extra steps, in Building the desktop app in
SELF-HOSTING.md. markbase instance <url> shows or
changes which instance the CLI and the desktop app talk to, and
MARKBASE_APP_URL overrides it for one command.
Skip step 2. Create a project on supabase.com, apply the migrations with
npx supabase@2 db push --db-url "<its connection string>", and take the
values for step 3 from the project's settings —
SELF-HOSTING.md section 1 has the details.
Pull requests are welcome. Commits need a Signed-off-by line (git commit -s); CONTRIBUTING.md says why and covers bringing code
from elsewhere.
Apache-2.0. The licence covers the code, not the name or the logo: TRADEMARK.md says what you may do with those without asking. Third-party notices are in THIRD_PARTY_NOTICES.md.