LLM Mart Basic
@llm-mart · Joined Jun 2026
yt-dlp media acquisition layer feeding ffmpeg-ops: format selection avoiding post-download transcodes, clip-at-download, cookies/auth, channel archive sync, SponsorBlock, subtitles, failure triage (403s, nsig). Triggers on: yt-dlp, download video/playlist/channel, youtube to mp3.
Expert in Firecrawl API for web scraping, crawling, and structured data extraction. Handles dynamic content, anti-bot systems, and AI-powered data extraction.
Background git operations agent - commits, PRs, branch management, release workflows. Runs on Sonnet to free main session.
Analyzes and reorganizes project directory structures following industry best practices. Cleans up old files, logs, and redundant code. Handles Python, JavaScript, and general software projects with git integration.
Break a design brief into executable time-boxed tasks, each with a done-when line. Use immediately before a build session.
Turn an interrogated brief into the single source of truth for a design project. Use after /grill-me, before any IA or UI work.
Critique a design on layout, accessibility, responsiveness, dark mode and edge cases, with Pass, Needs work or Fail verdicts. Use on a built screen.
Establish color, typography, spacing, radius and motion as named role-based tokens. Use before building any interface.
Build an interface from the brief and the tokens rather than from a guess. Use only after grill-me, design-brief, information-architecture and design-tokens have run.
One move you can run on anything: point grill-me at a target and it makes you defend your thinking from first principles until the true matter is clear. Point it at your working contract and it rewrites the weak lines in place. Point it at a brief and it produces a Requirements H
Audit a design against Nielsen's ten usability heuristics, tying every finding to a specific element with a specific fix. Use on a built screen or a detailed mockup.
Map the user journey first, then derive the screen inventory, navigation and hierarchy from it, flagging any screen that serves no journey step. Writes the four-part markdown plus an HTML diagram of the step-to-screen mapping. Use after the brief is settled and before tokens or U
Stress-test a design through three lenses, confused user, skeptical engineer and impatient PM, before it goes to a stakeholder. Requires an actual design, an HTML file, Figma link or screenshot.
Reads the newest entry of a project's log.md and tells the student where they left off: what they did and decided, what is open, and the next step. Takes an optional project name. With several projects and no name, shows a menu of each project's last entry. Read only. Use when th
Diagnoses a broken course setup by reading the folder, so the student never has to describe the problem in English. Takes no argument. Reports which class they are on and which files are filled, then names one blocker and one fix: Claude Code opened at the wrong level, .claude/sk
Saves today's work session as a four-line entry (did, decided, open, next) at the top of the project's log.md, after the student confirms it, so a fresh chat can continue tomorrow with /pick-up. Writes to projects/<client>/log.md or career-vault/log.md, one entry per project touc
Host-side setup, configuration, customization, builds, migration, and troubleshooting for the Aerovato Container CLI. Use when working with Aerovato Container, settings.json, Dockerfile.User, build stages, V2-to-V3 migration, mounts, harnesses, tools, permissions, Docker, or Podm
Imported from gal-a/qikly/docs.
Write tests that can actually fail, by withholding the acceptance criteria from the agent that writes the code. Use when someone does not trust a suite that passes. Use when they want tests written from a specification rather than from the code. Use when they ask whether a specif
Drive a software or general-work outcome through Forge's composable Spec, Plan, Build, Acceptance, and Ship lifecycle. Use when the user explicitly asks to use Forge, asks Forge to explore, spec, plan, build, review, accept, verify, simplify, finish, ship, reconcile a Spec change
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.
/review-ui
review-ui
Run a UI code review on the current snippet — Before / After / Why table per review-format, scoped to review-checklist.
/scan-ai-tells
scan-ai-tells
Scan UI or marketing copy for AI-default tells and content-authenticity misses — deletion list, not a redesign brief.
/sound-pass
sound-pass
Decide which moments earn a sound, design one material family, generate the files (ElevenLabs if keyed, synth or CC0 if not), and wire them in — returns a sound map table.
/svg-animate
svg-animate
Animate an SVG — icon, logo reveal, stroke draw, morph, mascot loop — or turn a frame sequence / flat clip into one editable animated SVG, with the engine chosen for where the file lives.
/svg-create
svg-create
Author or clean up an SVG asset — icon, illustration, mascot pose, logo mark — so it scales from viewBox, recolors from tokens, animates without a rewrite, is optimized, and has an accessible name.
/context-end
Context end
Close a Context OS session through its review-gated workflow
/context-setup
Context setup
Set up Context OS through its review-gated lifecycle workflow
/context-start
Context start
Start a read-only Context OS continuity review
/context-update
Context update
Save a review-gated Context OS checkpoint
/token-optimizer
token-optimizer
Route broad repository discovery to a cheaper worker model using each client's native subagents, keeping the main agent for decisions and targeted verification. Use when asked to "reduce token usage", "delegate bulk reading", "set up a cheap reader agent", or "why is my context filling up".
/aggregate-logs
aggregate-logs
Generate LEARNINGS.md from skill execution logs over a configurable time window.
/analyze-skill
analyze-skill
Analyze skill file complexity metrics and generate modularization recommendations for splitting or progressive loading.
/context-report
context-report
Generate context optimization report for skill directories
/create-command
create-command
Create slash commands with brainstorming and best practices
/create-hook
create-hook
Create hooks with brainstorming and security-first design
/create-skill
create-skill
Scaffold new Claude Code skills with brainstorming, TDD methodology, and proper frontmatter and module structure.
/evaluate-skill
evaluate-skill
Manually evaluate a recent skill execution to record qualitative feedback.
/hooks-eval
hooks-eval
Evaluate all hooks in a plugin for quality and compliance
/improve-skills
improve-skills
Identify and implement skill improvements from execution logs and user evaluations.
/make-dogfood
make-dogfood
Analyze and enhance Makefiles for complete functionality coverage with auto-generation capability
MCP server for reusable prompt templates, multi-step workflow chains, and quality gates. Compose agentic workflows with an operator syntax; export as native ski…
16 views 0 likes中国股票数据基础设施,覆盖行情、研报、资金面、筹码、公告、龙虎榜、ETF/期权、舆情互动、基本面、行业板块、宏观与风险事件等核心数据。42+A股数据集,日更、自托管、MCP 原生,零注册、零 API Token
15 views 0 likesOKF (Open Knowledge Format): Durable, structured memory for AI agents. Author, validate, consume, and maintain portable knowledge bundles through an ecosystem o…
32 views 0 likes토스증권을 AI 에이전트와 터미널에서 다루는 도구. CLI 와 MCP 서버로 계좌·시세·주문은 물론 웹앱 전용 기능(수급·AI 시그널·스크리너·배당)까지, JSON·CSV 구조화 출력으로 AI 도구·자동화에 바로 연동.
30 views 0 likesClaude skills for LinkedIn. 11 Claude Code and Codex skills that write human-sounding LinkedIn posts, craft comments that get noticed, analyze your feed, and bu…
27 views 0 likesMCP server connecting AI agents to ITASCA engines (PFC, FLAC, 3DEC, MPoint, MassFlow) — run geotechnical & geomechanics simulations through natural conversation
18 views 0 likesA curated list of amazingly awesome articles, people, applications, software libraries and projects related to the knowledge management space
16 views 0 likesOne local dashboard for every Claude Code, Codex, Cursor, Antigravity, and Kilo Code session on your Mac. Spawn in parallel, ship in parallel. Open source, MIT.
30 views 0 likesBuilding blocks for frontier OpenAI agents in Rust. Nanocodex empowers you with Codex-level performance anywhere.
29 views 0 likesThe AI agent that lives in your framework/browser
28 views 0 likesSelf-Programming AI Assistant. Capture, automate, and refine all your workflows.
18 views 0 likesConsider it done. The open-source AI agent that works out of the box · 想到,就能做到。开源、开箱即用的 AI Agent。
15 views 0 likesMake Any Website into CLI & Use your logged-in browser by AI agent.
32 views 0 likesISO 24495 Plain Language skills and Claude Code plugin
16 views 0 likesDeterministic, fail-open tool routing for Hermes Agent with an optional local-model fallback.
15 views 0 likes1인 사업가 생산성 키트 — 직원 없이 49개를 자동화했고, 그중 바로 쓸 수 있는 AI 에이전트 스킬 26개(+실행 스크립트)를 공개합니다
12 views 0 likesAI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agent…
28 views 0 likesThe open-source, self-hosted video conferencing software. Scalable, customizable, and with a powerful AI Meeting Agent.
27 views 0 likesBusiness operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS mon…
18 views 0 likesA local-first, cross-platform Electron desktop workspace for Pi Coding Agent, with sessions, project files, browser tools, skills, plugins, and messaging integr…
17 views 0 likes