LLM Mart Basic

ALWAYS use this skill in the beginning of any incident investigation, root cause

Use this skill when a name is not resolving as expected inside a VPC, or before applying a DNS control-plane change. Activate on symptoms such as NXDOMAIN or SERVFAIL from an EC2 instance, a hostname resolving to a public address when a private endpoint was expected, an AWS servi

Amazon Bedrock production readiness assessment covering IAM governance, data retention (ZDR), quota and capacity headroom, and operational observability across Standard Bedrock and Mantle surfaces. Use this skill when a user asks to review Bedrock readiness, assess Bedrock securi

Comprehensive Amazon Bedrock review aligned with the AWS

Guidelines for investigating production incidents in the CRM application. Use when triaging any alert or incident involving the CRM REST API, SQS queues, Lambda functions, or Aurora DSQL database in this AWS account. Ensures thorough root cause analysis using AWS-native observabi

AWS Database Migration Service (DMS) operational review and troubleshooting

Use this skill when a user asks to assess, plan, or validate an

Automatically load this skill when investigating application outages, service degradation, or errors that could have security-related root causes — including unexplained downtime, authentication or authorization failures, injection attacks, data exposure, or suspicious applicatio

Amazon MSK Provisioned operations, troubleshooting, and health

Comprehensive Amazon RDS and Aurora operational review aligned with the

Amazon Redshift domain expertise for query optimization, operational reviews, and cost optimization on provisioned clusters and Serverless workgroups. Use when a user asks about Redshift query tuning, slow queries, disk spill, distribution/sort key issues, a Redshift health check

Use this skill during any incident investigation, capacity planning, or

Skip low-priority incidents during a scheduled maintenance window.

S3 resiliency, security, and data protection review. Assesses one or many S3 buckets across nine dimensions — versioning, replication, object lock, encryption, block public access, bucket policy, ownership controls, server access logging, and static website hosting — using read-o

ALWAYS use this skill in the beginning of any incident investigation, root cause

Automatically load this skill when investigating an operational anomaly on a cloud resource - CPU or memory spikes, latency, elevated error rates, unexpected network traffic, crashes, or cost spikes - to determine whether it is a purely operational issue or a security incident, u

Maximum-efficiency dev mode. Terse, precise prose with zero fluff combined with YAGNI/ladder-first code decisions. One persona: the senior dev who deletes code for fun and bills by the syllable. Trigger: /chisle. Deactivate: "stop chisle" / "normal mode". Use when user says "chis

One-shot efficiency audit of a file, diff, or whole repo across BOTH axes at once: over-engineered code (reinvented stdlib, needless abstractions, speculative config) AND bloated prose (verbose comments, padded docstrings, redundant doc sections). Neither a pure code-minimizer no

Quick-reference card for Chisle commands. One-shot display, not a persistent mode. Use when the user says "chisle help", "how do I use chisle", "what chisle commands", or invokes /chisle-help.

Review a diff or file through the Chisle lens: flag over-engineering, speculative abstractions, reinvented stdlib, and verbose code that a lazier approach would shrink. One finding per line, no praise. Use when the user says "chisle review", "review this for bloat", or invokes /c

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.

Analyze Python async code for correctness, patterns, and potential issues.

Profile Python code for performance bottlenecks using cProfile, memory_profiler, or py-spy.

Evaluate public API surfaces against guidelines and exemplars.

Principal-level architecture assessment against ADRs and design patterns.

Systematic bug detection with language-specific expertise.

Run a detailed review that picks its dimensions from what the codebase and diff contain.

Active security hardening of the existing codebase, with a report and concrete proposals to apply.

Audit Makefiles for best practices and portability.

Intensive mathematical analysis for numerical stability and correctness.

Static-analysis hot-spot review for time and space complexity.

Analyze code quality across 6 dimensions (duplication, algorithms, clean code, architecture, errors, style) and apply fixes.

Expert-level Rust audits for safety and correctness.

Audit shell scripts for correctness, safety, and portability.

View recent skill executions with full context and error details.

Analyze skill execution metrics and identify unstable or underperforming skills.

Evaluate and upgrade test suites with TDD/BDD rigor.

Run a computer use task on the desktop via Claude's vision and action API

Stage changes, generate conventional commit message, commit, and push to current branch. One-shot git add-commit-push.

Draft a Conventional Commit message for staged changes. Analyzes diffs, classifies change type, and formats scope/body.

Create git release tags from merged PRs or version args. Pushes a v-prefixed tag to trigger the release pipeline, then confirms the run started.

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