LLM Mart Basic

Event concept development, logistics planning, vendor coordination, budget management, and timeline creation

Professional communication, email management, stakeholder coordination, follow-up systems

Executive operations, calendar management, travel coordination, expense workflows

Client advisory communication with fiduciary tone, compliance-friendly language, and plain-language financial education

Financial planning knowledge for retirement, education, estate, tax, and insurance needs analysis

Regulatory change monitor — current SEC, FINRA, IRS landscape with effective dates; flags advice impacted by recent changes

AI vendor billing-model fluency — auto-activates when normalizing, comparing, or forecasting AI spend across seats, usage, credits, and reserved capacity

AI unit-economics discipline — auto-activates when evaluating whether AI spend is worth it, pushing from tokens and requests to cost-per-successful-outcome

Weekly and monthly operating rhythm for solo founders — retros, three-bet weekly plans, honest monthly updates, and metric discipline

Scope and shipping guardrails for solo founders — cutting v1 to the one feature that tests the riskiest assumption, and a validation check before anything goes public

Worker-facing safety writing conventions — auto-activates when drafting toolbox talks, procedures, signage, alerts, or any safety material a crew has to read and act on

Safety-documentation guardrails — auto-activates on incident, inspection, recordkeeping, or regulatory work to keep drafts factual, uncertified, and never in front of a reporting obligation

Map clinical study data to FDA Substantial Equivalence and clinical performance criteria for AI-enabled medical devices

Determine the appropriate FDA premarket pathway for an AI-enabled medical device based on intended use and predicate landscape

HR operations, employment law, policy writing, compliance frameworks

Reskilling pathway mapper — given a displaced role, map AI-resistant adjacent roles and learning paths

Talent acquisition, job descriptions, DEI-inclusive language, onboarding

Insurance client relationship management, retention strategies, and cross-selling approaches

Insurance policy analysis across P&C, life, health, and commercial lines

Client management expertise for interior design proposals, scope management, and project communication

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.

One-line reliability verdict (OK / DEGRADED / FAILING) for Claude Code usage

Print a quick SLO snapshot — completion rate, tool success rate, and error rate

Generate an evidence-backed CCAM executive, cost, reliability, or workflow report.

List live and persisted CCAM-launched Claude Code and Codex runs

Search Agent Monitor sessions by cwd, model, or status and print the top matches.

List the N most recent Claude Code sessions from the Agent Monitor.

Summarize one Agent Monitor session by id — header plus a concise transcript recap.

Print the orchestration DAG edges (parent→child subagents) for a session.

List recent Workflow-tool fleet runs with status and agent counts.

Summarize the workflow intelligence for a session — stats, complexity, and top patterns.

Run broadcast on a distilled Raw — update related existing pages conversationally

Distill raw session records into refined Notes and Projects

Save knowledge to the cortex vault (Notes or Projects) and update index

Initialize cortex vault — set up config, vault structure, and rebuild index

Manually search the cortex vault (Notes, Projects, Raw) for existing notes

Create, resume, or clear a session hand-off baton (one per work line)

Command → Agent → Skill orchestration for end-to-end feature development.

Command → Agent → Skill orchestration for investigating and fixing bugs.

Brief the CEO: coordinate with the peer CTO and start or resume a founder project across 8 departments and 54 skills

Configure an optional active team profile in three short questions

Open-source, self-hosted AI media server. One server replaces your entire media stack, with a web app, native iPhone app, and an AI agent that gets things done.…

A curated list of tools built for Jev — TypeSafe AI's System One model for typed decisions.

🦦 Crayotter: A Multimodal AI-Agent for Video-Editing, Video-Composing, and Video Production. Powered by Multimodal LLMs for autonomous Text-to-Video agentic fr…

Webextension tool for Odoo