LLM Mart Basic

Use when the user is explicitly working with Quarto, .qmd files, _quarto.yml, Quarto projects, or Quarto features such as callouts, cross-references, citations, Mermaid diagrams, extensions, websites, books, presentations, and reports. Also use for explicit migration from or comp

Deploy or publish Python and R content to a Posit Connect server using rsconnect-python or the R rsconnect package. Handles interactive apps and dashboards, web APIs, rendered documents, and prepared bundles/manifests. Use whenever the user asks to deploy, publish, or redeploy co

Guide for drafting issue closure and decline responses as an open-source package maintainer. Use when helping compose a reply that says "no" to a feature request, closes an issue as won't-fix, redirects a user to a different package, explains why a design choice is intentional, o

Use when the user wants to find, evaluate, audit, or install an open-source AI agent skill or MCP server — e.g. "find an MCP server for Postgres", "is this skill safe to install", "what should I use to scrape a website". Searches a quality-scored, security-graded catalog of ~20K

Generator-evaluator separation and review methodology — loaded by review agents to enforce fresh-context review discipline and gate verdicts; findings from the code, security, and docs reviewers are formatted per the conventional-comments skill. Trigger on "review this diff", "re

Adversarially review a technical design document with fresh context. Dispatches the built-in read-only `Explore` subagent (clean context, no shared history with the design-author) against `docs/plans/<id>/design.md` and presents its verdict — APPROVE, REQUEST CHANGES, or COMMENT.

Tear down local and remote branch state after a pull request is finished, in one of two modes. Mode A (merged): verify the PR actually merged, remove the branch's worktree, resync the default branch, and delete the local branch. Mode B (closed / abandoned): close the PR(s), then

Bring a feature branch up to date with its base without changing what the branch does: capture a pre-rebase check baseline, fetch, rebase onto the latest base, resolve each conflict from both sides' intent with the rationale recorded to disk, re-run the same checks, and treat any

Watch your own pull request for review feedback: undraft it when the cue clearly says it is ready (an ambiguous cue watches the draft), take a baseline snapshot, then poll GitHub in ~31-minute cycles for up to 24 hours and triage new feedback as it arrives — inline review threads

Watch a pull request you are reviewing until your feedback is settled, re-review each settlement, then approve once: poll GitHub in ~31-minute cycles for up to 24 hours until every review thread you opened is resolved and every plain PR comment you posted has a later push behind

