LLM Mart Basic
@llm-mart · Joined Jun 2026
Pricing strategies, proposal writing, contracts, client management, and studio operations
Shot composition guidance, album narrative structure, and brand photography direction
Musculoskeletal and neurological rehabilitation expertise for physical therapy documentation and clinical reasoning
AI infrastructure and governance readiness — auto-activates when scoping or launching AI features
Competitive intelligence for AI product launches — auto-activates when benchmarking AI features, pricing, or positioning
Prompt-engineering expertise for designing test cases, edge cases, adversarial inputs, and iterating on prompts based on eval results
Skill and prompt benchmarking expertise for measuring latency, accuracy, token cost, and token-budget compliance across variants
Professional board reporting, financial presentation, compliance documentation, and resident communication
Property management expertise including fair housing law, lease administration, HOA governance, and vendor management
Real estate client relationship communication for buyers, sellers, and leads
MLS listing writing, social media marketing, and Fair Housing Act compliance for real estate
Pattern recognition for LLM-generated resume text — sentence length variance, em-dash density, and generic accomplishment phrasing
Employer branding expertise for EVP communication, DEI-inclusive language, and candidate experience
Auto-activates ghost-job red-flag detection on job postings, ATS pipeline indicators, and pay-transparency gaps
Talent acquisition expertise for sourcing strategy, candidate evaluation, structured hiring, and employment law awareness
Professional persuasive writing, personalization, urgency without pressure, and CTA best practices
Consultative selling, MEDDIC/BANT frameworks, value-based positioning, objection handling, and pipeline management
Auto-adapts tone to platform norms — LinkedIn professional, X witty, TikTok conversational, Threads candid
Social media metrics, analytics interpretation, and performance reporting expertise
Platform-specific social media content expertise and content creation best practices
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.
/health
Health
One-line reliability verdict (OK / DEGRADED / FAILING) for Claude Code usage
/slo
Slo
Print a quick SLO snapshot — completion rate, tool success rate, and error rate
/report
Report
Generate an evidence-backed CCAM executive, cost, reliability, or workflow report.
/runs
Runs
List live and persisted CCAM-launched Claude Code and Codex runs
/find-session
Find session
Search Agent Monitor sessions by cwd, model, or status and print the top matches.
/recent
Recent
List the N most recent Claude Code sessions from the Agent Monitor.
/replay
Replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
/dag
Dag
Print the orchestration DAG edges (parent→child subagents) for a session.
/runs
Runs
List recent Workflow-tool fleet runs with status and agent counts.
/workflow
Workflow
Summarize the workflow intelligence for a session — stats, complexity, and top patterns.
/broadcast
broadcast
Run broadcast on a distilled Raw — update related existing pages conversationally
/distill
distill
Distill raw session records into refined Notes and Projects
/evolve
evolve
Save knowledge to the cortex vault (Notes or Projects) and update index
/genesis
genesis
Initialize cortex vault — set up config, vault structure, and rebuild index
/query
query
Manually search the cortex vault (Notes, Projects, Raw) for existing notes
/takeoff
takeoff
Create, resume, or clear a session hand-off baton (one per work line)
/dev
Dev
Command → Agent → Skill orchestration for end-to-end feature development.
/investigate
Investigate
Command → Agent → Skill orchestration for investigating and fixing bugs.
/company
Company
Brief the CEO: coordinate with the peer CTO and start or resume a founder project across 8 departments and 54 skills
/onboard
Onboard
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.…
3 views 0 likesA curated list of tools built for Jev — TypeSafe AI's System One model for typed decisions.
3 views 0 likes🦦 Crayotter: A Multimodal AI-Agent for Video-Editing, Video-Composing, and Video Production. Powered by Multimodal LLMs for autonomous Text-to-Video agentic fr…
3 views 0 likesWebextension tool for Odoo
3 views 0 likes