LLM Mart Basic
@llm-mart · Joined Jun 2026
Gather information, evaluate sources, and synthesize findings.
Use skillfold to manage project and user skills for Claude Code, Codex, and Cursor. Declare skills in skillfold.yaml, pin them in skillfold.lock, and install them reproducibly.
Condense information with audience-appropriate detail levels.
Write and reason about tests, covering behavior, edge cases, and errors.
Produce clear, structured prose and documentation.
Implements code incrementally with quality gates. Use when the user says 'build' or 'implement', or when starting the implementation phase of an approved plan.
Monitor the CI pipeline for the current branch via a background Monitor script (GitHub or GitLab), reacting to pass, fail, and manual-gate states. Use when the user says 'watch CI', 'monitor the pipeline', 'is CI green', or after pushing a branch or creating a PR/MR.
Runs a structured production-incident investigation that forces evidence-first hypothesis ranking before any code change. Use when given an error message, Sentry alert, failing log, or an 'investigate <X>' request.
Creates or updates a diagram, picking mermaid vs drawio per rules/diagrams.md, writing the source file, and previewing via MCP. Use when the user says 'diagram' or '/diagram', or asks for a flowchart, architecture, sequence, or state diagram.
Drives a fleet of MRs/PRs to done with a manager loop plus the built-in /goal command, delegating all edit, review, rebase, and conflict work to worktree-isolated domain-expert subagents. Use when the user says 'drive fleet' or 'drive the fleet', has 2+ independent lanes to drive
Investigates and fixes a GitHub issue. Use when given an issue number or URL, or when the user says 'fix issue'.
Runs a grilling session that challenges a plan against the existing domain model, sharpens terminology, and updates the CONTEXT.md glossary inline as decisions are made. Use when the user wants to stress-test a plan against their project's language and documented decisions.
Compacts the current conversation into a handoff document another agent can pick up. Use when the user says 'handoff', 'hand off', or wants to continue this work in a fresh session.
Finds deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI
Read and write Jira work items through the acli CLI. Use when the user mentions a Jira ticket, issue, story, bug, or epic, drops a Jira key like SER-123, or pastes an atlassian.net/browse URL.
Create a merge request or pull request from the current branch: verify quality gates, enforce conventional commits, validate the title, and create it without a confirmation step. Use when the user says 'create MR', 'create PR', 'open a merge request', or 'raise a PR'.
Builds a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Reviews code exclusively for over-engineering and lists what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. Use when the user says 'review for over-engineering', 'is this over-engineered', or invokes /prune. Complements
Starts Phase 1 (Research) for a topic: reads every relevant file, optionally runs a panel of Explore teammates, and saves a research artifact to .claude/state/research/. Use when the user says 'research <topic>' or '/research', or before planning work in unfamiliar code. Research
Reviews a pull request with structured severity-based feedback. Use when asked to review a PR, asked for a code review, or given a PR number/URL.
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.
/group-chat
Group chat
Create a multi-agent group chat with AG2 using configurable speaker selection patterns
/new-a2a-agent
New a2a agent
Scaffold an A2A-compliant AG2 agent with server wiring, card settings, and skill definitions
/new-agent
New agent
Scaffold a new AG2 ConversableAgent with tool functions, system prompt, and LLM config
/new-tool
New tool
Create a tool function for an AG2 agent with type annotations, docstrings, and JSON return contracts
/sequential-workflow
Sequential workflow
Create a sequential multi-agent pipeline where each agent processes and passes results to the next
/workflow-from-spec
Workflow from spec
Design a complete multi-agent workflow from a natural language description, selecting the right orchestration pattern
/act
Act
Follow RED-GREEN-REFACTOR cycle approach for test-driven development
/add-authentication-system
Add authentication system
Implement secure user authentication system
/add-changelog
Add changelog
Generate and maintain project changelog
/add-mutation-testing
Add mutation testing
Setup mutation testing for code quality
/add-package
Add package
Add and configure new project dependencies
/add-performance-monitoring
Add performance monitoring
Setup application performance monitoring
/add-property-based-testing
Add property based testing
Implement property-based testing framework
/add-to-changelog
Add to changelog
Add a new entry to the project's CHANGELOG.md file following Keep a Changelog format
/agent-preflight
Agent preflight
Preflight a repo before AI agents change files
/all-tools
All tools
Display all available development tools
/architecture-review
Architecture review
Review and improve system architecture
/architecture-scenario-explorer
Architecture scenario explorer
Explore architectural decisions through systematic scenario analysis with trade-off evaluation and future-proofing assessment.
/bidirectional-sync
Bidirectional sync
Enable bidirectional GitHub-Linear synchronization
/big-features-interview
Big features interview
Interview to flesh out a plan/spec
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.
5 views 0 likesAdaptive Test-time Learning and Autonomous Specialization
3 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
4 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…
4 views 0 likesDeepAgent Code: AI coding agent with persistent memory and control plane
2 views 0 likesAwesome Jev — evidence-graded index of TypeSafe System One: SDKs, MCP tools, agents, apps and open models. 20 languages, rebuilt every 2 hours.
1 views 0 likesCLI for Telegram — agent-friendly, daemon-based, with webhook event push.
1 views 0 likesAI deep-research agent that turns any question into a cited report: plans searches, reads real sources, verifies evidence. Self-hosted, multi-provider, Docker-r…
0 views 0 likes