LLM Mart Basic
@llm-mart · Joined Jun 2026
Use when any bounded workflow starts or reaches an action, path, proposal, or merge boundary. Refuses rather than default-allow on an unreadable constraint set.
Use when work is about to grow past the ask, the task may already be done, or the user requests only the minimum. Not for executing the work: use tdd to build or strike-the-root to fix.
Use when an artifact or skill has just changed and is about to be called done, committed, or handed off. Not for remote, credential, publish, deploy, or irreversible changes.
Use when the user suspects no installed skill covers a task and wants proof. Names the owning skill or writes a missing-skill brief. Never routes or invokes the matched skill.
Use when a task, feature, or fix is called done, complete, finished, or fixed, or before a commit, PR, or next task. Not for fact-checking: use verify-both-ways. Not for measuring: use verify-this.
Use when the user wants to classify abstractions as useful, bad, or busy and keep one shallow level. Not for tasks requiring source or remote-system changes.
Use when a task is ambiguous or intent needs eliciting: exhaustive/collaborative/adversarial askme, batch questions, interview, ambiguity scan, or intent proposal. Not for one fork: use decide.
Use when the user runs /autoplan on a plan or idea. Reviews, amends, and derives task IDs with a final human approval gate. Not for remote, credential, publish, deploy, or irreversible changes.
Use when asked to park an undecided idea without representing it as decided or active work. Not for decided or active work: use the project task system.
Use when the user wants to collapse an open decision field to one decision and record its rationale locally. Not for multi-lens pressure testing. No remote or irreversible changes.
Use when the user has a fork and wants it resolved and applied, not explored: "decide this", "choose the path", or "decide and fix it".
Use when the user wants the finished-system contract for a piece of work: behavior, protocols, allowed, forbidden, and impossible states with a state-space proof. Not for runtime verification.
Use when the user wants to expand a decision field with additional options and dimensions. Not for selecting or applying an option: use decide. No source or remote-system changes.
Use when the user explicitly requests a Tarot draw or casually delegates an ambiguous choice among multiple valid approaches.
Use when a user wants to define failure states, recovery actions, bypasses, and degraded modes for a component during design. Not for runtime recovery.
Use when a user wants to rebuild a design, organization, or API from primitives. Not for a perspective take: use from-*-perspective seats.
Use when asked to derive the general rule a request carries as examples instead of a stated rule, then bound it. Not for ambiguity in a stated request: use askme. Read-only.
Use when a durable effort needs an approved, checkable success predicate before work starts. Not for requirement-to-evidence ledgers. Never remote, credential, publish, deploy, or irreversible.
Use when defining, revising, or gate-replanning the project structural backbone in project-root graph.yaml. Not for remote, credential, publish, deploy, or irreversible changes.
Use when the user asks to park ideas or inspiration for later. Not for code, backlog, or divergence-class cards, or remote, credential, publish, deploy, or irreversible changes.
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.
/story-cover
Story cover
网文封面生成。分析书名题材,生成专业封面图。
/story-deslop
Story deslop
网文去AI味。检测并清除文本中的AI写作痕迹,让文字回归自然。
/story-import
Story import
逆向导入已有小说。将已写好的小说反向解析为标准项目目录结构。
/story-long-analyze
Story long analyze
长篇网文拆文。深度拆解爆款长篇小说的黄金三章、人设、爽点、节奏。
/story-long-scan
Story long scan
长篇网文扫榜。分析起点、番茄、晋江等平台排行数据,提炼市场趋势。
/story-long-write
Story long write
长篇网文写作。从大纲到正文,辅助长篇网络小说的创作。
/story-review
Story review
多视角对抗式审查。使用多个 Agent 对作品进行多维度审稿。
/story-setup
Story setup
网文写作环境部署与检查。部署 hooks、rules、agents、项目指令等基础设施;传入 check 只检查不改动。
/story-short-analyze
Story short analyze
短篇网文拆文。拆解爆款短篇的故事核、结构、情感线和反转设计。
/story-short-scan
Story short scan
短篇网文扫榜。分析知乎盐言、番茄短篇等平台热门数据。
/story-short-write
Story short write
短篇网文写作。辅助短篇小说创作,从构思到成稿。
/story
Story
网文工具箱路由入口。根据模糊意图自动分发到对应的写作、拆文或扫榜工具。
/browser-cdp
Browser cdp
浏览器操控。通过 CDP 复用 Chrome 登录态执行浏览器自动化。
/story-cover
Story cover
小说封面生成。根据书名、作者名和题材生成专业网文封面。
/story-deslop
Story deslop
网文去 AI 味。检测并清理模板化、解释腔和过度工整表达。
/story-import
Story import
逆向导入已有小说,将成稿或半成品解析为可续写项目。
/story-long-analyze
Story long analyze
长篇网文拆文,分析黄金三章、人设、爽点和长线节奏。
/story-long-scan
Story long scan
长篇网文扫榜,分析起点、番茄、晋江等平台趋势。
/story-long-write
Story long write
长篇网文写作,从选题、大纲到逐章正文和持续追踪。
/story-review
Story review
多视角小说审查;ZCode 项目 agents 不可用时自动降级 solo。
🤖 MateClaw — Your second brain with Multi-Agent Orchestration, MCP Protocol, Skills & Memory, Dream, and Multi-Channel Support. Built on Spring AI Alibaba.
12 views 0 likesVibe-Research: Your Personal Trading Research Agent · A股/美股/港股 的个人投研 Agent:每日复盘、资讯雷达、个股数据、板块中心、我的持仓、研究记录、回测。Vibe-Research 把数据和功能配齐,由你自己的 Agent 驱动投资研究。基于开源的 Code…
8 views 0 likesWayland - The AI Agent That Perceives. Reasons. Acts. Evolves.
15 views 0 likesObservability and enforcement for AI agent harnesses. Capture every run and runtime reliability with policy enforcement. 40 built-in policies, a local dashboar…
16 views 0 likesTurn your Solana Seeker (or any Android phone) into a 24/7 personal AI agent
12 views 0 likesA curated collection of offensive, defensive and AI/LLM security tools.
11 views 0 likesAI agent 通用任务治理框架:对齐目标与事实,规划和调度能力,守住授权与风险边界,治理任务执行到真实验收与交付。Governance framework for evidence-driven planning, orchestration, and verified delivery.
21 views 0 likesOpen-source (Apache-2.0) PDF takeoff for construction & flooring — the first engine an AI agent drives natively over MCP, not bolted on. One-click room detectio…
11 views 0 likesStop degrading your model's reasoning. A minimal, zero-config AI coding agent. Enforced ephemeral subagents keep context pure. From tiny local models up to Sol,…
14 views 0 likes实习.skill — 双非也能拿大厂 offer。帮你改简历、抠面经、准备面试,把真实背景翻译成面试官想要的样子。
15 views 0 likes专门为 agent 打造的 agent 搜索工具,具备多语言搜索能力,覆盖中文/英文/学术/代码/购物/金融/新闻/百科。
9 views 0 likesLocal-first AI agent workspace for multi-agent collaboration, agent orchestration, scoped permissions, evidence-aware runs, and human-in-the-loop decisions.
11 views 0 likesKeyboard-first desktop Kanban workspace for AI coding agents with embedded terminals, git worktrees, and hook-driven task tracking.
15 views 0 likesClaude Code Prompt Mechanism Visualizer — Electron desktop app
19 views 0 likesMulti-repo semantic code search MCP server in Rust — hybrid vector + BM25 retrieval, tree-sitter AST chunking, fully offline. For OpenCode, Claude Code, Cursor,…
18 views 0 likesOne-ink editorial print image skill — warm paper, halftone photography, active negative space, and restrained typography.
17 views 0 likesUS stock market data for AI coding assistants — zero-auth, official sources. CBOE options with full Greeks + 0DTE flow, FINRA market-wide short volume, SEC EDGA…
15 views 0 likesAI-powered Werewolf (Mafia) social deduction game where every player is controlled by top LLMs like DeepSeek, Qwen, Gemini, and more
10 views 0 likesA股全栈数据工具包 · 十一层架构 · 54端点 · 19数据源 · 零鉴权 | Full-stack China A-share data toolkit for AI agents — 11 layers, 54 endpoints, 19 sources, zero-auth
14 views 0 likesAgentic desktop GUI client for Elasticsearch, OpenSearch, DynamoDB, MongoDB & EasySearch. Natural language queries, visual management, and monitoring. Privacy-f…
11 views 0 likes