LLM Mart Basic
@llm-mart · Joined Jun 2026
Audit Whetstone skills, agents, and commands when asked for a plugin quality or consistency audit.
Investigate negative session feedback for a Whetstone skill when asked to diagnose its failures.
Evaluate Whetstone skills from session evidence when asked to compare procedure-following results or optimization candidates.
Revise and evaluate a Whetstone skill when asked to evolve or optimize that skill.
Prune stale Whetstone sync decision entries when asked to clean the sync log.
Run the Whetstone release workflow when explicitly asked to release this plugin.
Prepare or run Whetstone SkillOpt optimization when asked to optimize a process skill using SkillOpt.
Compare Whetstone with reference repositories when asked to sync cross-repository improvements.
Triage Whetstone pull requests when explicitly asked to group, label, and review open PRs.
Author a new Whetstone plugin skill when asked to write a skill without upstream skills.sh sources.
Fetches top-rated skills from skills.sh, analyzes them, and synthesizes one token-efficient skill combining the best elements. Use when the user asks to "distill skills for X", "find and combine skills for X", "synthesize skills", "merge skills", "make a skill for X from skills.s
Performs two-stage code reviews (spec compliance, then code quality) with severity-ranked findings. Use when asked to "review code", "review this PR", "check this diff", "review before merge", or mentions reviewing, auditing, or critiquing code changes, pull requests, or diffs.
Systematic root-cause debugging: reproduce, investigate, hypothesize, fix with verification. Use when asked to "debug this", "fix this bug", "why is this failing", "troubleshoot", or mentions errors, stack traces, broken tests, flaky tests, regressions, or unexpected behavior.
Defensive Bash scripting for Linux: safe foundations, argument parsing, production patterns, ShellCheck compliance. Use when writing "bash script", "shell script", "linux automation", "system script", "cron job", "deployment script", "CLI tool in bash", or "automate with bash".
Manages project documentation: AGENTS.md, README.md, and CONTRIBUTING.md. Use when asked to "update README", "update agents", "init agents", "create AGENTS.md", "update AGENTS.md", "update CONTRIBUTING", "update context files", or "init context". Not for general markdown editing.
Enhanced reasoning patterns via slash commands (/think, /verify, /adversarial, /edge, /compare, /confidence, /budget, /constrain, /json, /flip, /assumptions, /tensions, /analyze, /trade) or natural language ("argue against", "what could break", "show reasoning", "deep review", "m
Node.js backend patterns: framework selection, layered architecture, TypeScript, validation, error handling, security, production deployment. Use when building REST APIs, Express/Fastify servers, microservices, or server-side TypeScript.
Modern PHP 8.2+ and Laravel patterns: architecture, Eloquent, queues, Pest testing. Use when asked to "write PHP", "build a Laravel app", "fix Eloquent query", "add a queue job", "write a Pest test", or mentions PHP, Laravel, Eloquent, Blade, artisan, or migrations.
Pine Script v6 patterns: syntax rules, performance, debugging, backtesting, visualization. Use when asked to "write a Pine Script", "create an indicator", "build a strategy", "fix Pine code", or mentions PineScript, TradingView, indicator, strategy, or backtest.
Software implementation planning with file-based persistence (task_plan.md, findings.md, progress.md). Use when asked to "plan", "break down this feature", "implementation plan", or starting complex tasks needing >5 tool calls. Apply proactively before non-trivial coding.
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.
/chain
Chain
Run an ad-hoc ordered chain of pm-skills with shared context (ephemeral; routes to the pm-workflow-orchestrator)
/workflow-customer-discovery
Workflow customer discovery
Run the Customer Discovery workflow (research -> JTBD -> opportunities -> problem)
/workflow-design-sprint
Workflow design sprint
Run the Design Sprint workflow (5-day prototype-and-test arc producing a Decider's build/iterate/pivot/stop call)
/workflow-feature-kickoff
Workflow feature kickoff
Run the Feature Kickoff workflow (problem -> hypothesis -> PRD -> stories)
/workflow-foundation-sprint
Workflow foundation sprint
Run the Foundation Sprint workflow (2-day strategic-alignment arc producing a Founding Hypothesis)
/workflow-foundation-to-design
Workflow foundation to design
Run the end-to-end Foundation Sprint + Design Sprint workflow with narrative handoff
/workflow-post-launch-learning
Workflow post launch learning
Run the Post-Launch Learning workflow (instrumentation -> dashboard -> results -> retro -> lessons)
/workflow-product-strategy
Workflow product strategy
Run the Product Strategy workflow (competitive analysis -> stakeholders -> opportunities -> solution -> ADR)
/workflow-sprint-planning
Workflow sprint planning
Run the Sprint Planning workflow (refinement -> stories -> edge cases)
/workflow-stakeholder-alignment
Workflow stakeholder alignment
Run the Stakeholder Alignment workflow (stakeholders -> problem -> solution -> launch)
/workflow-technical-discovery
Workflow technical discovery
Run the Technical Discovery workflow (spike -> ADR -> design rationale)
/c-one
C one
Placeholder command file for the WS-T9 dual-shell parity smoke. No count phrases.
/minutes-brief
Minutes brief
Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.
/minutes-cleanup
Minutes cleanup
Manage old recordings — find large files, archive old meetings, delete processed originals. Use when the user says "clean up recordings", "how much space are meetings using", "delete old recordings", "archive meetings", "manage meeting storage", or asks about disk space from minutes.
/minutes-copilot
Minutes copilot
Start and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal. Use only for explicit Coach or HUD lifecycle requests such as "start Minutes Coach", "open the Coach HUD", "pause Minutes Coach", "resume Minutes Coach", "Minutes Coach status", or "stop Minutes Coach". Do not use for requests that explicitly ask the current terminal agent to watch or strategize; those belong to minutes-live-sidekick. An ambiguous request such as "coach me live" requires one short surface clarification and must not automatically start Coach.
/minutes-debrief
Minutes debrief
Post-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.
/minutes-graph
Minutes graph
Policy-safe relationship rankings, commitments, aliases, person profiles, and topic research. Always use Minutes' bounded native CLI surfaces; never build or read a durable graph cache.
/minutes-ideas
Minutes ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
/minutes-ingest
Minutes ingest
Extract facts from meetings and update your knowledge base — person profiles, chronological log, and index. Use when the user asks "ingest my meetings", "update my knowledge base", "extract facts from meetings", "sync meetings to wiki", "backfill knowledge", or wants their PARA/Obsidian/wiki profiles updated from conversation data.
/minutes-lint
Minutes lint
Health-check your meeting knowledge for contradictions, stale commitments, and decision conflicts. Use when the user asks "any conflicts in my meetings", "check for stale action items", "lint my meetings", "consistency check", "are there contradictions", or wants to audit their decision history.
Ultra-lightweight, open-source, self-hosted personal AI agent framework in Python with WebUI, tools, memory, MCP, multi-agent workflows, automation, and chat ap…
29 views 0 likesGovernance framework for AI coding agents. It runs them through a five-step workflow (plan, build, review, test, ship) where no step counts as done without evid…
17 views 0 likesUltimate Multi-Agent OS for Autonomous AI NPCs 2026
15 views 0 likesPersonal AI Agent Hub 2026 — Build Your 24/7 Autonomous Assistant
26 views 0 likesProven 2026 Multi-Agent AI Review System – Verdict-Driven Quality Control
29 views 0 likesSlash API Batch: Cut AI Costs by 50% in 2026
16 views 0 likesWeb dashboard for Hermes Agent — multi-platform AI chat, session management, scheduled jobs, usage analytics
19 views 0 likesAgent Skills for Solopreneurs
31 views 0 likesAirLLM dramatically reduces inference memory usage, letting 70B large language models run on a single 4GB GPU card
144 views 0 likesZero, your trustworthy AI teammate for real work.
16 views 0 likes一套 DSH runtime,Desktop、Web 与 TUI 三种开发体验。
12 views 0 likesOpen-source operational advisor for ClickHouse — real-time monitoring plus AI-driven index/partition/materialized-view recommendations.
17 views 0 likes⚙️ TypeScript Style Guide and Agent Skill. A concise set of conventions and best practices for consistent, maintainable code.
28 views 0 likesFramework for AI agents to build and maintain a digital brain through Obsidian wiki
17 views 0 likesApache Maka (Incubating) is a local-first AI agent workspace. Model messages, tool calls, tool results, permission decisions, and termination events are recorde…
25 views 0 likesNeo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inhabits live apps via Neural Link, Active H…
25 views 0 likesAgentic development harness for Claude Code — SPEC-driven plan/run/sync, TRUST 5 quality gates, model+effort routing, and Claude×GLM multi-LLM cost control. Sin…
19 views 0 likesNocoBase is an open-source AI + no-code platform for building business systems fast. Instead of generating everything from scratch, AI works on top of productio…
27 views 0 likesAn open-source AI coding agent that lives in your terminal.
29 views 0 likesPawWork — free, open-source desktop AI agent for macOS and Windows. Alternative to Codex App and Claude Cowork. BYOK with 75+ providers, ChatGPT OAuth, local mo…
16 views 0 likes