LLM Mart Basic
@llm-mart · Joined Jun 2026
Deploy an AI legal operations agent for contract review, regulatory monitoring, policy enforcement, audit preparation, and document management. Complete Hermes configuration blueprint.
Deploy an AI marketing agent for SEO monitoring, campaign analytics, content performance, competitive intelligence, and social scheduling. Complete Hermes blueprint with cron and connectors.
Deploy an AI research agent for competitor monitoring, market intelligence, academic literature reviews, patent tracking, and news aggregation. Complete Hermes configuration blueprint.
Deploy an autonomous Hermes sales agent for lead qualification, pipeline management, outreach sequences, and daily CRM reporting. Complete configuration blueprint with cron schedules.
Deploy an AI customer support agent for ticket triage, knowledge base search, response drafting, SLA monitoring, and trending issue detection. Complete Hermes configuration blueprint.
Recommend AND run open-source AI tools, agents, Claude Code / Codex skills, and MCP servers for any stage of a literature review — searching, reading, extracting, synthesizing, screening, citation-checking, and paper writing. Use when the user asks "what tool should I use to..."
Orchestrate many forge runs at once: analyze which tasks collide on the same files, schedule the colliding ones sequentially, and run the rest in parallel worktrees at the right model tier and review depth. Use when the user runs /blacksmith-orchestrate or asks to ship several is
Brainstorm UI/UX changes into an approved design through interactive browser proposals rendered in the project's real design language. Option clicks assemble a response prompt copied to the user's clipboard. Use when the user runs /blueprint or wants to brainstorm, redesign, or v
Forge an issue, ticket, or PR into a shipped fix: propose a plan, get it approved, then implement, review, and refactor. Use when the user runs /forge or asks to investigate, fix, resolve, triage, or solve one. See Parameters for modifier flags.
Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the `td` CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.
Guide for adding new CLI commands or subcommands to todoist-cli. Use when implementing new SDK endpoints, adding subcommands to existing command groups, or extending CLI functionality.
Guide for adding new CLI commands or subcommands to todoist-cli. Use when implementing new SDK endpoints, adding subcommands to existing command groups, or extending CLI functionality.
Use when composing an ask_user_question round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
Use this BEFORE any creative or feature work: building a new feature, adding functionality, changing behavior, or making a nontrivial design decision. Turns the user's request into a validated design — recorded as a spec-graph task-spec — before any implementation. Do not skip th
Use FIRST when any new piece of work arrives — a request, feature, change, fix, question, or idea — before starting on it or choosing an approach. Not for continuing work already routed to a workflow skill.
Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced proj
Use whenever asked to set up, onboard, initialize, or spec a project — the front door when the workspace has no spec graph yet (brand-new or an existing codebase); also seeded by the app's Set-up-project card (/skill:setting-up-a-project). Not for feature work in an already-specc
Use when finished work needs to ship as a pull request, or when the ask is about a PR — creating one, bringing it up to date, adding screenshots, watching its checks, or addressing its review comments. Not for reviewing a PR you are not shipping.
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instea
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
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.
/show-ticket
Show ticket
Display comprehensive ticket information including history, actions, and related entities
/sla-dashboard
Sla dashboard
View SLA status across tickets, including approaching breaches and at-risk tickets
/update-ticket
Update ticket
Update fields on an existing HaloPSA ticket including status, priority, and assignment
/create-deal
Create deal
Create a new deal in HubSpot with company association
/log-activity
Log activity
Log a note or create a task on a HubSpot contact, company, or deal
/lookup-company
Lookup company
Find a HubSpot company by name or domain and show associated contacts and deals
/pipeline-summary
Pipeline summary
Summarize the HubSpot deal pipeline - deals per stage, total value, and expected close dates
/search-contacts
Search contacts
Search HubSpot contacts by name, email, or company
/search-deals
Search deals
Search HubSpot deals by name, stage, or company
/find-company
Find company
Find a company in Hudu by name
/get-password
Get password
Retrieve a password from Hudu (with security logging)
/lookup-asset
Lookup asset
Find an asset in Hudu by name, hostname, serial number, or IP address
/search-articles
Search articles
Search Hudu knowledge base articles by keyword or phrase
/agent-inventory
Agent inventory
List and filter Huntress agents across organizations
/billing-report
Billing report
Generate a Huntress billing summary for a period
/incident-triage
Incident triage
Triage open Huntress incidents by severity
/investigate-incident
Investigate incident
Deep dive investigation into a specific Huntress incident with remediations
/org-health
Org health
Organization health check covering agents, incidents, and escalations
/resolve-escalation
Resolve escalation
Review and resolve a Huntress escalation
/compliance-report
Compliance report
Generate an ImmyBot software-compliance scorecard for a tenant or the whole fleet
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…
11 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