LLM Mart Basic

Read and answer messages in the chat apps on the user's phone (微信 and the like) through the screen — catch up, draft a reply in the user's voice, send only text they confirmed. Use when the user asks what someone said on WeChat or wants a chat answered.

The user's 腾讯会议 via the official tmeet CLI — upcoming meetings, creating, changing or cancelling one, inviting people, then the recording, minutes, transcript and attendance. Use when the user mentions 腾讯会议, a 会议号, a 会议链接, 纪要 or 录制, or wants a meeting set up or looked up.

Trains in China through the 12306 MCP server — routes, dates, options, connections and stops with no screen; booking only on the user's word, in the 12306 app on their phone, stopping before payment. Use when the user asks about 火车票 / 高铁 / 12306 or a train between two cities.

Plan a trip end to end — itinerary by day, a packing list to tick off, a budget, and the calendar checked for conflicts — as pages in the workspace. Use when the user is going somewhere for more than a day and wants a plan, an itinerary or a packing list.

Look back at the past week and set up the next one — calendar, mail, goals and files in one page, with a short plan. Use when the user asks for a weekly review, a week in review, "how did my week go" or to plan next week.

Подготовка русского текста к проверке системой «Антиплагиат» (antiplagiat.ru, «Антиплагиат.ВУЗ»): оценка доли «ИИ-сгенерированного» текста по фрагментам в духе модуля ИИ-детекции, переписывание подсвеченных абзацев своим голосом, чистка технических артефактов, из-за которых докум

Аудит и правка русских текстов от признаков ИИ-генерации («ИИ-стиль», канцелярит, кальки с английского, шаблонная структура). Используй, когда просят «убрать ИИ-стиль», «очеловечить текст», «почистить от нейросетевых штампов», «проверить, не звучит ли как ChatGPT», «вычистить кан

Official NVIDIA-authored guidance for NVIDIA cuDF GPU DataFrames, pandas acceleration, dask-cuDF, ETL, joins, groupby, CSV/Parquet I/O, nullable semantics, and multi-GPU DataFrame workloads.

Convert a grover_base checkpoint (encoder-only or encoder + vocab heads) into a hybrid checkpoint by adding a randomly-initialized cMIM decoder + latent_dist, then continue pretraining on the user's corpus as hybrid (vocab + contrast). Effectively kermt-continue-pretrain with a o

Continue KERMT pretraining on a custom SMILES corpus with a grover_base, cmim, or hybrid checkpoint. Use a local checkpoint or optionally download a pinned Hugging Face model bundle using HF_TOKEN if configured. Run containerized training and write model bundles, prepared data, l

Extract per-molecule embeddings from any encoder-bearing KERMT checkpoint. Use a local checkpoint or optionally download a pinned Hugging Face model bundle using HF_TOKEN if configured. Run containerized embedding extraction and write model bundles, per-readout .npy embeddings, c

Run predictions with a finetuned KERMT checkpoint on a SMILES-only CSV. The skill validates that the input ckpt has task FFN heads (refuses pretrain ckpts with a redirect to kermt-finetune), validates the CSV, prepares the data (clean + rdkit_2d features), then launches main.py p

Check progress for a detached KERMT run (pretrain, finetune, or any kermt_run_detached invocation). Reads run.json, queries docker for container state, tails the pretrain/finetune log, and parses progress lines (epoch, step, val loss).

Bootstrap the KERMT agent environment — verify host docker + nvidia-container-toolkit, build the kermt:latest image from the repo's Dockerfile if it doesn't yet exist, and run a GPU smoke test inside the container. Every other kermt-* skill depends on this; invoke it first.

NOTE: your protein sequence and the retrieved MSA alignment are transmitted to external NVIDIA-hosted APIs (health.api.nvidia.com) on every call. Use local NIM containers for confidential or proprietary sequences. Run a complete protein structure prediction pipeline using NVIDIA

Use when porting circuits from another framework (e.g. Qiskit) into CUDA-Q kernels while preserving the source algorithm and validation fidelity.

Modify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions.

Trace, complete, and interpret the Pareto frontier across competing objectives using repeated single-objective cuOpt solves (weighted-sum and ε-constraint).

LP, MILP, and QP (beta) with cuOpt — Python, C, and CLI. Use when the user is solving LP, MILP, or QP with any cuOpt interface.

