LLM Mart Basic
@llm-mart · Joined Jun 2026
Everyday Rust engineering for Skill Doctor — errors, ownership, clippy, APIs, iterators. Use when writing or reviewing Rust that is not specifically about perf, unsafe, or YARA.
Nine non-negotiable Skill Doctor product invariants. Use when changing scan defaults, scoring, features, networking, LLM/MCP paths, CLI flags, or anything that could weaken determinism or additive-only behavior.
Rust performance and memory optimization for Skill Doctor L1. Use when making scans faster, reducing RSS or binary size, adding rayon/mmap, writing benchmarks, or discussing the §7.3 targets (2000 skills/min, 40MB, 12MB binary, 15s cold).
How to write Skill Doctor tests — unit, integration, CLI, fixtures, determinism, additive-only. Use when adding tests, fixtures, snapshots, or changing cargo test layout.
Cargo workspace layout, crate boundaries, and dependency policy for Skill Doctor. Use when creating crates, editing Cargo.toml, adding modules, moving types, or adding a dependency.
Rules for unsafe Rust and the L3 microVM sandbox. Use when adding unsafe blocks, FFI, sandbox features, differential replay, or canary credentials.
Author and compile YARA-X rules for SDTM-v1. Use when adding or changing detectors, rules/*.yar, rule IDs, or taxonomy mappings.
Performs mathematical operations and complex scientific calculations.
Builds and packages project artifacts.
Triage a PR's review comments, CI failures, and merge conflicts through the /age lens. Use when the user asks to address PR feedback, fix CI, or resolve conflicts. Do not use for a diff without a PR. Use /age instead.
Route an idea, path, pull request, issue, failure, question, or bare `/cheese` to the correct workflow skill. Use this skill for `/cheese`, routing requests, help requests, or opening messages without a named workflow skill.
Primarily the agent's internal-thinking skill — invoke it silently to model a problem, identify trade-offs, and decide what to do, BEFORE asking the user anything or dispatching another skill. Only treat this as a user-facing skill when the user has explicitly opted out of code w
Apply selected fixes from an /age report, findings list, or CI failure. Run the project gates and hand a clean result to /plate. Use when the user wants selected findings resolved. Do not use for review, test authoring, or direct publication.
Register the durable `cheese-durable` Hallouminate corpus. Repair the durable corpus when its configuration changes. Register the repository tenant. Repair the repository tenant when its configuration changes. Use this skill when the user requests durable corpus setup or repair.
Resolve Git merge, rebase, or cherry-pick conflicts through a structural merge cascade. Run mergiraf first, Git rerere second, and kdiff3 last. Use this skill when conflicts exist or Git shows an incomplete operation. Trigger phrases include "melt the conflicts", "resolve the reb
Turn a high-leverage design decision into an approved spec through grounded dialogue. Use it when a leverage trigger fires (auth, irreversible effects, concurrency, contracts, destructive ops, a new slice, a cross-slice dependency, an invariant gap) or when the user asks for a sp
Diagnose and fix a hard bug. Build a reliable reproduction, name the cause, add a regression test, and apply the minimum fix. Use when the user reports a bug, a failure, a flaky test, a performance regression, an error, or a wrong result whose cause is unknown. Use when the user
Turn finished local work into a commit, an ordinary pull request, or a pull request stack. Use this skill to commit changes or to publish a branch. Use it to open or update a pull request. Use it to create, sync, restack, or submit a pull request stack. You can also run /plate. T
Run the tests-only adversarial gate after `/cook`. Route bounded corrective Cook continuations. Use this skill when the user says "press the changes", "harden this", "press before /age", or "/press". Do not edit production code. Do not dispatch a global Cook repair from Press.
Retired — /ultracook no longer exists as a standalone skill. Any /ultracook invocation resolves to /cook, which now owns the single implementation pathway (including the fan-out mechanics this skill used to run). Use /cook instead.
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.
/drift-report
Drift report
Portfolio-wide Inforcer baseline drift report — every managed tenant's alignment vs its assigned baseline, classified aligned / semi-aligned / drifted and sorted drifted-first, with secure score
/tenant-posture
Tenant posture
Single-tenant Microsoft 365 posture snapshot from Inforcer — secure score plus alignment score, band, and the per-policy drift detail against the tenant's assigned baseline
/classify-email
Classify email
Get an Ironscales AI verdict on a raw email, then act on it with a remediation action
/triage-incidents
Triage incidents
Triage open Ironscales phishing incidents — list by status and severity, investigate, and remediate
/get-quote
Get quote
Get a Kaseya Quote Manager quote with its sections and line items
/get-sales-order
Get sales order
Get a Kaseya Quote Manager sales order with its lines and payments
/list-quotes
List quotes
List Kaseya Quote Manager quotes, optionally scoped to a recent window
/add-note
Add note
Add a note or comment to an existing Autotask ticket
/check-contract
Check contract
View contract status, entitlements, and remaining hours for a company or specific contract
/check-pricing
Check pricing
Check pricing details for an Autotask product or service from price lists
/create-quote
Create quote
Create a new Autotask quote with line items for products, services, and service bundles
/create-ticket
Create ticket
Create a new service ticket in Autotask PSA
/expenses
Expenses
Use this skill when working with Autotask expense reports - creating reports, adding expense items, searching by status or submitter, and tracking reimbursable and billable expenses
/lookup-asset
Lookup asset
Search for Autotask configuration items/assets by name, serial number, or company
/lookup-company
Lookup company
Search for Autotask companies by name, ID, or other attributes
/lookup-contact
Lookup contact
Search for Autotask contacts by name, email, phone, or company
/my-tickets
My tickets
List tickets currently assigned to you with optional filtering
/reassign-ticket
Reassign ticket
Reassign a ticket to a different resource or queue
/search-products
Search products
Search the Autotask product catalog for products, services, or inventory items
/search-tickets
Search tickets
Search for tickets in Autotask PSA by various criteria
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