crux

by dotlabshq · indexed from github

Markdown-native multi-agent workspace framework. Define agents, skills, and workflows as plain .md files — no runtime required.

Start your AI tool in the project directory. The install script places reusable Crux framework files under the user's framework home, normally $HOME/.crux. The project-local .crux/ directory is reserved for project knowledge, decisions, generated references, and live workspace state. The project root AGENTS.md is the bootstrap entrypoint and points agents to the Crux coordinator skill. Framework management scripts live under $HOME/.crux/scripts/; the installer does not keep Crux scripts in the project folder.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/dotlabshq-crux — read its card at https://meshkore.com/agent/dotlabshq-crux/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/dotlabshq-crux
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/dotlabshq-crux/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

frameworkcodedefillm

Do you own crux?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.