LP, MILP, QP — concepts, problem-text parsing, and formulation patterns (parameters, constraints, decisions, objective). Concepts only; no API.

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.

Run an organic-social (ECHO) workflow: channel portfolio and voice dossiers, platform-native content and calendars, the social-quality gate with a pre-publish go/no-go, community/inbox/crisis operations, and the listening/SOV/dark-social measurement loop. Not sure? Use /aaron-marketing:auto.

Route meeting-recall questions to the right Minutes MCP tool.

Prepare a sourced Minutes meeting outcome for human-governed closeout of existing X1 work. Use when the user wants a meeting decision or commitment to close, defer, escalate, or retire a specific X1 coordination thread. Never use it to infer settlement, move money, contact anyone, or close X1 work automatically.

Route meeting-recall questions to the right Minutes MCP tool.

Prepare a sourced Minutes meeting outcome for human-governed closeout of existing X1 work. Use when the user wants a meeting decision or commitment to close, defer, escalate, or retire a specific X1 coordination thread. Never use it to infer settlement, move money, contact anyone, or close X1 work automatically.

`crabbox capacity [--json]` reports the authenticated owner's current admission

Code review the current proposed code change

Resolve a merge conflict

Code review for pull request $1

Six Thinking Hats Analysis

Slash commands shipped by the plugin. Portable framework commands work in any Claude Code session; the workflow commands embed one author's personal setup and are opt-in - see [Adapting for your workflow](../README.md#adapting-for-your-workflow) before relying on them. Back to th

Autonomous fix loop for failing CI on the repo's default branch

Autonomous PR fixing loop - iterates on CI failures and review comments until green

GitHub-issue marathon - triage open issues, then run agent-ready ones to merge with Agent Teams

Example Marathon Configuration for CLAUDE.md - copy the section below into your project's CLAUDE.md

Task Master - plan, start, review, and close

Deep understanding mode (nemawashi) - exhaustive context-gathering before action

Searches Burp Suite project files for security analysis

Detects timing side-channels in cryptographic code

Performs security-focused differential review of code changes

Atom Agent, Open-Source Governed AI Agent Platform for Self-Hosted Automation

The agent engineering intelligence harness, optimized tools, memory system, subagents and mixture of models packages ⚚

Sesori iOS/Android app and the Sesori Bridge CLI — drive Claude, Codex, OpenCode, Cursor, Pi, OMP, Hermes coding sessions from your phone

🧠 RepoBrain (formerly Antigravity) — Give your repo a brain. ChatGPT for your codebase: works in Claude Code, Cursor, Codex, Windsurf & more.

Use ChatGPT (Codex), Claude, and Grok (X Premium) subscriptions as DeepSeek Harness LLM providers — OAuth login in the web UI, no API keys

Latitude is the open-source AI monitoring platform.

Open-source AI browser agent for Chrome and Firefox (monorepo) 🧠

Official Model Studio CLI（阿里云百炼 CLI）built for AI Agent frameworks, exposing models, search, multimodal, and workflow capabilities as structured tool calls.

Curated DeepSeek Harness (DSH) plugins, extensions, tools, skills, clients, runtimes, integrations, and verified references — English and Chinese.

Turn papers, code, and docs into presentation-ready, natively editable PPTX in Codex / Claude Code. Native charts and equations, speaker notes, click-build anim…

Grix : Work with agents like talking to people.

Local First Ai Agent. Optimized for Local Ai models. Long context window. Proper tools callings. Runs privately on your device.

Model Context Protocol server that integrates AgentQL's data extraction capabilities.

AI that ships your tickets.

Metadata-driven CLI for AI Agent Bots — 48 operations across 7 domains, structured JSON envelope I/O, zero interactive prompts.

An open-source, extensible, self-hosted agent workspace with multi-runtime support for Codex, Claude Code, and more, plus reusable local apps for custom interfa…

Open-source Windows desktop client and GUI for DeepSeek Harness — zero-setup installer with Codex, plugins, skills, SSH, mobile remote access, and 11 skins.

The open-source AI workbench for scientific research

DeepSeek-native AI coding agent for your terminal. Engineered around prefix-cache stability — leave it running.

A Fully free agentic browser driver for AI , few tools, full control, real stealth, top-tier token efficiency.