LLM Mart Basic
@llm-mart · Joined Jun 2026
Use when recent resolved feedback may reveal a broader recurring defect pattern across the project surface. Not for source-level feedback collection: use feedback-sweep.
Use when one named review viewpoint must run fix cycles until a fresh reviewer finds nothing. Not for multi-viewpoint review or remote, credential, publish, deploy, or irreversible changes.
Use when the user invokes this skill to generate targeted questions proving the author understands the change's codebase effect. Not for reviewing the change: use review.
Use when asked to review a pull request, examine code changes, find bugs, or audit a branch, in standard or depth mode. Not for an iterative review-and-fix loop: use audit-project.
Use when the user wants a per-finding visual walk through a diff or PR. Not for written review reports: use review. Not for codebase tours: use show-me.
Use when implementation must be checked against an authoritative specification, or during PR review for spec drift against checked-in specs. Not for spec updates: use spec-driven-implementation.
Use when the user runs /browser-qa for report-only QA results without entering a fix loop. Not for remote, credential, publish, deploy, or irreversible changes.
Use when asked to reproduce, profile, or verify CLI/TUI behavior. Produces a deterministic transcript or profile proof with session cleanup. Not for CLI design advice, use cli-for-agents.
Use when asked to verify or reproduce browser or Electron UI behavior with before-and-after evidence and no leftover processes. Not for remote, credential, publish, deploy, or irreversible changes.
Use when asked to prove coverage, find missing cases, or enumerate state, decision, requirement, or behavior space. Not for round-based or single-property tests: use askme, property-test-authoring.
Use when a complete product needs production-like acceptance evidence against documented acceptance criteria. Not for single-component evaluation or evaluation without documented criteria.
Use when verification is looping, would re-run untouched code, or duplicates an established proof. Not for tasks that require source or remote-system changes.
Use when a test surface needs behavior-guarding coverage raised to a configured target with mutation kill evidence. Not for line-coverage inflation without mutation proof.
Use when asked to initialize, scope, estimate, configure, validate, or optimize a mewt, muton, or mutation testing campaign before execution. Writes the TOML config. Not for running it: use the mewt CLI.
Use when a mutation campaign leaves surviving mutants needing triage. Classifies each as false-positive, missing-test, genotoxic, or removable. Not for setup: use mutation-campaign-configuration.
Use when a product surface must be tested against extreme or hostile worlds. Not for design disputes: use possible-worlds. Not for remote, credential, publish, deploy, or irreversible changes.
Use when property-based testing, theorem proving, or formal proof tactics require zero unproven properties. Not for remote, credential, publish, deploy, or irreversible changes.
Operate explicit orchestrator, implementer, validator, and scribe roles through a caller-selected agent runtime. Triggers: "agent-native factory", "role-shaped agent panes", "persistent workers".
Use an explicitly selected AGY runtime for one provided packet or fresh validator context. Triggers: "agy", "antigravity", "AGY evidence".
Run one caller-supplied Codex command non-interactively and capture evidence. Triggers: "run Codex headless", "capture Codex evidence".
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.
/config-validate
Config validate
Validate application configuration with schemas, per-environment rules, runtime checks, and secure handling of sensitive values
/spark-preflight
Spark preflight
Preflight a DGX Spark system for an ML training or inference workload and emit env-report.json
/debug-trace
Debug trace
Set up debugging and tracing with remote debugging, distributed tracing, debug logging, profiling, and production diagnostics
/doc-generate
Doc generate
Generate API, architecture, code, and user documentation from a codebase and automate keeping it current
/error-analysis
Error analysis
Analyze and resolve errors across the full application lifecycle — from stack traces to distributed tracing — using systematic root-cause analysis and observability tools.
/error-trace
Error trace
Set up error tracking and monitoring — implement structured logging, configure alerts, and integrate with error tracking services for real-time error detection.
/multi-agent-review
Multi agent review
Coordinate specialized review agents in parallel or in sequence and synthesize their findings into one code review
/error-analysis
Error analysis
Analyze and resolve errors across the full application lifecycle — from stack traces to distributed tracing — using systematic root-cause analysis and observability tools.
/error-trace
Error trace
Set up error tracking and monitoring — implement structured logging, configure alerts, and integrate with error tracking services for real-time error detection.
/smart-debug
Smart debug
AI-assisted smart debugging — parse error messages, stack traces, and failure patterns to identify root causes and produce a fix with automated observability steps.
/code-migrate
Code migrate
Generate comprehensive migration plans and scripts for transitioning codebases between frameworks, languages, versions, or platforms with minimal disruption.
/deps-upgrade
Deps upgrade
Plan and execute safe, incremental dependency upgrades with minimal risk — including breaking-change migration paths and proper test verification.
/legacy-modernize
Legacy modernize
Orchestrate legacy system modernization using the strangler fig pattern with gradual component replacement
/component-scaffold
Component scaffold
Scaffold React and React Native components with TypeScript, tests, styles, and Storybook stories
/xss-scan
Xss scan
Scan React, Vue, Angular, and vanilla JavaScript code for XSS vulnerabilities and report fixes with secure coding examples
/full-stack-feature
Full stack feature
Orchestrate end-to-end full-stack feature development across backend, frontend, database, and infrastructure layers
/git-workflow
Git workflow
Orchestrate git workflow from code review through PR creation with quality gates
/onboard
Onboard
Create a role-specific onboarding plan for a new team member, from pre-arrival setup through the first 90 days
/pr-enhance
Pr enhance
Enhance a pull request with a generated description, review checklist, risk assessment, and test coverage report
/incident-response
Incident response
Orchestrate multi-agent incident response with modern SRE practices for rapid resolution and learning
AI agent orchestration kit for Windows, Linux/MacOS with Codex skills, hooks, routing rules and profiles for Claude, OpenCode, Cursor, Gemini and Windsurf.
1 views 0 likesSkills & reviewer agents for AI-first climate science — built and used by a PhD atmospheric scientist
4 views 0 likes出行路书工作流 skill:联网实查 + 多源交叉验证,产出可核验、能执行的旅行攻略。覆盖吃住行游拍避全维度,附美食情报卡、基准骨架与校验工具,支持一键部署在线版。
4 views 0 likesSelf-hosted AI code reviewer with indexed PR reviews, walkthroughs, vulnerability scanning, dependency graphs, custom rules, and a learning loop.
4 views 0 likes🧬 Extend EvoScientist with Installable Skill & Knowledge Packs
3 views 0 likesGive the agent a machine. Just not yours. Each AI coding agent gets its own isolated machine with root, Docker, and systemd - active defense detects and stops t…
3 views 0 likesAutomatic memory consolidation for OpenClaw agents — like sleep for your AI. Powered by MyClaw.ai
0 views 0 likes🗂 The essential checklist for modern web development, for humans and AI agents
1 views 0 likesDistribb CLI, Claude, Codex, Hermes, OpenClaw skill for AI-powered SEO. Write content with your own AI, publish through Distribb's backlink network.
3 views 0 likesOpen-source AI browser agent — type plain-language commands and Bah operates the web for you. Works with cloud AI (DeepSeek, Mistral, NVIDIA) or local Ollama mo…
3 views 0 likesDeepSeek Harness Desktop (dsh-desktop). EAC: Embracing All Creation (揽尽万象). Bundled Node.js runtime with full dsh-CLI kernel, one-click startup, 10 built-in UI…
2 views 0 likesUse your ChatGPT / Codex subscription with DeepSeek Harness via OAuth, with model access, usage quotas, search, and image generation — no API key or Codex CLI r…
3 views 0 likesLocal-first A-share research workbench for DeepSeek Harness: market dashboards, watchlists, valuation, four investor agents, versioned reports, and continuous p…
2 views 0 likesOpen-source video pipeline (clipper, AI video & more) — scout trends, clip long videos, generate captioned shorts, design motion graphics. Local-first, BYOK. AG…
3 views 0 likesDesktop app for the pi coding agent: streaming timeline, Git review with hunk staging, session tree, native UI for pi extensions. Windows · macOS · Linux. pi 编程…
4 views 0 likesZero-dependency browser video editor that AI agents can drive — JSON timeline, MCP + REST, live-reloading UI
3 views 0 likesPersonal Context Manager for Claude Code. Your life in walnuts.
1 views 0 likesFast way to switch between Claude Code configuration profiles
5 views 0 likesAutoClip|一个链接,一键出片。开源 AI 视频剪辑桌面工具,将播客、访谈、课程等长视频自动剪成短视频,生成字幕、封面和发布文案,适配抖音、小红书、TikTok、Reels 与 YouTube Shorts。Open-source AI video clipping & content repurposing.
4 views 0 likes