LLM Mart Basic

Review an upstream documentation change against the skills, agent instructions, or runbooks that cite it. Identify supported updates, unaffected instructions, and unresolved version or evidence gaps. Use with a supplied source diff or Skill Watch result.

Turn a repository issue into an evidence-backed triage note: observed behavior, missing reproduction details, possible duplicates, and the next useful action. Use for issue triage, not implementation or bulk issue closure.

Verify a proposed bug fix against an unchanged regression test and the relevant existing tests, reporting baseline and candidate outcomes separately. Use for fix verification, not a general claim that software is bug-free.

Draft factual project announcements, GitHub launch posts, and development updates for a specified audience or platform. Use to explain shipped work clearly, with evidence and a useful invitation for feedback.

Draft clear, respectful replies to issues, PR discussions, and technical support reports from available evidence. Use to explain status, request a minimal reproduction, or communicate a project decision without inventing commitments.

Create or improve a repository README from actual project evidence, with a clear purpose, usable quickstart, and honest limitations. Use for project landing documentation and onboarding, rather than long tutorials or release notes.

Write a focused regression test from an established bug reproduction and public behavior. Use when a fix needs a test that fails on the affected version; avoid mirroring the implementation or weakening assertions.

Build a step-by-step technical tutorial around a reproducible outcome, with prerequisites, checkpoints, and recovery steps. Use for hands-on guides when a README quickstart is too short.

Write or revise interface labels, errors, empty states, and confirmation text from actual product behavior. Use for UI microcopy with clear next actions, preserved localization tokens, and explicit length constraints.

Investigate training failures, NaNs, missing gradients, misleading losses, and non-reproducible runs in PyTorch, Lightning, or TensorFlow/Keras. Use for a concrete training bug or regression, not an open-ended architecture or hyperparameter search.

Edit stiff or AI-sounding prose into natural writing while preserving meaning, facts, citations, and the author's point of view. Use when asked to humanize, de-AI, or make an existing draft sound more human, in its original language.

Translate and localize Polish and English technical documentation, UI text, and project updates. Use for natural PL/EN phrasing while preserving commands, placeholders, factual precision, and a project glossary.

Adapt a draft to a user's writing samples or explicit tone brief. Use for consistent personal or project voice across docs and posts; distinguish style evidence from factual content.

Prepare release notes and migration guidance from a verified revision range and project release policy. Use for release preparation; never present open PRs or planned changes as shipped features.

Reduce a reported software bug to a runnable, minimal reproduction with the exact command, environment, and observed failure. Use when verifying a bug report; do not infer success from a failing setup command.

Review a pull request for concrete correctness regressions using its diff, surrounding code, and relevant tests. Use for a requested PR review; distinguish actionable defects from optional preferences.

Review an upstream documentation change against the skills, agent instructions, or runbooks that cite it. Identify supported updates, unaffected instructions, and unresolved version or evidence gaps. Use with a supplied source diff or Skill Watch result.

Turn a repository issue into an evidence-backed triage note: observed behavior, missing reproduction details, possible duplicates, and the next useful action. Use for issue triage, not implementation or bulk issue closure.

Verify a proposed bug fix against an unchanged regression test and the relevant existing tests, reporting baseline and candidate outcomes separately. Use for fix verification, not a general claim that software is bug-free.

Draft factual project announcements, GitHub launch posts, and development updates for a specified audience or platform. Use to explain shipped work clearly, with evidence and a useful invitation for feedback.

A green PR, a controller reporting success, and not one line of the new code running

Discover testnet↔mainnet subnet lineage from repo configs and open a PR for review (pass --dry-run to report only)

Triage raw inbox notes into reviewed repository destinations without deleting their sources.

Audit and rewrite content to remove AI writing patterns

Log a completed piece of content to content/log.md after the user confirms it was published.

Validate a dream artifact, review each proposal, and apply only individually accepted changes.

Run a curator pass against the validated memory directory and produce a proposal artifact.

End a session — log what happened, update state and the decision log, propose memory updates, and check for uncommitted or unpushed work

