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.
/lineage-discovery
Lineage discovery
Discover testnet↔mainnet subnet lineage from repo configs and open a PR for review (pass --dry-run to report only)
/capture
capture
Triage raw inbox notes into reviewed repository destinations without deleting their sources.
/clean-ai-writing
clean-ai-writing
Audit and rewrite content to remove AI writing patterns
/content-shipped
content-shipped
Log a completed piece of content to content/log.md after the user confirms it was published.
/dream-apply
dream-apply
Validate a dream artifact, review each proposal, and apply only individually accepted changes.
/dream
dream
Run a curator pass against the validated memory directory and produce a proposal artifact.
/end
end
End a session — log what happened, update state and the decision log, propose memory updates, and check for uncommitted or unpushed work
/find-context
find-context
Find relevant context files by topic. Use when you need to load files for a topic without a slash command, or when a task spans multiple domains.
/migrate-gemini
migrate-gemini
Inventory and migrate selected Gemini CLI workflows with dry-run review and parity checks.
/mine-gemini-workflows
mine-gemini-workflows
Find repeated workflows in selected Gemini CLI sessions and draft portable skills after review.
/reconcile
reconcile
Scan multi-session drift and offer individually reviewed fixes only after explicit approval.
/recover
recover
Scan orphaned worktrees and stale branches, then offer explicit approval-gated cleanup.
/setup
setup
Guided onboarding or import for durable workspace context
/start
start
Start a session — load state files, flag staleness, and give a briefing on current priorities, deadlines, and blockers
/today
today
Create a morning heartbeat from repository state and update the local heartbeat log.
/update
update
Mid-session checkpoint — append progress to today's session log and update state files if a priority shifted, without ending the session
/distribution-audit
distribution-audit
Maintainer-only. Find every file that would newly ship to adopters, classify each one against the written distribution-boundary categories, default to withhold on no clean match, and ask the maintainer only where the taxonomy does not settle it. Drives the release CLI, which refuses to produce a manifest until every shipping file has an answer.
/gaia-audit
gaia-audit
Audit memory, wiki, and auto-loaded files for duplication, conflicting instructions, and stale content. The default path researches, then asks you a single Apply / Discuss / Decline question; on Apply it applies the report, files any out-of-scope problem as a tech-debt issue, then commits, opens a PR, and merges it on a main-branch run like /update-deps. Pass --apply to re-run the apply-and-publish stage against the most recent report.
/gaia-debt
gaia-debt
Fix the tech-debt backlog, a single issue or a recommended related batch, highest severity then oldest first, on a fresh isolated branch through the audit gate, closing the issue(s) on merge. Pass `list` to see the ordered backlog, `why <issue-number>` to explain the recommendation, or a bare `<issue-number>` to fix that issue directly.
/gaia-fitness
gaia-fitness
Health-check and auto-heal this project's Claude integration, triage, heal, verify, and report an F-to-A+ grade.
AI coding platform for teams
20 views 0 likesAI Multi-Agent Framework in .NET
14 views 0 likesProduction-ready code examples for Telnyx AI Communications Infrastructure — Voice AI, SMS, SIP, and IoT APIs
12 views 0 likesUltraGameStudio - AI coding agent for game development: engine workflows, gameplay code, and asset generation.
12 views 0 likes🦞 ResearchClawBench: Evaluating AI Agents for Automated Research from Re-Discovery to New-Discovery
12 views 0 likesThe context-aware model router that learns & adapts to your long-horizon coding agent workflows. Lightweight & extensible, works with any harnesses, any models,…
20 views 0 likesOpen-source sandboxes where coding agents build and deploy. Spin up isolated environments where Claude Code, Cursor, and other agents code and deploy software.
24 views 0 likesNative desktop UI for Claude Code with orchestration, streaming, background agents, and multi-provider support. Built with Tauri + React.
22 views 0 likesOpenCode mobile client via Telegram: run and monitor AI coding tasks from your phone while everything runs locally on your machine. Scheduled tasks support.
17 views 0 likesTerminal session manager for AI coding agents. One TUI for Claude, Gemini, OpenCode, Codex, and more.
23 views 0 likesExposes internet search tools for use by LLM-backed Assist in Home Assistant
15 views 0 likesTemplates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs
8 views 0 likesVersus Incident is the self-hosted AI SRE agent. It learns what your system normally look like and escalates only what is new or unexpected issues — routing to…
14 views 0 likesBrowser-native side panel for Hermes Agent — connect web context to your local Hermes runtime.
6 views 0 likesAgentic-friendly CLI generator for APIs: turn Swagger, OpenAPI, and google.api.http protos into single-binary CLIs with catalogs and generated Skills.
10 views 0 likesOpen-source agent platform for Global × China enterprises — wire every system through one agent core. Self-hosted, any LLM.
7 views 0 likesOfficial python implementation of UTCP. UTCP is an open standard that lets AI agents call any API directly, without extra middleware.
11 views 0 likesAn agent small enough to run anywhere. A minimal agentic runtime in C — ~380 lines, 54KB binary, ~2MB RAM. A skill file + an LLM + a shell loop, no framework.
10 views 0 likesAgentiLoop Agent! An Autonomous Agentic Agent for Mac, and exclusive Apple only harnesss. Suppprtd automation, scripting, coding, build anything and more. Power…
10 views 0 likes微信公众号 AI 运营助手 | 选题、写稿、审稿、排版、配图、发布全流程 Skill,支持 OpenClaw / Claude Code / Cursor / Codex
17 views 0 likes