LLM Mart Basic

Docs specialist — docstrings, API refs, README, standalone FAQ/comparison tables. NOT for CHANGELOG (oss:shepherd), linting (foundry:linting-expert), implementation (foundry:sw-engineer), narrative content (foundry:creator). TRIGGER: "write docs for", "add docstrings to", "update

Python static analysis — ruff, mypy, pre-commit, lint/type fixes, type annotations. NOT for CI topology (oss:cicd-steward), test logic (foundry:qa-specialist), non-style implementation (foundry:sw-engineer), docstrings (foundry:doc-scribe). TRIGGER: "is this clean", "lint issues"

Perf engineer — CPU/GPU/memory/I/O bottlenecks, DataLoader throughput, PyTorch tuning. Profile-first, measures before changing. NOT for refactoring (foundry:sw-engineer), architecture (foundry:solution-architect), DataLoader correctness (research:data-steward). TRIGGER: "why is t

QA specialist writing/fixing tests. Black-box tester: public API surface, expectations from docs not implementation. NOT for linting (foundry:linting-expert), implementation (foundry:sw-engineer), test perf (foundry:perf-optimizer), non-Python frameworks. TRIGGER: "write tests fo

Architectural spec specialist — ADRs, API design, migration plans, component diagrams. Reads code, produces specs only. NOT for implementation (foundry:sw-engineer), release mgmt (oss:shepherd), adversarial challenge (foundry:challenger), perf tuning (foundry:perf-optimizer). TRI

Senior SW engineer writing/refactoring Python — features, bugfixes, TDD, SOLID. Also authors hook JS files under hooks/. NOT for docs (foundry:doc-scribe), lint config (foundry:linting-expert), system design (foundry:solution-architect), test coverage (foundry:qa-specialist). TRI

Fetches web pages, API docs, external package/release info — version lookups, GitHub release extraction, docs scraping. NOT for code analysis (foundry:sw-engineer), ML paper analysis (research:scientist), internal docs (foundry:doc-scribe), local codebase search. TRIGGER: "check

CI/CD health specialist, Python/GitHub Actions only — failing CI runs, build times, test matrices, caching, SHA pinning. NOT for ruff/mypy config (foundry:linting-expert), PyPI release/CHANGELOG (oss:shepherd), non-GitHub-Actions platforms. TRIGGER: failing CI runs, slow builds,

Fetches all GitHub API data for a repo (REST + GraphQL) in two parallel groups; writes raw JSONL for oss:repo-warden axis scorers. TRIGGER when: spawned by /oss:analyse (vitality mode) to fetch raw GitHub data. NOT for axis scoring or report generation. NOT for direct user invoca

Scores an assigned group of vitality axes from a pre-fetched DATA_FILE using vitality-scoring.md; writes partial scores JSON for /oss:analyse assembly. TRIGGER when: spawned 3× in parallel by /oss:analyse (vitality mode) to score axis groups A, B, or C. NOT for raw data fetching

OSS shepherd, Python/ML/CV/AI — contributor communication (triage, reply/PR drafts), release coordination (SemVer, PyPI, CHANGELOG). NOT for docstrings/README (foundry:doc-scribe), CI/publish YAML (oss:cicd-steward), diff review (/oss:review), CHANGELOG gen (/oss:release). TRIGGE

