LLM Mart Basic
@llm-mart · Joined Jun 2026
Use this skill when you need to design functional test plans or cases for business flows, UI, data, and integrations; triggers include functional testing and functional test cases.
Use this skill when you need evidence-bounded repeat inputs, version/model/prompt factors, invariants, variance evidence, and comparison boundaries; triggers include LLM 一致性 and LLM consistency.
Use this skill when you need to design LLM evaluation datasets, judges, metrics, and human-review boundaries; triggers include llm evaluation design.
Use this skill when you need evidence-bounded claim-to-source relations, unsupported assertions, abstention, uncertainty, and evidence review; triggers include LLM 幻觉 and LLM hallucination.
Use this skill when you need to test LLM behavior, failure modes, and evidence-based quality boundaries; triggers include llm testing.
Use this skill when you need to analyze logs into evidence, timelines, anomalies, and follow-up hypotheses; triggers include log analysis.
Use this skill when you need to plan manual or exploratory testing with charters, heuristics, and session records; triggers include manual testing and exploratory testing.
Use this skill when you need to derive test candidates from input transformations and expected relations when a direct oracle is limited; triggers include 变形测试 and metamorphic test design.
Use this skill when you need to identify, contextualize, and investigate metric anomalies from observability evidence; triggers include metrics anomaly analysis.
Use this skill when you need to design mobile test plans for iOS or Android covering functionality, compatibility, performance, network, and security; triggers include mobile testing and app testing.
Use this skill when you need to review mock fidelity, contract alignment, over-mocking, and drift evidence; triggers include Mock 质量评审 and mock quality review.
Use this skill when you need to derive test-path candidates from sourced behavior, state, or process models; triggers include 基于模型的测试 and model-based test design.
Use this skill when you need evidence-bounded delegation, coordination, shared state, conflicts, ownership, termination, and traceability; triggers include 多 Agent 协作 and multi-agent coordination.
Use this skill when you need to interpret mutation operators, killed and survived mutants, and evidence limits; triggers include 变异测试分析 and mutation testing analysis.
Use this skill when you need to discover invalid, denied, failed, degraded, or unsafe-recovery scenarios from product evidence; triggers include negative scenario discovery.
Use this skill when logging, metrics, tracing, alerting, or SLO design needs an evidence-bounded review before implementation; triggers include observability design review, telemetry readiness review, and alert actionability audit.
Use this skill when you need to identify interactions that need at least pairwise coverage after factors, values, and constraints are explicit; triggers include 成对测试 and pairwise test design.
Use this skill when you need to form evidence-based performance bottleneck hypotheses and validation steps; triggers include performance bottleneck analysis.
Use this skill when you need to compare performance evidence across versions and assess regression risk; triggers include performance regression analysis.
Use this skill when you need to interpret performance results, evidence quality, and risk without inventing conclusions; triggers include performance result analysis.
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.
/client-backup-overview
Client backup overview
Backup health overview across every device for one Axcient client
/azure-cost
Azure cost
Azure cost and pricing analysis for a subscription — Advisor cost recommendations, retail pricing lookups, and quota-driven right-sizing signals, scoped to one subscription
/azure-diagnostics
Azure diagnostics
Resource health and diagnostics triage for an Azure resource or subscription — Resource Health status, AppLens deep diagnostics, and Azure Monitor alert state
/backup-status
Backup status
Portfolio-wide backup job health snapshot - failure count, at-risk clients, and storage trends
/restore-check
Restore check
Restore-readiness check - has this actually been restore-tested, for one client or the whole portfolio
/retention-audit
Retention audit
Retention and RPO compliance audit against contracted requirements, for one client or the whole portfolio
/create-monitor
Create monitor
Create a new Better Stack uptime monitor
/incident-triage
Incident triage
Triage current Better Stack incidents
/monitor-status
Monitor status
Check all Better Stack monitor statuses and identify downtime
/search-logs
Search logs
Search logs via Better Stack Logtail
/status-page-update
Status page update
Update a Better Stack status page with current status or maintenance
/investigate-detection
Investigate detection
Investigate a single Blackpoint Cyber / CompassOne detection end-to-end
/partner-overview
Partner overview
Portfolio-level Blackpoint Cyber / CompassOne rollup of detections and exposure across all tenants
/search-detections
Search detections
List recent Blackpoint Cyber detections for a tenant
/tenant-exposure
Tenant exposure
Build a prioritized exposure report for a Blackpoint Cyber / CompassOne tenant
/triage-detections
Triage detections
Sweep and prioritize the open Blackpoint Cyber / CompassOne detection queue across tenants
/agent-inventory
Agent inventory
List all devices and agents across the organization with status and health information
/finding-triage
Finding triage
Triage open Blumira findings by severity, presenting a prioritized list for review
/investigate-finding
Investigate finding
Deep investigation of a specific Blumira finding with details, context, and comment history
/msp-overview
Msp overview
MSP dashboard showing all managed accounts with open finding counts and severity breakdown
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…
0 views 0 likesAn AI Agent that lives in your pocket. Local-first and privacy focused.
1 views 0 likesUnofficial skill that teaches coding agents to build with TypeSafe AI's Jev: typed decisions, calibrated confidence, and prior art from 150+ community projects.
3 views 0 likesAdaptive Test-time Learning and Autonomous Specialization
2 views 0 likesPrediction-market trading engine — Wang Transform pricing on 291K+ contracts; paper-traded across Kalshi · Polymarket · Solana DFlow (Jito bundles) · 633 tests
2 views 0 likesKnowledge Management for Humans and Agents
2 views 0 likesOpen-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…
3 views 0 likesDeepAgent Code: AI coding agent with persistent memory and control plane
2 views 0 likes