LLM Mart Basic
@llm-mart · Joined Jun 2026
Produce a periodic review of a second-brain vault: what was added, which topics are growing, what contradicts what, which questions are still open, and what is worth reading next. Use this skill whenever the user asks for a weekly or monthly review, asks what changed in their vau
Clean a raw transcript before ingestion: punctuate, paragraph, label speakers, fix mistranscribed technical terms, and split long recordings by topic. Use this skill when the user drops an auto-generated transcript, subtitle file, podcast or lecture transcript, meeting recording
Draft from the vault: outline from concept pages, keep citations to the user's own sources, and surface where their material disagrees. Use this skill when the user wants to write an article, post, essay or newsletter based on what they have collected, or asks what they could wri
Use this skill when selecting and reporting verification for Skill changes; triggers include Skill change verification, quality gates, and evidence levels.
Use this skill when designing, running, interpreting, or reporting Agent Skill evaluations, selecting cases or judges, and analyzing trigger, benchmark, or regression evidence; triggers include Skill evaluation and evaluation design.
Use this skill when reviewing the contract completeness of Skills, Prompts, metadata, or QA documentation; triggers include Skill prose review, Prompt review, and contract audit.
Use this skill when auditing or trimming process residue from Skills, Prompts, comments, or docs; triggers include process prose cleanup, review residue, and current-state rewriting.
Use this skill when reviewing a complete Skill package for architecture, scope, triggers, independent installation, bilingual consistency, Eval readiness, and evidence boundaries; triggers include Skill quality review and package review.
Use this skill when you need to review acceptance criteria for ambiguity, missing rules, and verifiability; triggers include acceptance criteria review.
Use this skill when you need to design accessibility testing against WCAG, keyboard navigation, and assistive technology scenarios; triggers include accessibility testing and a11y testing.
Use this skill when you need evidence-bounded failure classification, retry/fallback/escalation, state consistency, user notice, and recovery evidence; triggers include Agent 故障恢复 and Agent failure recovery.
Use this skill when you need evidence-bounded checkpoints, heartbeats, resume, cancellation, duplicate submission, timeouts, and resource lifecycle; triggers include 长运行 Agent and long-running Agent.
Use this skill when you need evidence-bounded loop state, plan/action/observation cycles, stop conditions, budgets, repetition, and trace evidence; triggers include Agent 循环 and Agent loop.
Use this skill when you need evidence-bounded memory write/read/update/delete, retention, contamination, isolation, provenance, and forgetting behavior; triggers include Agent 记忆 and Agent memory.
Use this skill when you need evidence-bounded Agent identity, tool/resource scope, approval, denial, escalation, and side-effect boundaries; triggers include Agent 权限 and Agent permission.
Use this skill when you need to test AI agent tool-call contracts, authorization, failures, and side-effect boundaries; triggers include agent tool testing.
Use this skill when you need to test AI agent goals, state, planning, recovery, and safety boundaries; triggers include ai agent testing.
Use this skill when you need AI-assisted testing workflows such as test data generation, root-cause analysis, and prioritization; triggers include AI-assisted testing and AI for QA.
Use this skill when you need to test an AI-enabled product feature for behavior, safety, and user-impact boundaries; triggers include AI feature testing.
Use this skill when reviewing AI-generated unit, functional, API, or end-to-end tests for false confidence, weak assertions, missing risks, or unsafe test behavior; triggers include AI-generated test review and functional test review.
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.
/improve-agent
Improve agent
Improve an existing agent through performance baselines, prompt engineering, A/B testing, and staged rollout
/multi-agent-optimize
Multi agent optimize
Optimize multi-agent system performance through profiling, context window tuning, coordination efficiency, and cost and latency tradeoffs
/team-debug
Team debug
Debug issues using competing hypotheses with parallel investigation by multiple agents
/team-delegate
Team delegate
Task delegation dashboard for managing team workload, assignments, and rebalancing
/team-feature
Team feature
Develop features in parallel with multiple agents using file ownership boundaries and dependency management
/team-review
Team review
Launch a multi-reviewer parallel code review with specialized review dimensions
/team-shutdown
Team shutdown
Gracefully shut down an agent team, collect final results, and clean up resources
/team-spawn
Team spawn
Spawn an agent team using presets (review, debug, feature, fullstack, research, security, migration) or custom composition
/team-status
Team status
Display team members, task status, and progress for an active agent team
/api-mock
Api mock
Build realistic API mock servers with request stubbing, dynamic data, test scenarios, and contract testing
/performance-optimization
Performance optimization
Orchestrate end-to-end application performance optimization from profiling to monitoring
/feature-development
Feature development
Orchestrate end-to-end feature development from requirements to deployment
/block-no-verify
Block no verify
Set up PreToolUse hook to block --no-verify and other git bypass flags in Claude Code projects
/c4-architecture
C4 architecture
Generate comprehensive C4 architecture documentation (Context, Container, Component, Code) for a codebase using bottom-up analysis and four coordinated C4 agents.
/workflow-automate
Workflow automate
Automate CI/CD pipelines, releases, and development workflows with GitHub Actions, pre-commit hooks, and infrastructure automation
/code-explain
Code explain
Explain complex code, algorithms, and design patterns with step-by-step breakdowns, visual diagrams, and interactive examples
/doc-generate
Doc generate
Generate API, architecture, code, and user documentation from a codebase and automate keeping it current
/context-restore
Context restore
Restore saved project context and decisions to resume a session
/refactor-clean
Refactor clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
/tech-debt
Tech debt
Analyze and remediate technical debt — inventory debt items, score by impact, and produce a prioritized remediation plan with estimated effort.
Open-source super AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-model, multi-channel. Lightwei…
10 views 0 likesOpen-source AI browser agent for web automation: a web browsing agent and computer-use agent in plain English. Browser MCP for Claude Code and Gemini CLI.
9 views 0 likesAgent-native trading terminal built on DeepSeek Harness. Crypto, US, CN and HK in one three-column GUI, 19+ hot-swappable connectors, dry-run by default with hu…
11 views 0 likesOpen-source desktop and web coding agent with a first-party host and harness, durable sessions, model connections, streaming chat, and workspace tools.
8 views 0 likesOrcaReplay — Time travel for AI agents. Record, replay, fork, and debug any agent run with any model. Built by the OrcaRouter.ai team.
8 views 0 likesA complete toolkit for connecting R and LLMs
9 views 0 likesOpenSRE — the memory-first AI SRE. Self-hosted incident investigation with episodic memory, knowledge graph, web console, Slack & Teams. opensre.in
11 views 0 likesA desktop AI coding assistant that works with your local projects. Ally helps you understand code, edit files, search a workspace, manage tasks, and complete de…
9 views 0 likes【在线免费使用】 简单快速将SQL或DBML转换为美观的ER图(支持 Agent Skill)/ The best SQL to ER Diagram converter (Support Agent Skill).
11 views 0 likesOperation-bound protection for autonomous AI agents: contain and verify operations before committing changes, understand intent and risk across long-running wor…
8 views 0 likesLocal-first AI coding agent desktop: Electron + Rust host core + pi Agent Harness + user-installable plugins
10 views 0 likesLocal-only Go static analysis engine with a built-in MCP server. Gives AI coding agents deterministic structural awareness: call graphs, impact analysis, symbol…
17 views 0 likesSelf-hosted AI agent workspace with tool calling, MCP, multi-model routing, sandboxed execution, multi-agent workflows, and LLM-authored 3D character animation…
16 views 0 likesAutomated TDD enforcement for Claude Code
12 views 0 likesHigh-performance platform for building websites, e-commerce, and web applications—with Native AI, JavaScript development, and a marketplace for portable sites a…
13 views 0 likesAutonomous AI-agent orchestration engine for job discovery with decision traces, tool adapters, and production-grade run control.
9 views 0 likesToken efficient Claude Code full Python rebuild. AI Coding Agent in 310K LoC Python.
13 views 0 likesOPC — One Person Company. A full team in a single Claude Code skill. Adaptive agent orchestrator with 21 built-in roles, 6 flow templates, and adversarial quali…
10 views 0 likesOpen-source, secure environment with real-world tools for enterprise-grade agents.
9 views 0 likesMCP server for AI-powered GitHub project management — agent orchestration, PRD-to-issues pipeline, sprint planning, and multi-agent swarm coordination
10 views 0 likes