Data lifecycle specialist — dataset acquisition, DVC versioning, split audits, leakage detection, DataLoader config. Manual invocation only — no research skill auto-dispatches this agent. Delegates scraping to foundry:web-explorer. NOT for ML experiment design (research:scientist

AI/ML researcher — paper analysis, hypothesis generation, experiment design. ONLY for named research paper/hypothesis/experiment. NOT for general Python (foundry:sw-engineer), SOTA surveys (/research:topic), web content (foundry:web-explorer), dataset acquisition (research:data-s

Creates original editorial illustrations where a recurring mascot character performs the idea — one caught scene by default, a hand-built explainer diagram (labeled stages, a fan-out, timeline, loop, or stack) when the structure itself is the point, or a transparent character cut

Use when the user has agreed to install the Hedgehog build discipline in a project that does not have it yet, or when they mention Hedgehog by name — carries the `npx @skyf0xx/hedgehog init` install procedure and its core and host flags. The plugin's SessionStart hook decides whe

Maintainer-only. Use when re-vendoring vendor-skills/BMAD/ against a newer BMAD-METHOD commit — "update BMAD", "re-vendor BMAD", "bump the BMAD pin". Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.

Maintainer-only. Use when triaging inbound GitHub issues and pull requests on skyf0xx/hedgehog — "triage the issues", "check the PRs", "review inbound", "what's in the queue". Reads each item read-only, judges it for security and for whether it is real, then fixes and closes or c

Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit — this skill matters most whe

Use when the user wants to contribute a fix or ROADMAP.md item back to the Hedgehog project itself (skyf0xx/hedgehog) rather than their own project. Triggers on "let's fix that in Hedgehog", "I want to contribute", "let's pick up a roadmap item", or when `tweaker` offers this at

Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining `04-prd.md` into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure —

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 inspect` prints the full record for a single lease: state, provider,

Run named, repo-local jobs defined in your Crabbox config.

`crabbox list` shows the current Crabbox machines (leases) for a provider. It is

`crabbox login` authenticates the CLI against a coordinator, stores the

`crabbox logout` clears the stored broker token from your user config so the CLI

`crabbox logs` prints the retained command output for a recorded run.

`crabbox marketplace` previews the Crabbox credits gateway: one Crabbox billing

`crabbox media` turns a recorded desktop video into lightweight review

`crabbox open` prepares an existing SSH-capable lease for an external editor.

`crabbox pause` pauses a single lease, freeing the remote compute while

`crabbox pond` is the cross-provider peer-discovery and lifecycle surface for a

`crabbox pool` contains machine-pool helpers. `pool list` keeps the older

`crabbox ports` bridges provider-native port publishing for an existing Crabbox

`crabbox prewarm` leases a reusable box and prepares it for test runs. For

`crabbox providers` prints the provider capability matrix that the CLI compiles

`crabbox receipt <run-id>` retrieves a brokered run's committed terminal

`crabbox results` prints the structured test summary attached to a recorded

`crabbox resume` resumes a lease previously paused with [`pause`](pause.md),

`crabbox run` syncs the current dirty checkout to a box, runs a command there,

`crabbox screenshot` captures a single PNG from a desktop lease without opening a

Open-source super AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-model, multi-channel. Lightwei…

Open-source AI browser agent for web automation: a web browsing agent and computer-use agent in plain English. Browser MCP for Claude Code and Gemini CLI.

Agent-native trading terminal built on DeepSeek Harness. Crypto, US, CN and HK in one three-column GUI, 19+ hot-swappable connectors, dry-run by default with hu…

Open-source desktop and web coding agent with a first-party host and harness, durable sessions, model connections, streaming chat, and workspace tools.

OrcaReplay — Time travel for AI agents. Record, replay, fork, and debug any agent run with any model. Built by the OrcaRouter.ai team.

A complete toolkit for connecting R and LLMs

OpenSRE — the memory-first AI SRE. Self-hosted incident investigation with episodic memory, knowledge graph, web console, Slack & Teams. opensre.in

A desktop AI coding assistant that works with your local projects. Ally helps you understand code, edit files, search a workspace, manage tasks, and complete de…

【在线免费使用】 简单快速将SQL或DBML转换为美观的ER图（支持 Agent Skill）/ The best SQL to ER Diagram converter (Support Agent Skill).

Operation-bound protection for autonomous AI agents: contain and verify operations before committing changes, understand intent and risk across long-running wor…

Local-first AI coding agent desktop: Electron + Rust host core + pi Agent Harness + user-installable plugins

Local-only Go static analysis engine with a built-in MCP server. Gives AI coding agents deterministic structural awareness: call graphs, impact analysis, symbol…

Self-hosted AI agent workspace with tool calling, MCP, multi-model routing, sandboxed execution, multi-agent workflows, and LLM-authored 3D character animation…

Automated TDD enforcement for Claude Code

High-performance platform for building websites, e-commerce, and web applications—with Native AI, JavaScript development, and a marketplace for portable sites a…

Autonomous AI-agent orchestration engine for job discovery with decision traces, tool adapters, and production-grade run control.

Token efficient Claude Code full Python rebuild. AI Coding Agent in 310K LoC Python.

OPC — One Person Company. A full team in a single Claude Code skill. Adaptive agent orchestrator with 21 built-in roles, 6 flow templates, and adversarial quali…

Open-source, secure environment with real-world tools for enterprise-grade agents.

MCP server for AI-powered GitHub project management — agent orchestration, PRD-to-issues pipeline, sprint planning, and multi-agent swarm coordination