LLM Mart Basic
@llm-mart · Joined Jun 2026
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.
/create-component
Create component
Guided component creation with proper patterns
/design-review
Design review
Review existing UI for issues and improvements
/design-system-setup
Design system setup
Initialize a design system with tokens
/test-generate
Test generate
Generate unit tests for Python, JavaScript/TypeScript, and React code with mocks, edge cases, and coverage gap analysis
/backlog-from-demo
Backlog from demo
Turn a recorded product demo into a prioritized backlog with timestamped evidence.
/bug
Bug
Turn one screen recording of a bug into an evidence-backed GitHub issue draft (quote, frames, OCR identifiers, wall-clock; silent recordings work too).
/correlate-with-logs
Correlate with logs
Walk a recording's remarks against system logs using wall-clock timestamps.
/meeting-actions
Meeting actions
Turn a recorded meeting (audio is enough) into action items, decisions, and open questions with timestamps.
/spec-from-workshop
Spec from workshop
Turn a recorded workshop or design walkthrough into a structured spec with quoted decisions and open questions.
/triage-recording
Triage recording
Turn a narrated screencast into precise, evidence-backed findings JSON (bug / feature / question routing with frame evidence).
/ai-governance
ai-governance
Generate and enforce policy gates for AI coding agents (Copilot, Claude Code) — real-time session hooks that deny protected-path edits and dangerous commands, plus a merge-time backstop for anything that bypasses them. Use when asked to "govern AI agents", "block AI from touching secrets", "add an AI policy gate", or "why did the AI agent hook not fire".
/pwf-status
Pwf status
Show the active planning-with-files plan (id, mode, attestation, current phase, phase counts)
/pwf
Pwf
Start planning-with-files (task_plan.md, findings.md, progress.md); flags --gated, --autonomous, --template analytics, then an optional plan name
/ad
Ad
Run a paid-ads (ROAS) workflow: audience segments, account structure, ad creative, experiment design, pre-launch signal QA + the account-audit gate, measurement, and attribution. Not sure? Use /aaron-marketing:auto.
/auto
Auto
Natural-language front door to the marketing pack (narrative/TALE, SEO/GEO/SITE, social/ECHO, email/SEND, Paid Ads/ROAS, influencer/STAR, launch/RAMP). Use when a marketing goal is open-ended or spans disciplines, when it is unclear which skill fits, or for requests like 'help with our marketing', 'grow our traffic', 'plan our launch', 'what should we post', 'is our messaging landing' — it infers the discipline and runs the smallest useful workflow. Add --deep for exhaustive, maximum-rigor, or stress-test runs.
/email
Email
Run an email-marketing (SEND) workflow: deliverability/consent setup, segmentation, email creative, lifecycle flows, newsletter monetization, send-testing, and the email-quality audit gate. Not sure? Use /aaron-marketing:auto.
/influencer
Influencer
Run an influencer-marketing (STAR) workflow: audience & creator scouting, campaign targeting, briefs, outreach, amplification, and ROI reporting. Not sure? Use /aaron-marketing:auto.
/launch
Launch
Run a product-launch (RAMP) workflow: positioning and launch tiering, window/early-access design, message house and asset kits, the launch-readiness gate with a T-1 go/no-go, launch-day execution, and the post-launch prove loop. Not sure? Use /aaron-marketing:auto.
/narrative
Narrative
Run a brand-narrative & messaging (TALE) workflow: trace the current message and positioning truth, architect the durable message house/voice/story canon, land it consistently across every surface, and evaluate resonance with tests and drift monitoring. Not sure? Use /aaron-marketing:auto.
/seo-geo
Seo geo
SEO/GEO end-to-end along the SITE loop: survey demand and competitors, implement content, tune quality/tech/on-page, and evaluate authority/rankings/reports/memory (--phase survey|implement|tune|evaluate). Not sure? Use /aaron-marketing:auto.
Open-source, self-hosted AI media server. One server replaces your entire media stack, with a web app, native iPhone app, and an AI agent that gets things done.…
3 views 0 likesA curated list of tools built for Jev — TypeSafe AI's System One model for typed decisions.
3 views 0 likes🦦 Crayotter: A Multimodal AI-Agent for Video-Editing, Video-Composing, and Video Production. Powered by Multimodal LLMs for autonomous Text-to-Video agentic fr…
3 views 0 likesWebextension tool for Odoo
3 views 0 likes基于多模态视觉感知与 LLM Agent 的 macOS 微信自动化框架 | Visual RPA for WeChat
0 views 0 likesThe operational superset of Pi Coding Agent — everything Pi, plus observability, governance, recovery, evaluation and multi-agent orchestration. Pi Coding Agent…
0 views 0 likesMetrik 可以集中查看本机多个 Agent 的配额余量和 Token 消耗,目前支持 ChatGPT、Claude、GLM、Kimi 等主流 AI 服务。
0 views 0 likesAn AI agent with a real self — soul she wrote, desires that drive her, a heartbeat for autonomous action, dreams she processes when you're away. Capability supe…
0 views 0 likesProduction-ready open source terminal coding agent with readable, layered code: permission rules, OS sandboxing, MCP, skills, sub-agents, and Anthropic, OpenAI-…
0 views 0 likesAnswer me with HTML — an agent skill that answers hard questions with a one-page HTML you can actually read. 让 AI Agent 用一页 HTML 回答复杂问题。
1 views 0 likesPrompt packs that make any AI agent a LaTeX expert — fix errors, polish writing, format for venues, read papers, recover source
1 views 0 likesClaude Code plugin: universal radial-tree exploration engine. One tree skill + swappable presets (brainstorm / attack / design / code-audit) for divergent ideat…
1 views 0 likesClaude Code + OpenClaw + Codex + WorkBuddy 中文教程 | 50篇完整教程 + 1张速查卡 | 80万+内容量 | 1500+实操示例 | AI Coding / Agent 四线学习路径(编程+助手+Agent+办公)
1 views 0 likesSmartLabelBench 2026: LLM-Powered Auto Annotation and Dataset Builder for Everything
1 views 0 likes从零开始玩转OpenClaw:最全面的中文教程,涵盖安装、配置、实战案例和避坑指南(github版)
1 views 0 likes