Find relevant context files by topic. Use when you need to load files for a topic without a slash command, or when a task spans multiple domains.

Inventory and migrate selected Gemini CLI workflows with dry-run review and parity checks.

Find repeated workflows in selected Gemini CLI sessions and draft portable skills after review.

Scan multi-session drift and offer individually reviewed fixes only after explicit approval.

Scan orphaned worktrees and stale branches, then offer explicit approval-gated cleanup.

Guided onboarding or import for durable workspace context

Start a session — load state files, flag staleness, and give a briefing on current priorities, deadlines, and blockers

Create a morning heartbeat from repository state and update the local heartbeat log.

Mid-session checkpoint — append progress to today's session log and update state files if a priority shifted, without ending the session

Maintainer-only. Find every file that would newly ship to adopters, classify each one against the written distribution-boundary categories, default to withhold on no clean match, and ask the maintainer only where the taxonomy does not settle it. Drives the release CLI, which refuses to produce a manifest until every shipping file has an answer.

Audit memory, wiki, and auto-loaded files for duplication, conflicting instructions, and stale content. The default path researches, then asks you a single Apply / Discuss / Decline question; on Apply it applies the report, files any out-of-scope problem as a tech-debt issue, then commits, opens a PR, and merges it on a main-branch run like /update-deps. Pass --apply to re-run the apply-and-publish stage against the most recent report.

Fix the tech-debt backlog, a single issue or a recommended related batch, highest severity then oldest first, on a fresh isolated branch through the audit gate, closing the issue(s) on merge. Pass `list` to see the ordered backlog, `why <issue-number>` to explain the recommendation, or a bare `<issue-number>` to fix that issue directly.

Health-check and auto-heal this project's Claude integration, triage, heal, verify, and report an F-to-A+ grade.

The fastest way to put Volcengine Ark in your terminal and your AI agent — go from prompt to generated media, multimodal answer, or deployed endpoint in a sin…

本地私有、开源的自进化跨平台 AI 内容发现 Agent：先理解你，再主动从 B站、小红书、抖音、YouTube、X、知乎、Reddit、微博等平台与开放 Web 寻找内容。（支持 deepseek harness 插件） | Local-first open-source cross-platform AI cont…

Persistent memory for AI coding agents — one verified kb_search replaces the grep/find/ls orientation loop. Cross-repo, CPU-only, zero token spend.

AI 时代的伯克希尔：基于 Claude Code / Codex 的价值投资研究框架。巴菲特·芒格·段永平·李录四大师方法论 + 多Agent并行研究。| AI-era Berkshire: a value investing research framework built for Claude Code / Co…

The batteries-included, No-Code FinOps automation platform, with the AI you trust.

Open-source 3D AI agent framework — GLB/glTF avatars with LLM brains, memory, emotions, and autonomous payments. MCP server · x402 · Solana/EVM · Three.js. Embe…

XLSX parser for LLMs, RAG, LangChain, LangGraph, CrewAI, Claude, MCP — turns Excel (.xlsx) into citation-ready JSON with formulas, charts, dependency graphs, an…

Hermes-Relay — Your Hermes AI agent, in your pocket — chat, voice, and control.

A minimalist, terminal-native coding agent written in C.

AI-powered OSINT agent with interactive REPL, MCP server, and CLI. 19 tools. Works with Claude, GPT-4, or local models. For authorized security research only.

AI pair programming in your terminal — one static binary, sub-ms startup, any model

Where data access meets operational intelligence

Build your own security agents. Open-source framework for agents with live, read-only access to your infrastructure, with no path to widen it. Reasons across AW…

Multi-workspace terminal aggregator with Claude Code AI integration

Go implementation of AI coding agent

Harness engineering beginner tutorial, from 0 to 1

Generate images directly in DeepSeek Harness chats

A smarter, self-hosted AI assistant — multi-user, multi-agent.

Turn any research paper into a commercialization report — 6 AI agents, TRL/MRL scoring, patent landscape, market intelligence, verified citations. DeepSeek / Op…

Power BI CLI - semantic models (.NET TOM) and PBIR reports for token-efficient AI agent usage, built for Claude Code