LLM Mart Basic
@llm-mart · Joined Jun 2026
缺陷修复方法论唯一入口:口喷 bug 定位直修;implement-test-review 循环内的反馈修复也走本 skill(循环内分支,原 impl worker 执行)。触发:修 bug / 有个 bug / 报错了 / 行为不对 / fix / /eo-fix。 NOT FOR: 明确的业务变更(走 /eo-change)。
在 /clear 之前生成最小可恢复快照到 tmp/eo/handoff/<topic>.md,让下一个会话载入这一个文件就能从当前节点继续。优先记录任务状态、关键口径、下一步分叉,主动丢弃探索过程。触发:handoff / 存一下进度 / 我要 clear / /eo-handoff。 NOT FOR: 机械压缩对话流(用内置 /compact)。
按 change.md 的 TODO 分批落地代码,批末自验对应 AC。触发:实现 / 写代码 / implement / /eo-implement。 NOT FOR: bug 与反馈修复(口喷 bug 与 test/review/acceptance 循环内反馈一律走 /eo-fix);变更起草(走 /eo-change)。
eo 流程总控:按用户意图圈一段(入口节点 → 出口节点 → 收敛标准),把 eo-change / eo-implement / eo-archive 及可选闸门(eo-change-review / eo-test / eo-review)派发到可插拔执行基底上推进至收敛,窗口化汇报进度。触发:eo-loop / 串起来跑 / 循环推进到收敛 / 总控调度 / /eo-loop。 NOT FOR: 单点动作(直接调对应 eo-* skill);派出去不再监督的完全交接(orca-cli full handoff);bug 口喷(/eo-fix)。
eo-skills 在当前仓库的总入口:生成 .eo-project.json、初始化项目管理侧(roadmap)和代码侧最小骨架(eo-doc/),以及 agent 配置注入。触发:启动项目 / 初始化项目 / 新建项目 / /eo-project-init。
项目记忆的统一写入口:经验教训(lessons/)与关键决策(decisions/),带 INDEX 与检索锚点,供 eo-change / eo-fix / eo-recall 消费。通过 .eo-project.json 定位。触发(仅用户明确要求记录时):把这个坑记下来 / 记条经验 / lesson learned / 把这个决策记下来 / 记录决策 / reindex lessons / reindex decisions / /eo-project-record。NOT FOR: 对话提到踩坑或决策但用户未要求记录;待办类(走 /eo-bac
只读的回忆与解释入口,分层作答带出处。触发:这个功能当时怎么设计的 / 这段逻辑怎么实现的 / 当初为什么这么定 / 帮我回忆 / recall / /eo-recall。 NOT FOR: 修 bug(/eo-fix)、发起变更(/eo-change)、维护文档(/eo-doc-manager)。
按需代码审查:风险信号命中或用户点名时,对已实施代码做 AC 逐条核对 + 代码质量审查,产简版 review.md(P0/P1/P2)。触发:review / 代码审查 / 再找双眼睛看看 / /eo-review。 NOT FOR: change 方案审查(/eo-change-review,代码还没写时用);默认主路(无信号时不强制)。
按需独立测试视角:风险信号命中或用户点名时,对已实现 change 做测试审计、补缺与重验证,产简版 test.md。严禁修改业务代码。触发:找双新眼睛跑测试 / 独立验证 / 给这个 change 补测试 / /eo-test。 NOT FOR: 与 change 无关的日常跑测试或补单测(直接做即可,不产报告);默认主路的自验(归 eo-implement)。
接口级测试时使用——从 OpenAPI/Swagger 文档或用例 Schema 中可自动化的接口用例出发,覆盖参数、边界、鉴权、幂等、并发、错误响应与数据一致性,产出可执行的 API 测试脚本与运行结果;含接口压测承接(k6,类型矩阵轴 1 执行层)。不用于:Web UI 流程(automated-e2e-testing)、手动用例编写(test-case-writing)。
将手动测试用例转为 Playwright E2E 测试并执行时使用;含写自动化前的业务熟悉踩点、Page Object/Helper 编写、执行中的 Bug 证据收集与报告条目记录。不用于:纯 API 接口测试(api-testing)、以理解系统为目的的独立探索会话(exploratory-testing)、已确认 Bug 的根因分析(bug-analysis)。
对已确认的 Bug 做根因定位、影响分析、回归建议时使用——复现 → 读代码定位根因 → 影响五面分析 → 回归建议,条目(根因/影响/Severity 依据/修复建议)追加进测试报告。不用于:仅收集 Bug 证据(automated-e2e-testing / api-testing)、疑似未定性缺陷(test-case-writing 的 Cx 记录)。
qa-skills 共享知识库,安装依赖单元(非触发 skill):承载被其余 10 个 skill 以相对路径引用的方法、规则、模板与脚本(可执行性标准、证据分级、风险模型、类型决策矩阵等)。仅在 qa-skills 系列 skill 工作流中被引用读取;任何具体测试任务都不要独立触发本 skill,独立使用无意义。通过 npx skills 等安装器单独安装其他 qa-skills skill 时,必须同时安装本 skill,否则引用路径断裂。
需求不完整、系统陌生、文档不足时,发起以理解系统/发现风险为目的的独立探索式测试会话时使用——charter 驱动(目标 → 探索 → 记录),产出探索笔记(系统理解/风险清单/测试想法)作为需求建模输入或独立交付。不用于:为写自动化踩点的小规模探索(automated-e2e-testing 工作流零)、按既有用例执行(执行类 skill)。
端到端测试的唯一入口:用户说"帮我测试这个需求/功能"、"把这个功能完整测一遍"时,编排需求理解→测试策略(风险与类型决策)→用例→审查→执行→Bug 分析→回归→报告的完整流水线,产出落盘、可断点续跑。只要单阶段产出(如"帮我审一下这份用例")→ 直接用对应阶段 skill,不用本 skill。
代码变更(diff/Bug 修复/需求变更)后判断应回归哪些测试时使用——沿"改动文件 → 改动函数 → 受影响功能 → 受影响用例"分析链,基于用例 Schema 的追溯映射产出分级回归清单。不用于:用例文件本身的增量修改(test-case-writing)、长期回归策略(test-strategy)。
系统性建模某个需求/系统时使用——从 PRD、设计/API 文档、Bug、Issue、代码中提炼目标、范围、角色、规则、异常、依赖与不明确项,产出结构化需求模型(含澄清记录与用户裁决)。不用于:已有需求模型直接写用例(test-case-writing)、"怎么测"的策略决策(test-strategy)、端到端流水线(qa)。
审查已有测试用例(存量资产、他人编写、AI 产出)的覆盖与可执行性时使用——先建可测点基准,再独立评估覆盖、可执行性与正确性,直接修订用例文件并留审查记录。不用于:从零写用例(test-case-writing)、写时自审(其阶段四)、端到端流水线(qa)。
从需求文档、API 文档、Bug 报告或代码仓库产出可执行的手动测试用例(markmap)时使用——代码优先:索取仓库、先代码审查找潜在 bug 再写用例,并抽取机器可读 Schema。不用于:需求建模(requirement-analysis)、测试策略(test-strategy)、独立审查(test-case-review)、自动化脚本(automated-e2e-testing / api-testing)。
回答"这个功能应该怎么测"时使用——风险评级挂证据(Risk Map),翻译成功能域+类型域两域范围与深度:类型域十轴全轴必答(脚本扫描信号+预填修订),include挂信号、exclude挂理由、full有预算上限。不用于:已有策略直接写用例(test-case-writing)、需求建模(requirement-analysis)、端到端流水线(qa)。
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.
/plugin-review
plugin-review
"Tiered plugin quality review: branch (quick gates),
/promote-discussions
promote-discussions
Check GitHub Discussions for highly voted learnings and promote them to Issues.
/rules-eval
rules-eval
Evaluate Claude Code rules in .claude/rules/ directories for quality
/skills-eval
skills-eval
Audit skill quality, frontmatter compliance, token efficiency, and activation reliability. Recommends improvements.
/test-skill
test-skill
Test Claude Code skills using RED/GREEN/REFACTOR TDD phases in fresh subagents to prevent priming bias.
/validate-hook
validate-hook
Validate hooks for security, performance, and SDK compliance
/validate-plugin
validate-plugin
Validate plugin structure, schema, and naming. Use for plugin creation, debugging, or verification.
/arch-init
arch-init
Initialize projects with architecture-aware templates using paradigm research and selection guidance for the target domain.
/blueprint
blueprint
Generate an implementation plan with system architecture design and dependency-ordered task breakdown from a specification.
/brainstorm
brainstorm
Guide project ideation through Socratic questioning to generate briefs with validated approaches and decision rationale.
/execute
execute
Execute implementation plan systematically with progress tracking and checkpoint validation
/mission
mission
Run full attune lifecycle as a mission with state detection and phase routing
/project-init
project-init
Initialize a new project with git setup, CI/CD workflows, pre-commit hooks, Makefiles, and language-specific tooling.
/skill-library
skill-library
Build a project skill library under .claude/skills/ as a resumable mission: discover, author in parallel, review adversarially.
/specify
specify
Create specs from project briefs with acceptance criteria and testable requirements
/upgrade-project
upgrade-project
Update existing project configurations to current best practices with selective component upgrades
/validate
validate
Validate project structure and configurations against best practices with detailed issue reporting
/war-room
war-room
Convene a multi-LLM expert panel to pressure-test strategic decisions with adversarial review and reversibility assessment.
/visualize
visualize
Generate visual diagrams of codebase structure using Mermaid Chart MCP rendering.
/ai-hygiene-audit
ai-hygiene-audit
Audit codebase for AI-generated code quality issues (vibe coding, Tab bloat, slop)
Implementation of Podlite markup language
13 views 0 likesOpen-source AI video workbench. Bring any model or your local ComfyUI, and let Claude Code / Codex / Cursor direct it over MCP — storyboard, references, generat…
15 views 0 likes《深入理解 AI Agent:设计原理与工程实践》(李博杰 著)开源主仓库:全书正文、编译版 PDF 与按章配套代码
8 views 0 likesDistilly — Distill how they think into reusable Skills for any Agent or Bot. Formerly Colleague Skill(原同事 Skill).
16 views 0 likes本地优先的类飞书 Markdown 编辑器,内置可审改的 AI 助手 | Local-first WYSIWYG Markdown editor with a reviewable AI agent
14 views 0 likesA lightweight all-in-one terminal with 20+ protocols — SSH, RDP, SFTP, databases, Kubernetes and more. With a built-in autonomous AI Agent that plans and runs m…
27 views 0 likes一款专注于桌宠方向的AIAgent。特点是一键安装、功能齐全、极低开销、完全暴露上下文、全功能插件化、AI自主插件开发、永久唯一会话、类游戏引擎交互策略。具有极高的扩展性和拟人程度上限,非常适合想长期培养和自定义需求高的用户。
11 views 0 likesControl Gmail, Google Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Search & Drive with AI - Comprehensive Google Workspace MCP Server & CLI Tool
14 views 0 likes一个先接住情绪、再分析关系并给出可执行策略的 Codex 恋爱军师,内置心理、法律、社会、人文、哲学、婚姻家庭与性学知识库,支持多元关系。
11 views 0 likesAI-powered SRE platform — read-only infrastructure diagnostics with deep investigation, security governance, and team collaboration
27 views 0 likesAn open-source AI desktop companion inspired by Cyrene, combining immersive Chat, personalized long-term memory, and an agentic Work mode.
13 views 0 likesA local-first AI agent with persistent memory, emotional intelligence, and a peer-to-peer skills economy.
15 views 0 likesThe open-source, multi-agent alternative to Claude Tag. @ any agent, wherever work happens, your agents work alongside your team and each other, learning as the…
27 views 0 likesSimple LLM service identification - translate IP:Port to Ollama, vLLM, LiteLLM, or 60+ other AI services in seconds
14 views 0 likes🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
15 views 0 likesClaude in Chrome, reverse-engineered and open-source. No domain blocklist. Any Chromium browser. Same 18 MCP tools, same performance.
14 views 0 likesAgent-native flight & hotel search and booking — MCP server, CLI, and Python/JS SDKs. Hundreds of airlines plus the major booking sites, with per-flight reliabi…
19 views 0 likesOpen-source desktop AI agent for tools, files, knowledge, workflows, and real deliverables.
13 views 0 likesOpen-source AI job search: scan job portals, evaluate listings into a structured A-H report with a global 1-5 score, tailor your CV, track applications — runs l…
25 views 0 likesPrivacy-first Codex skill for discovering, validating, completing, and tracking job applications
14 views 0 likes