Land a reviewed pull request: discover the open PR for the current branch, push any unpushed commits, wait for CI to go green, then squash-merge it so the PR title (which may carry a version) lands as the commit subject. Handles a PR that has fallen behind its base (rebase + forc

Decide the approach before any code is written. The design-author drafts the ~200-line design document, resolving its own open questions autonomously as recorded assumptions, then an adversarial design review gates advancement. Trigger on "design this", "let's align on the approa

Compressed bug-fix pipeline — reproduce, write failing test, minimal fix, verify, and open a draft PR. Skips Question/Research/Design/Structure/Plan phases. Invoke ONLY on explicit pipeline intent — the user says "run the bug-fix pipeline", "team-fix this bug", or runs "/team-fix

Execute the implementation phase. Includes test-first sub-step (writing failing tests, mechanical confirmation gate) and adversarial verification (5 parallel reviewers with hard-gate retry loop). Trigger on "implement this", "execute the plan", or "/team-implement".

Produce the tactical implementation plan from the structure. The plan is an autonomous artifact for the implementer — no approval gate at this phase (the design was already gated by the adversarial design review). Trigger on "plan the implementation", "spell out the steps", or "/

Open the pull request after verification passes. Updates the changelog, optionally surfaces the tracking ticket, and closes out the topic. Trigger on "open the PR", "open a draft PR", or "/team-pr". To land/merge a reviewed PR (wait for CI, then squash-merge) use the separate /sh

Decompose a feature description, ticket, or issue link into the QRSPI Question artifacts (task.md, questions.md). Trigger on "shape this idea", "decompose this task", or "/team-question".

Research a codebase area before making changes. Dispatches parallel read-only agents (file-finder + researcher) that read questions.md only — never task.md. Trigger on "research this", "explore the codebase for", or "/team-research".

Break the reviewed design into vertical slices with verification checkpoints. Runs autonomously and advances to PLAN — no approval gate. Trigger on "slice this up", "break the design into steps", or "/team-structure".

Prepare one or more isolated git worktrees — one per repository the topic touches. Router action — no agent. Trigger on "set up the worktree", "isolate this work", or "/team-worktree".

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.

`crabbox shard` forks a [checkpoint](checkpoint.md) into `--count` leases

`crabbox share` grants other people access to an existing lease through the

`crabbox ssh` resolves a lease and prints a ready-to-run `ssh` command for it.

`crabbox status` prints the current state of a lease: its slug, provider,

`crabbox stop` ends a single lease. For coordinator-backed and direct cloud

`crabbox sync-plan` prints the local sync manifest and its size hotspots

`crabbox tunnel` opens one foreground SSH local port-forward to a resolved

`crabbox unshare` removes sharing rules from a coordinator-backed lease. It is

`crabbox usage` reports lease cost and usage estimates from the broker, broken down by user, organization, or the whole fleet.

`crabbox verify` checks a signed run receipt produced by `crabbox run --attest`.

`crabbox vnc` prints (or opens) the connection details for a desktop-capable

`crabbox warmup` leases a box and waits until it is ready: it provisions (or

`crabbox watch` runs a command on a warm lease, then watches the local

Linux portal viewers default to **Match window**: only the connected controller

`crabbox whoami` calls the broker's `/v1/whoami` endpoint and prints the

Vet a new or changed third-party dependency for license, provenance, and supply-chain risk before any install runs.

Inspect ADR health read-only; optionally select one ADR with --adr N.

{{SKILL_ENTRY:decision-lifecycle}}

Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.

Lightweight Q&A about the project — answer from context and return, no routing, no state change.

Open‑WebUI Tools is a modular toolkit designed to extend and enrich your Open WebUI instance, turning it into a powerful AI workstation. With a suite of over 15…

The token-efficient agentic coding workbench. Built for a future where every token counts — it optimizes token usage at the agent-loop level, saving 70%+ on lon…

MCP server for controlling a real iPhone via macOS iPhone Mirroring...and any MacOs app. Screenshot, tap, swipe, type — from any MCP client.

One desktop for all your AI coding Agent — Claude Code, Codex CLI & Gemini CLI. Auto-detect, one-click install, unified chat, file explorer, terminal & editor.…

Pi — A cross-platform AI coding agent, bringing the Claude Code experience to your desktop. No environment setup, no terminal commands. Download and start codin…

DeepSeek Harness Desktop (dsh-desktop). EAC: Embracing All Creation (揽尽万象). Bundled Node.js runtime with full dsh-CLI kernel, one-click startup, 10 built-in UI…

A telegram bot for searching and auto-saving.

金蝶云星空 K3Cloud MCP Server，让 AI 助手（Claude Desktop、Claude Code、Cursor、Cline、Cherry Studio、Openclaw 等任意支持 MCP 协议的客户端）通过自然语言查询和操作金蝶 ERP 系统。

Rewrite frontier research using allegorical structural mapping.

Free4Chat is a temporary collaboration fabric for Humans and Agents.

Give any AI agent a full desktop — it sees the screen, clicks, types, and runs apps like a human. Automate anything with a UI: browsers, legacy software, intern…

A personal AI agent that can work safely on your machine, remember useful context, and keep its data under your control.

A framework for AI-driven economic activity. Declarative, composable, observable, deterministic.

Open-source, self-hosted customer support desk in a single binary. A lightweight alternative to Intercom, Zendesk, Chatwoot.

54 rigorous skills for Codex, OpenCode, and Pi: code review, security audit, feature development, frontend design, MCP tools, Hugging Face ML/training, and more…

A wonderful list of Game Development resources.

Open Science Desktop — local-first, model-agnostic AI research workbench for macOS, Windows & Linux. Open-source Claude Science desktop alternative built on Tau…

Lexora — Personal AI workspace built around Desktop / 以 Desktop 为核心的个人 AI 工作台

Open-source, AI-native Evernote alternative with native MCP. Zero-cost on Cloudflare or self-hosted with Docker.

Full job-hunt Claude skill bundle — Job Description decoder + Resume builder (11 templates) + Behavioral Interview / story bank. Three self-contained sub-skills…