LLM Mart Basic

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.

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.

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

Repeatable pass upgrading an Angular admin dashboard into a compact black-and-cyan developer-cockpit PWA

Run the drift-detection checklist (incl. agent-drift signals); report + fix in-turn

Orchestrate the final review fan-out (integration + diversity + risk + release readiness)

Run the AI-augmented lint self-improvement loop on the current project. Scans `.lint-history/` for recurring violation patterns (≥3 hits in 30d window), drafts a Claude-ready prompt to author a new semgrep rule for the top candidate, and surfaces the proposal under `.lint-history/proposals/<ts>.md`. Non-blocking analysis. See rules/lint-doctrine.md § Self-improving.

Bootstrap industry-leading lint+autofix+commit-hygiene stack on the current project. Drops in lefthook, oxlint, ESLint, Prettier, Stylelint, markdownlint, ruff, shellcheck, shfmt, yamllint, hadolint, actionlint, jscpd, knip, semgrep, gitleaks, commitizen + git-cz-emoji (emoji-mandatory commits), and semantic-release. Idempotent — re-runs upgrade safely. See rules/lint-doctrine.md.

Surface all retrospective documents with key shape metrics; compare arcs deliberately.

Progressive multimedia enrichment pass — add high-value audio/video/image/interactive to a site, run again and again

Run the autonomous-engineering operating loop on a task (plan→implement→verify→repair→report)

Capture the cumulative output of a /loop arc into a single auditable retrospective document; scans the heymegabyte-claude-skills plugin for modified files, categorizes by directory, counts LOC delta, extracts tool counts from MCP servers, and writes a timestamped report to retrospectives/

Turn a comma-separated list of file paths into a fully structured Pattern A agent brief — ordered writes, per-file schemas, and a verification step baked in.

Turn Pattern B from agent-resilience-discipline into a one-keystroke agent brief for a single-file deliverable < 300 lines.

Chain the full Superpowers process flow — brainstorm → plan → worktree → build → review → finish — on one slash command

Generate a timestamped arc retrospective from the past 7 days of git history in `~/.agentskills`.

Review ~/.claude/CLAUDE.md + rules for contradictions, stale guidance, duplication; consolidate

Batch-run all LLM eval cases in tools/evals/cases/*.json; aggregate pass/fail, cost, regression vs last run; exit nonzero in CI mode

One-line SaaS — from a description, scaffold a complete CF-native multi-tenant SaaS (Hono + D1 + Drizzle + Better Auth + Stripe + shadcn) deployed to a real URL

Unified supply-chain audit. Checks GitHub Actions SHA-pinning (`sha-pin:check`), package.json git+https deps (per `no-gitlab-megabytelabs-deps` semgrep), gitleaks scan, and trufflehog verified-only sweep. Surfaces any tag-mutable, git-URL, or secret-exposed surface. Per rules/ai-agent-security.md § Supply chain.

Run a learning pass after a major run; fold reusable lessons into global config

Summarize recent CHANGELOG.md entries for context restoration. Parses the canonical heading shape `## YYYY-MM-DD — pass-N — summary`. Filters: last N (default 10), YYYY-MM date prefix, or "today". Supports --json for machine-readable output.

Run quality-scores + token-budget + dep-graph, interpret results, flag missing budgets, orphans, and oversize skills

Make any song you can imagine

Leading AI-powered video generation platform that specializes in creating hyper-realistic talking avatars

Hermes Agent is an open-source, self-improving autonomous AI agent developed by Nous Research

Kilo Code is a popular, open-source AI coding agent and "agentic engineering" platform designed to help developers build, refactor, and debug software faster

General-purpose agent in one static Go binary. ReAct loop, ACP server for IDEs, OpenAI-compatible REST API with embedded web UI, Telegram gateway, cron schedule…

Autonomous agent framework with structured memory, safety hooks, and loop management. Built by the agent that runs on it.

TSP自托管、零运维的 A 股「选股 + 监控 + 回测」量化工作台 | 基于 TickFlow 数据源 | LLM能力驱使策略定制+个股分析+复盘 | 自由接入第三方数据源与个性化扩展数据 | 个人开源 ,非TickFlow官方项目

Curated, verified Agent Skills powered by ModelStudio.

Run Claude Code, Codex, Antigravity, Cursor Agent and OpenCode as one runtime — persistent sessions, multi-agent councils, an OpenAI-compatible endpoint, an MCP…

pi had nothing (nothing), so I made something (something) — sorry mariozechner-senpai, I went ahead and lovingly soiled your pure pi for you. opinionated fork o…

A persistent workspace for development work that self-improves and continues beyond one session.

Open-source memory and context for user-aware agents: scoped memory, provenance, retrieval quality, correction, boundaries, evals, and MCP/HTTP access.

📚 A zero-dependency, git-backed micro-lesson library for AI Agents to asynchronously share and search verified debugging experience. Python stdlib only. | http…

Deterministic, local-first memory and guardrails for AI coding agents with no LLM in the hot path.

Deterministic spec-orchestration for local LLMs in the pi coding agent — drives prompts through refine→research→grill→compose→critique, with bundled web/docs/fe…

Native Safari browser automation for AI agents. 97 tools via AppleScript — zero overhead, keeps logins, runs silently in background. Drop-in alternative to Chro…

Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.

Git for agent memory. Branches, diffs, PRs, and rollback for what your agents know.

Multi-Provider AI Gateway - No personal logs by design. Model autodiscovery, Failover groups, High availability, Android companion app, and more - "Because we h…

Production-grade MCP server for MikroTik RouterOS with secure AI-native network automation.