LLM Mart Basic
@llm-mart · Joined Jun 2026
Autonomous task executor for spec-kit development. Executes a single task from tasks.md, verifies, commits, and signals completion.
Expert task planner for breaking plans into executable tasks. Masters POC-first workflow, task sequencing, quality gates, and constitution alignment.
This agent should be used to "create technical design", "define architecture", "design components", "create design.md", "analyze trade-offs". Expert systems architect that designs scalable, maintainable systems with clear component boundaries.
This agent should be used to "generate requirements", "write user stories", "define acceptance criteria", "create requirements.md", "gather product requirements". Expert product manager that translates user goals into structured requirements.
This agent should be used to "run verification task", "check quality gate", "verify acceptance criteria", "run [VERIFY] task", "execute quality checkpoint". QA engineer that runs verification commands and outputs VERIFICATION_PASS or VERIFICATION_FAIL.
This agent should be used to "update spec files", "refactor requirements", "revise design", "modify tasks after execution", "incrementally update specifications". Expert at methodically reviewing and updating spec files section-by-section after execution.
This agent should be used to "execute a task", "implement task from tasks.md", "run spec task", "complete verification task". Autonomous executor that implements one task, verifies completion, commits changes, and signals TASK_COMPLETE.
This agent should be used to "review artifact", "validate spec output", "check quality", "review research output", "review requirements", "review design", "review tasks", "review execution", "review prototype evidence". Read-only reviewer that validates artifacts against type-spe
This agent should be used to "create tasks", "break down design into tasks", "generate tasks.md", "plan implementation steps", "define quality checkpoints". Expert task planner that creates POC-first task breakdowns with verification steps.
This agent should be used to "decompose a large feature", "triage a big task", "break down into multiple specs", "create epic decomposition", or needs guidance on splitting large features into dependency-aware spec graphs.
dstack is an open-source control plane for GPU provisioning and orchestration across GPU clouds, Kubernetes, and on-prem clusters.
Create and manage dstack presets: a toolkit that streamlines model inference optimization with agents, and a portable preset format. Use together with the dstack skill, and only when the user explicitly asks to create a preset or manage existing presets, not for deploying or serv
Use with the dstack skill for model-serving work when the image, serving command, resources, backend/fleet choice, or service behavior is not proven. Guides task-first prototyping on real hardware, choosing fleets/backends that can reuse idle instances and caches, checking vLLM/S
Extract semantic structure and transferable style grammar from academic figures, PDFs, and paper or figure URLs for analysis, redraws, or reference-conditioned generation. Do not use it for paper-text-only figure planning.
Unified academic figure designer, semantic color & surface decision engine, and FigureSpec v1 compiler. Handles style selection, reference palette derivation, colorblind-safe token binding, SVMC visual metaphors, and normalized compact prose prompt compilation across classic-tech
Plan evidence-backed figures for a paper draft, markdown notes, outline, manuscript, PDF, or paper webpage. Supports Draft-to-Figure fast-track for Markdown notes as well as comprehensive multi-figure planning for full manuscripts.
Plan, generate, inspect, and refine academic figures from repositories, papers, draft notes, paper URLs, PDFs, or reference images. Supports fast-track draft-to-figure generation and user passthrough mode.
Analyze ML, AI4Science, Systems, and research repositories into an evidence-backed semantic architecture graph for paper figure planning. Code serves as supporting evidence; paper narrative and user intent remain the primary source of truth.
Coordinate agents via the AMQ CLI for file-based inter-agent messaging. Use this skill whenever you need to send messages to another agent (codex, claude, or any named handle), check your inbox, drain queued messages, set up co-op mode between agents, join a swarm team, route mes
Parallel-research-then-converge design workflow between two agents. Use this skill when the user wants two agents to independently think through a design problem before aligning on a solution — "spec X with codex", "design X together", "both agents think through X", "brainstorm a
Fourteen posts of being wrong in production, compressed to checkboxes
Healthy nodes, a quiet network, 300 restarts in three days, and a latency budget measured in milliseconds
Discovery worked. Ping worked. Every TCP connection timed out, and later the tunnel only worked when someone had a terminal open.
Every VM came back. The cluster did not. Declarative systems converge on config, and the datapath isn't config.
A surprising share of AI-in-the-terminal failures aren't the AI. They're zsh, and a version of bash from 2006.
A Claude Code plugin turns standalone project configuration into a namespaced, installable extension that teams and communities can update as one unit.
None of the safety came from the model. It came from six boring habits.
Skills package instructions and references. Subagents run work in a separate context and return results. They solve different problems and can be composed deliberately.
Six hours in, one step left, everything green, and the incident that didn't happen
CLAUDE.md carries persistent project context. Skills load reusable procedures when relevant. Separating stable facts from task-specific workflows keeps both easier to maintain.
Twenty minutes recovering secrets that never existed, and the one sentence from a human that ended it
An API request routing a model's tool call through an approval gate to a remote MCP server
31 config keys, two audits, and why the first one was wrong in both directions
The official MCP Registry stores standardized server metadata rather than package code. Publishers verify a namespace, describe installation or remote access, and submit immutable versions.
Everyone looks at the Dockerfile. The file that actually leaked the key was the project file.
Remote MCP authorization uses established OAuth standards, but secure integration still requires issuer validation, least-privilege scopes, protected token handling, and server-side enforcement.
"Copy it over and switch the reference" is two steps, and the outage lives in the one nobody checks
stdio fits local processes and prototypes. Streamable HTTP fits hosted services and shared integrations. The right choice follows where the capability runs and who must reach it.
The most important rule wasn't about what I could change. It was about what I was allowed to display.
Tools perform operations, resources expose readable context, and prompts provide reusable templates. Choosing the correct primitive makes an MCP server easier to understand and govern.
/release
Release
This is the only sanctioned way a version tag gets created, and it holds no knowledge of any
/review
Review
A read-only review of the current change, dispatched by path against a reviewer-to-path matrix:
/spike
Spike
This is the outlet for "I need to write code to find out" rather than "I know what to build." The
/sprint
Sprint
This is codeArbiter's autonomy mode. It collapses the usual spec-plan-execute cycle into one
/standup
Standup
The daily hygiene checklist, made routine and gated: fetch and offer a fast-forward pull, list
/status
Status
A read-only snapshot of `.codearbiter/` state: the project's `stage:` maturity value, every
/statusline
Statusline
Wires codeArbiter's renderer into `~/.claude/settings.json`, or removes it. A plugin can't own a
/task
Task
The only blessed way to mutate `.codearbiter/open-tasks.md`. It runs a thin writer over pure
/threat-model
Threat model
An opt-in, lightweight STRIDE pass over a design before it's built — invoked deliberately, never
/tribunal
Tribunal
Tribunal is codeArbiter's deepest review, for a deliberate audit of a repository or subtree.
/watch
Watch
Watches a pull request's CI checks to completion without polling by hand. The wait is a real
/debug
Debug
A fixture command named debug, colliding with the debug skill/agent.
/prune
Prune
A fixture command named prune, used to regression-test forge badges.
/another
Another
Another command, description only, no argument hint.
/sample
Sample
A sample command for fixtures — single sanctioned path to a thing.
/to-gif
To gif
Convert an animated HTML file (like /fig output) to a perfectly looping high-quality small GIF using Playwright + ffmpeg
/getpix
Getpix
Find a free licensed image on the internet and add it to the project, optimized
/photo-pass
Photo pass
Art-direction photo pass over the site: add photography only where it earns its place
/tree-ring-audit
Tree ring audit
Audit consolidate or forget stale sensitive or superseded Tree Ring Memory entries
/tree-ring-capture
Tree ring capture
Capture a concise validated lesson decision warning or preference in Tree Ring Memory
Build AI Agents like playing LEGOs. Everything is a Plugin.
4 views 0 likesThe coding agent that answers to you, your model, your machine, your rules.
6 views 0 likesCI-native agent CLI tool for deterministic pipeline gating.
11 views 0 likesLocal-first cross-platform desktop workspace for Claude Code / agents: multi-agent, Git worktrees, code diffs, skill marketplace, multi-model, Computer Use, tas…
10 views 0 likesLocal-first visual generation runtime and studio for people and coding agents, with reproducible image and video workflows across multiple providers.
11 views 0 likesA token-efficient MCP server for safe, line-oriented text file editing with partial reads, hash-based conflict detection, and atomic multi-file operations.
15 views 0 likesOpen-source, evidence-driven MCP server for RTL simulation debugging: correlate VCS/Xcelium logs, VCD/FSDB waveforms, SystemVerilog/UVM source, hierarchy, and c…
13 views 0 likesruns anywhere. uses anything
18 views 0 likesOne macOS app for Claude Code, Codex, and every agent runtime you use — scheduled runs, global hotkey launcher, per-run git worktrees, one review board.
12 views 0 likesSoul-driven AI agent with permission-hardened tools, token budgets, and multi-channel access. Runs 24/7 from CLI or Telegram.
7 views 0 likesEmail, SMS & phone-call infrastructure for AI agents — send and receive real email and text messages, and place agent-driven outbound voice calls, all programma…
14 views 0 likes55 MCP tools to drive the Unity Editor from any MCP-compatible AI agent — scenes, GameObjects, prefabs, assets, tests, and builds. OpenClaw gateway included for…
12 views 0 likesGoogle Ads MCP + Meta Ads MCP + GA4 in one server for Claude, ChatGPT, Cursor & n8n — 250+ tools, hosted remote MCP, OAuth login, no API keys. By Ryze AI.
4 views 0 likesClaude Code & Codex 本地 token 追踪 — 状态栏(Codex 业界首创伪 statusline)、GitHub 风格热力图、多模型成本分析。 | Local token tracker for Claude Code & Codex — status line (industry-first…
12 views 0 likesEmpower the Shell to think. Evolve Operations.
6 views 0 likes🤖 A full-stack Agent Chat Runtime for pre-production validation, built with act, TypeScript, and LangGraph JS combining streaming, multimodal, HITL, and tools…
14 views 0 likesCerul — video memory infrastructure for AI products. SDKs, CLI, MCP, and developer integrations.
17 views 0 likesStealth headless browser for AI agents — bypass Cloudflare, bot detection, and anti-scraping. Drop-in Puppeteer/Playwright replacement.
8 views 0 likesWeb research for your agents with smart and safe tooling + knowledge store
16 views 0 likesFuXi is a fast, self-contained AI coding agent that lives in your terminal — edit code, run commands, and drive tools, with cost-aware routing across LLM provid…
12 views 0 likes