LLM Mart Basic

DSM-5 diagnostic criteria, evidence-based therapy modalities, treatment planning, and progress measurement

Suicide risk assessment using the Columbia Protocol (C-SSRS) and SAFE-T framework — auto-prompts when warning indicators appear

Empathetic clinical writing, health literacy adaptation, and crisis sensitivity

Trauma-informed language guardrails — flag re-traumatizing phrasing and suggest SAMHSA-aligned alternatives

Professional trade communication, estimate presentation, warranty explanation, and upsell framing

Building code awareness, permit references, industry terminology for plumbing, electrical, HVAC, and safety documentation

Empathetic, plain-language communication for treatment discussions, costs, prognosis, and end-of-life care

Clinical documentation, diagnostics, pharmacology, treatment protocols, and species-specific medical knowledge

Produces Alon's design-doc system before code: SOURCE_OF_TRUTH.md, ARCHITECTURE_ROADMAP.md, TODO_WORKFLOW.md, CLAUDE.md, plus a modular docs/architecture set for larger projects. Model first: data and invariants before framework, every invariant enforced at two boundaries, failur

Convenes a panel of opinionated Claude advisors, each with a distinct mandate and a forbidden move so they genuinely diverge, then a Chairman synthesis that commits to one recommendation with the decisive tradeoff and the strongest dissent named.

Forces the laziest solution that actually works: YAGNI, reuse before new code, stdlib before custom, native platform before dependencies, one line before fifty. Three levels — lite (name the lazier alternative, build what's asked), full (ladder enforced, default), ultra (YAGNI ex

Turns a vague ask into a rigorous, grounded, token-efficient prompt for another agent or LLM: role and objective, testable done criteria, anti-hallucination and anti-tokenmaxing rules baked into the generated prompt itself, and strict agent discipline for coding-agent hand-offs.

Local, free, multi-specialist review of a diff: parallel Claude subagents for correctness, security/trust boundaries, data/perf, architecture-altitude, ponytail-simplicity, and tests/failure-paths, each non-trivial finding adversarially verified before being kept, deduped, and ra

Preflight sync and situational brief before repo work: fetches origin, reports ahead/behind divergence (with a no-upstream/detached-HEAD fallback), recent commits, open PRs and issues touching the work, and dirty-tree warnings, then names one recommended first action. Read-only b

Write and publish a new blog post for the skillfold site (site/blog/). Use whenever asked to write a blog post, cover a news story about the agent tooling ecosystem, announce a feature rollout, publish the next post from the queue, or when the weekly blog automation runs. Covers

Review code for correctness, clarity, and security.

Write clean, correct, production-quality code.

Evaluate trade-offs, document options, and justify recommendations.

Read, create, edit, and organize files and directories.

Work with GitHub branches, PRs, issues, and reviews via the gh CLI.

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.

Use MCP Inspector to connect to local or remote servers, inspect capabilities, call tools, read resources, test prompts, and diagnose failures before release.

Build an MCP server in TypeScript with focused tools, validated schemas, local and remote transports, Inspector tests, and production security controls.

Generate API documentation from code

Update or generate YAML documentation for SQL models with proper descriptions and tests

Configure end-to-end testing suite

Generate accurate project time estimates

Analyze and explain code functionality

Explain how tasks in an issue were implemented with detailed breakdown

Search and locate tasks across all orchestrations using various criteria.

Apply the Five Whys root cause analysis technique to systematically investigate issues

Analyze and fix a GitHub issue with comprehensive testing and verification

Fix a specific issue or problem with the given identifier or description

Fetch unresolved comments for current branch's PR and fix them

Generate and analyze future scenarios with plausibility scoring, trend integration, and uncertainty quantification.

Auto-generate API reference documentation

You are tasked with generating a technical work log comment for a Linear issue based on recent git commits.

Generate comprehensive test cases automatically

Generate comprehensive test suite for $ARGUMENTS following project testing conventions and best practices.

Show detailed git repository status

Deploy critical hotfixes quickly

Verify repository is in working state by running CI checks and fixing issues

Design and implement caching solutions

PiG (Pi in Go) is a faithful Go port of upstream Pi, the TypeScript codebase behind the Pi coding agent. It is a parity-bound translation, not a rewrite: upstre…

An AI Agent that lives in your pocket. Local-first and privacy focused.

Unofficial skill that teaches coding agents to build with TypeSafe AI's Jev: typed decisions, calibrated confidence, and prior art from 150+ community projects.

Adaptive Test-time Learning and Autonomous Specialization

Prediction-market trading engine — Wang Transform pricing on 291K+ contracts; paper-traded across Kalshi · Polymarket · Solana DFlow (Jito bundles) · 633 tests

Knowledge Management for Humans and Agents

Open-source Claude Cowork / Codex / WorkBuddy alternative — a local-first AI office agent that turns one request into real PPTX, DOCX, XLSX and HTML files. Runs…

DeepAgent Code: AI coding agent with persistent memory and control plane