LLM Mart Basic
@llm-mart · Joined Jun 2026
Address a document by its BLOCKS instead of reading it whole. Use for any long Markdown or documentation file — README, spec, guide, design doc, changelog — when the job is to find where something is documented, read one section, or change one section: `geml list`, `geml find` an
Build, view, update, and navigate a project's call graph as GEML codemap documents. Use when asked to see/update/build a project's code graph or codemap (看下/更新下 code-graph), when asked "who calls X" / "what does X call" / to trace a call chain or impact path, or whenever a .geml-
Address a document by its BLOCKS instead of reading it whole. Use for any long Markdown or documentation file — README, spec, guide, design doc, changelog — when the job is to find where something is documented, read one section, or change one section: `geml list`, `geml find` an
Build, view, update, and navigate a project's call graph as GEML codemap documents. Use when asked to see/update/build a project's code graph or codemap (看下/更新下 code-graph), when asked "who calls X" / "what does X call" / to trace a call chain or impact path, or whenever a .geml-
Address a document by its BLOCKS instead of reading it whole. Use for any long Markdown or documentation file — README, spec, guide, design doc, changelog — when the job is to find where something is documented, read one section, or change one section: `geml list`, `geml find` an
Build, view, update, and navigate a project's call graph as GEML codemap documents. Use when asked to see/update/build a project's code graph or codemap (看下/更新下 code-graph), when asked "who calls X" / "what does X call" / to trace a call chain or impact path, or whenever a .geml-
Address a document by its BLOCKS instead of reading it whole. Use for any long Markdown or documentation file — README, spec, guide, design doc, changelog — when the job is to find where something is documented, read one section, or change one section: `geml list`, `geml find` an
Build, view, update, and navigate a project's call graph as GEML codemap documents. Use when asked to see/update/build a project's code graph or codemap (看下/更新下 code-graph), when asked "who calls X" / "what does X call" / to trace a call chain or impact path, or whenever a .geml-
Memory washer/defragmenter for agent memory — two lanes: class-B (memory+governance) cleans the FAT, never the MEAT; class-A (transcripts) is byte-identity-only. Fidelity-first: a free mechanical Quick pass + a CODE gate blocking any STRUCTURED-token drop by diff; the paid Full p
Memory washer/defragmenter for agent memory — two lanes: class-B (memory+governance) cleans the FAT, never the MEAT; class-A (transcripts) is byte-identity-only. Fidelity-first: a free mechanical Quick pass + a CODE gate blocking any STRUCTURED-token drop by diff; the paid Full p
Ask which skill or flow fits your situation. A router over the skills in this repo.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agent
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
A relentless interview to sharpen a plan or design.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Compact the current conversation into a handoff document for another agent to pick up.
Implement a piece of work based on a spec or set of tickets.
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.
/health
Health
One-line reliability verdict (OK / DEGRADED / FAILING) for Claude Code usage
/slo
Slo
Print a quick SLO snapshot — completion rate, tool success rate, and error rate
/report
Report
Generate an evidence-backed CCAM executive, cost, reliability, or workflow report.
/runs
Runs
List live and persisted CCAM-launched Claude Code and Codex runs
/find-session
Find session
Search Agent Monitor sessions by cwd, model, or status and print the top matches.
/recent
Recent
List the N most recent Claude Code sessions from the Agent Monitor.
/replay
Replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
/dag
Dag
Print the orchestration DAG edges (parent→child subagents) for a session.
/runs
Runs
List recent Workflow-tool fleet runs with status and agent counts.
/workflow
Workflow
Summarize the workflow intelligence for a session — stats, complexity, and top patterns.
/broadcast
broadcast
Run broadcast on a distilled Raw — update related existing pages conversationally
/distill
distill
Distill raw session records into refined Notes and Projects
/evolve
evolve
Save knowledge to the cortex vault (Notes or Projects) and update index
/genesis
genesis
Initialize cortex vault — set up config, vault structure, and rebuild index
/query
query
Manually search the cortex vault (Notes, Projects, Raw) for existing notes
/takeoff
takeoff
Create, resume, or clear a session hand-off baton (one per work line)
/dev
Dev
Command → Agent → Skill orchestration for end-to-end feature development.
/investigate
Investigate
Command → Agent → Skill orchestration for investigating and fixing bugs.
/company
Company
Brief the CEO: coordinate with the peer CTO and start or resume a founder project across 8 departments and 54 skills
/onboard
Onboard
Configure an optional active team profile in three short questions
Unofficial KakaoTalk CLI and native MCP server for macOS — read, watch, and send messages via Accessibility automation.
3 views 0 likesLocal-first AI action assistant for operators: memory, skills, tools, and permission gates to turn work into controlled action.
3 views 0 likesAgent-driven media library for your cloud drives (Quark 夸克 / 115 / 光鸭 GuangYa / 123网盘 / 天翼 Tianyi)
4 views 0 likesAn open-source desktop AI agent built around Cyrene’s persona and powered by the self-developed Cyrene_Harness framework. It combines immersive character chat w…
3 views 0 likes在 Android 上运行的 AI 编程 Agent,内置 Linux 终端与代码编辑器,支持 MCP 协议扩展。
4 views 0 likesTencentDB Agent Memory is a team-level memory hub for AI Agents — turning conversations, docs, and code into four reusable memory assets (Chat Memory, Skill, LL…
4 views 0 likesFloe — a native iOS/iPadOS AI agent workspace for iPhone and iPad, built for private bring-your-own-key workflows.
4 views 0 likesSpring Boot AI Agent — an out-of-the-box solution that makes your app converse, remember, think, and act.
4 views 0 likesGive your AI agent eyes for PDFs — structured text, tables, OCR, visual evidence, and page-level citations via MCP. Native Rust, local-first.
5 views 0 likesA tiny Claude Code skill that keeps your prompt cache warm during idle sessions, so your next message reads from cache instead of paying full price.
5 views 0 likesMonet — Multi-engine mission control for coding agents (Claude Code and Codex today). Browse, search, and drive your agent sessions from a native desktop app.
1 views 0 likesA DottedSign MCP server that enables AI assistants (Claude, ChatGPT) to manage signing tasks, templates, and document status via natural language.
1 views 0 likesКурируемый handbook по Claude Code на русском: hooks, skills, CLAUDE.md шаблоны, MCP-серверы, кейсы.
1 views 0 likes👾 Open Computer Use – Open-Source Alternative to Codex Computer Use
1 views 0 likesAn open-source AI companion that actually remembers you — runs entirely on your own Mac or server. Desktop pet · long-term memory · proactive companionship · mu…
3 views 0 likesGraphical management tool for Kubernetes on desktop and mobile.
4 views 0 likesOpen-source desktop app for content creation, with an agent runtime and standalone CLI.
3 views 0 likesConnect Claude and ChatGPT to KDAN PDF — upload, edit, compress, protect, redact, and compare PDFs in chat.
2 views 0 likesEkko Studio is a local-first AI workspace for multi-agent chat, coding, and visual workflows, available on desktop and the web.
3 views 0 likesOpen-source native iPhone/iPad client for OpenAI Codex CLI and Claude Code — review diffs, approve actions, steer sessions, and manage Git remotely.
4 views 0 likes