LLM Mart Basic
@llm-mart · Joined Jun 2026
Use in pre-implementation (idea-to-design) stages to understand spec/requirements and create a correct implementation plan before writing actual code. Turns ideas into a fully-formed PRD/design/specification and implementation-plan. Creates design docs and task lists in docs/feat
Compare two versions of a skill's instructions to detect degradations and complexity increases. TRIGGER when: user asks to diff, compare, or review changes to a skill's markdown instructions. Asymmetric check — only regressions count. Additions, clarifications, and strengthenings
After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.
TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/feat/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Examples: "work on task 1", "fix this bug", "implement feature X from the issue". Provides structured execution
Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.
Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable
Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
TRIGGER when: adding or upgrading any dependency — library, SDK, framework, API, IaC API version (K8s/Terraform/Helm), CRD, or container image. Use BEFORE writing the call. Forces context7/capy lookup instead of guessing.
Use in pre-implementation (idea-to-design) stages to understand spec/requirements and create a correct implementation plan before writing actual code. Turns ideas into a fully-formed PRD/design/specification and implementation-plan. Creates design docs and task lists in docs/feat
Compare two versions of a skill's instructions to detect degradations and complexity increases. TRIGGER when: user asks to diff, compare, or review changes to a skill's markdown instructions. Asymmetric check — only regressions count. Additions, clarifications, and strengthenings
After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.
Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.
Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable
Designs, reviews, revises, and templates deployable system prompts for agent projects. Use whenever the user asks to write, improve, review, or debug an agent's system prompt, system message, or role/boundary instructions — including Chinese requests such as 系统提示词、角色设定、角色和边界规范、提示
Делает одностраничный сводный снимок бизнеса для собственника — позиция по деньгам (бухгалтерия), тренд продаж (платежи), движение по воронке (CRM), обязательства недели (календарь), срочный список наблюдения (почта, мессенджер) и единственное самое важное на сегодня. Сам пробует
Ранжирует топ-5 лидов, которым стоит позвонить сегодня, готовит тезисы разговора из истории переписки, бронирует время в календаре и набрасывает follow-up сообщения. Принимает необязательные аргументы количества и даты. Командная форма: вызывается по имени.
Берёт согласованный контент-бриф и выполняет кампанию от начала до конца: строит календарь публикаций, генерирует макеты для постов в соцсетях через ~~дизайн (VistaCreate, Supa, Поликрафт), пишет тексты подписей и писем, ставит публикации в очередь через ~~crm. Макеты делаются то
Берёт дебиторку и кредиторку, историю сроков поступления денег и известные постоянные расходы из бухгалтерии (1С, МойСклад) и платёжных сервисов (ЮKassa, Тинькофф, банк-выписка) — или из выгрузки CSV — и строит прогноз денежного потока на 30/60/90 дней с доверительными коридорами
Закрывает месяц — сверяет данные бухгалтерии с эквайрингом и выписками, помечает расхождения, пишет ОПиУ-сводку, выгружает пакет закрытия. Принимает необязательные аргументы месяца и места сохранения. Командная форма: вызывается по имени.
Анализирует данные о продажах из ~~платежи и ~~бухгалтерии (ЮKassa, 1С, МойСклад), находит хиты и зависшие позиции, накладывает сезонность и выдаёт приоритизированный контент-бриф на 30 дней: что продвигать, какие акции запускать, что придержать. На выходе только стратегия — без
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.
/meraki-network-health
Meraki network health
Sweep an organization's networks, devices, and appliance VPN status for a site-health overview
/entra-audit
Entra audit
Run a read-only Microsoft Entra identity hygiene audit via the Graph Enterprise MCP — inactive user accounts, admins without MFA registered, unassigned/wasted licenses, and a guest user inventory
/entra-report
Entra report
Conversational Microsoft Entra directory reporting via the Graph Enterprise MCP — license usage, user and group counts, application inventory, and directory composition, formatted for client check-ins and QBRs
/check-queue
Check queue
Check Mimecast email delivery queue status and identify stuck or deferred messages
/review-threats
Review threats
Review Mimecast TTP threat logs for URL clicks, malicious attachments, and impersonation attempts
/trace-message
Trace message
Trace an email through Mimecast by sender, recipient, subject, or date range
/device-inventory
Device inventory
Inventory devices for an N-central customer or site with class, warranty, and monitor-health breakdown
/issue-sweep
Issue sweep
Sweep active issues across N-central customers, grouped by severity and probable root cause
/task-status
Task status
Drill into an N-central scheduled task's outcome - aggregate status down to per-device results and output
/get-record
Get record
Retrieve a NetSuite record by type and internal ID
/browse-files
browse-files
List, search, and inspect ENCODE files by format, type, and assembly
/cite-encode
cite-encode
Generate ENCODE citations for publications, grants, and presentations
/compare-experiments
compare-experiments
Check if two ENCODE experiments are compatible for combined analysis
/cross-reference
cross-reference
Cross-reference ENCODE data with PubMed, GEO, ClinicalTrials, and bioRxiv
/download-encode
download-encode
Download ENCODE files (BED, FASTQ, BAM, bigWig) with MD5 verification
/log-provenance
log-provenance
Log derived files and trace provenance back to ENCODE source data
/manage-credentials
manage-credentials
Store, check, or clear ENCODE API credentials for restricted data
/quality-check
quality-check
Assess ENCODE experiment quality using audit counts and replicate counts
/search-encode
search-encode
Search ENCODE experiments by assay, organ, biosample, or target
/track-experiments
track-experiments
Track ENCODE experiments locally with publications and provenance
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