LLM Mart Basic

Finance (CFO). Owns plugins/finance/** and nothing else. Delegate work in this department's remit here.

Corporate IT. Owns plugins/it-operations/** and nothing else. Delegate service desk, systems and network administration, endpoints, assets, identity lifecycle, and backup work here.

Reviewer-class. Read-only review of what other departments commit to — contract terms, privacy and data handling, risk acceptance, and compliance findings. Holds no write surface. Its findings are not overrulable by the department under review.

Legal & Risk (CLO/CCO). Owns plugins/legal-risk/** and nothing else. Delegate work in this department's remit here.

Marketing (CMO). Owns plugins/marketing/** and nothing else. Delegate work in this department's remit here.

Operations (COO). Owns plugins/operations/** and nothing else. Delegate work in this department's remit here.

People (CHRO). Owns plugins/people/** and nothing else. Delegate work in this department's remit here.

Enterprise PMO. Owns plugins/pmo/** and nothing else. Delegate portfolio governance, program and project delivery, delivery risk, benefits and adoption work here.

Product (CPO). Owns plugins/product/** and nothing else. Delegate work in this department's remit here.

Repository scaffolding — docs, CI, scripts, plugin manifests, and the README. Owns everything outside plugins/. Delegate structural and documentation work here.

Revenue (CRO). Owns plugins/revenue/** and nothing else. Delegate work in this department's remit here.

Reviewer-class. Read-only security review of what other departments build — authorization, data handling, secrets, dependencies, and designs that create exposure. Holds no write surface. Blocking findings are not overrulable by the department under review.

Security (CISO). Owns plugins/security/** and nothing else. Delegate threat modeling, security architecture, incident response, vulnerability management, and identity work here.

Technology (CTO/CIO). Owns plugins/technology/** and nothing else. Delegate work in this department's remit here.

Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals bef

Imported from nitinjain999/platform-skills/assets/agents/navigator.template.md.

코드·설정·프리셋 변경 뒤 문서를 현행화한다. "문서 현행화", "README 갱신", "문서 최신화" 요청 시, 그리고 동작·경로·버전·수치를 바꾼 PR 을 올리기 직전에 사용. 문서의 주장을 실제 코드·명령 출력·공식문서와 대조해 정정하고, 다국어 짝 파일을 함께 갱신한다.

이 파일을 복제해 프로젝트 스킬을 만든다. 트리거 조건을 description 에 구체적으로 적을 것.

사용자가 /grill-me 를 호출하거나 아이디어·기능 요청·스펙을 구현 전에 굽고(grill)·압박 검증하고·심문해 달라고 할 때 사용. superpowers:brainstorming 의 opt-in 대체재 — 작업마다 사용자가 둘 중 하나를 고른다.

에이전트 영속 메모리를 실제 소스와 대조 — 각 메모리의 핵심 단언을 코드·DB·이슈 트래커·파일시스템에 대조해 stale 을 정정하고 dead 를 아카이브 후보로 리포트. 메모리가 30개를 넘거나, 스택/인프라 큰 변경(라이브러리 교체·버전 업그레이드·서버 이전·스키마 DROP) 직후, 메모리끼리 모순돼 보일 때, 또는 "메모리 정리/감사" 요청 시 사용.

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

Build AI Agents like playing LEGOs. Everything is a Plugin.

The coding agent that answers to you, your model, your machine, your rules.

CI-native agent CLI tool for deterministic pipeline gating.

Local-first cross-platform desktop workspace for Claude Code / agents: multi-agent, Git worktrees, code diffs, skill marketplace, multi-model, Computer Use, tas…

Local-first visual generation runtime and studio for people and coding agents, with reproducible image and video workflows across multiple providers.

A token-efficient MCP server for safe, line-oriented text file editing with partial reads, hash-based conflict detection, and atomic multi-file operations.

Open-source, evidence-driven MCP server for RTL simulation debugging: correlate VCS/Xcelium logs, VCD/FSDB waveforms, SystemVerilog/UVM source, hierarchy, and c…

runs anywhere. uses anything

One macOS app for Claude Code, Codex, and every agent runtime you use — scheduled runs, global hotkey launcher, per-run git worktrees, one review board.

Soul-driven AI agent with permission-hardened tools, token budgets, and multi-channel access. Runs 24/7 from CLI or Telegram.

Email, SMS & phone-call infrastructure for AI agents — send and receive real email and text messages, and place agent-driven outbound voice calls, all programma…

55 MCP tools to drive the Unity Editor from any MCP-compatible AI agent — scenes, GameObjects, prefabs, assets, tests, and builds. OpenClaw gateway included for…

Google Ads MCP + Meta Ads MCP + GA4 in one server for Claude, ChatGPT, Cursor & n8n — 250+ tools, hosted remote MCP, OAuth login, no API keys. By Ryze AI.

Claude Code & Codex 本地 token 追踪 — 状态栏（Codex 业界首创伪 statusline）、GitHub 风格热力图、多模型成本分析。 | Local token tracker for Claude Code & Codex — status line (industry-first…

Empower the Shell to think. Evolve Operations.

🤖 A full-stack Agent Chat Runtime for pre-production validation, built with act, TypeScript, and LangGraph JS combining streaming, multimodal, HITL, and tools…

Cerul — video memory infrastructure for AI products. SDKs, CLI, MCP, and developer integrations.

Stealth headless browser for AI agents — bypass Cloudflare, bot detection, and anti-scraping. Drop-in Puppeteer/Playwright replacement.

Web research for your agents with smart and safe tooling + knowledge store

FuXi is a fast, self-contained AI coding agent that lives in your terminal — edit code, run commands, and drive tools, with cost-aware routing across LLM provid…