LLM Mart Basic

Analyzes SIEM alert pipelines for rule optimization, alert fatigue reduction, criticality scoring, asset-based prioritization, and correlation rule design using NIST CSF and detection engineering principles..

Maps the entire API surface of a codebase -- route definitions, middleware chains, auth requirements, request/response types, deprecated endpoints, orphaned endpoints, and cross-endpoint inconsistencies..

Analyzes mobile app binary size -- asset audit for unused images and font subsetting, code stripping with ProGuard and tree-shaking, on-demand resources, dynamic feature modules, and app thinning strategies..

Analyzes App Store and Play Store listing optimization -- keyword research, title optimization, screenshot conversion analysis, A/B testing setup, review sentiment analysis, competitor gaps, and localization coverage..

Analyzes apparel demand prediction systems for trend forecasting, size curve optimization, color and style analytics, sell-through rate tracking, and markdown optimization following CPFR collaborative planning and GTIN product identification standards..

Analyzes asset lifecycle planning systems for capital expenditure forecasting, replacement scheduling, total cost of ownership modeling, depreciation tracking, and facility condition assessments using IFMA standards and Facility Condition Index scoring..

Analyzes audit readiness systems for internal control testing, evidence collection workflows, statistical sampling methodology, audit finding documentation, and remediation tracking using PCAOB, ISA, and SOX compliance frameworks..

Generates backend or frontend engineering specs in structured Jira format with description, categorized acceptance criteria, routes, dev notes, and table schemas.

Analyze pharmaceutical batch production records for yield optimization, process parameter tuning, deviation trending, and cycle time reduction under cGMP compliance. Triggers: phrases: "optimize batch yield", "analyze batch records", "pharma manufacturing analysis".

Analyze behavioral segmentation systems for RFM scoring, cohort tracking, churn propensity, engagement scoring, persona clustering, and journey mapping using behavioral economics frameworks..

Analyze government benefits processing software for eligibility determination, application workflow efficiency, document verification, error rates, appeal tracking, multi-program coordination, and ADA/Section 508 compliance..

Analyze bookkeeping automation systems for transaction categorization, bank reconciliation, AP/AR efficiency, chart of accounts optimization, and month-end close using GAAP and double-entry accounting patterns..

Analyze packaging configurations for carton size selection, void fill minimization, palletization efficiency, sustainable materials, and total packaging cost reduction aligned with ISTA and ASTM D4169 standards..

Analyze budget allocation systems for departmental budgeting, variance analysis, rolling forecasts, zero-based budgeting, and capital allocation using FP&A frameworks and driver-based planning methodologies..

Analyze frontend bundle size, detect heavy dependencies, find duplicates, evaluate tree-shaking, recommend code splitting, and generate size budget configs. Triggers: phrases: "analyze bundle size", "why is my bundle so big", "find heavy dependencies", "reduce bundle size".

Generate a multi-channel abandoned cart recovery sequence — SMS at 15 min (98% open rate, 25-40% conversion) followed by email cadence at 1hr / 24hr / 72hr, plus optional push and retargeting touchpoints..

Analyze catastrophe modeling systems for natural disaster exposure, PML estimation, and reinsurance optimization. Use when: 'assess cat model', 'evaluate disaster exposure', 'review PML calculations', 'audit reinsurance program', 'check exposure data quality', 'analyze hurricane/

Audit an ecommerce checkout flow against the 2026 conversion playbook. Triggers: "checkout audit", "checkout optimization", "Shopify checkout", "Stripe checkout", "Apple Pay".

Analyze insurance claims workflow systems for intake optimization, adjudication rules, subrogation, litigation management, and settlement analytics. Triggers: 'audit claims process', 'review FNOL workflow', 'evaluate claims automation', 'check subrogation recovery'.

Analyze agricultural climate risk systems for weather impact modeling, crop insurance, drought/flood prediction, soil moisture, and carbon tracking. Triggers: 'assess crop climate risk', 'evaluate weather yield models', 'review crop insurance integration'.

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.

Daily standup: all 8 departments report on the current project in parallel

Identify skills injected where not needed, propose regex and description tightening

Draft X/Twitter announcement post (or thread) for the latest plugin release

Deep quality audit of all skills, agents, and commands for inconsistencies, gaps, duplication, and token waste

Analyze negative-signal sessions for a skill, identify failure patterns, propose and apply fixes

Eval all skills with sufficient data, rank by procedure-following score, identify candidates for optimization

Propose a skill revision and compare fresh executions under a frozen rubric

Prune stale entries from the whetstone sync decision log

Bump version, commit, push, mirror to ai-skills, and update local plugin

Run the SkillOpt process-skill optimizer (offline, local). Default prints the exact bare-terminal command (safe); --run executes it in-session (hardened + checkpointed).

Analyze reference repos and recommend skill/agent/command improvements based on cross-repo patterns

Triage all open PRs with parallel agents, label, group, and review one-by-one

Author a new skill from scratch with paired trigger fixtures and full validation. Use when adding a skill that has no upstream skills.sh source (discipline, meta, or internal-pattern skills).

Create Architecture Decision Records with format selection and lifecycle management

Score each of the 5 agent-native principles (parity, granularity, composability, emergent capability, improvement-over-time) against a codebase and report gaps

Explore requirements and approaches through collaborative dialogue before planning implementation

Create engaging changelogs for recent merges to main branch

Expand each section of a plan via parallel research agents that add framework specifics, library conventions, and concrete implementation steps

Post-ship documentation sync. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, and optionally bumps the version.

Record a video walkthrough of a feature and add it to the PR description

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