LLM Mart Basic
@llm-mart · Joined Jun 2026
The most important actions and content in a UI should be visually prominent — through size, colour, weight, and position. Visual hierarchy guides the user's eye to what matters most and signals which action is primary. Use when designing button groups, CTAs, dashboards, cards, or
UI must comply with WCAG 2.2 Level AA, as required by the European Accessibility Act (EN 301 549). Do not deviate without deliberate justification. Disabled UI elements are explicitly exempt from colour contrast requirements. Use when designing, building, or reviewing any user-fa
Install, observe, tune, and enforce Sponsio: a runtime contract layer for LLM agents that blocks unsafe tool calls and scores output quality against declared rules. Use when the user wants to set up / add / install Sponsio, add guardrails or runtime safety to an LLM agent, genera
Use after `/plugin install sponsio-claude-code` to wire the runtime end-to-end. The plugin install only registers hooks + skills; the contract library and per-environment overrides are configured here. Bootstraps the per-plugin contract library tree at ~/.sponsio/plugins/, instal
Use after installing the sponsio-openclaw plugin to wire the runtime end-to-end. The plugin install only registers hooks + skills; the contract library and per-environment overrides are configured here. Bootstraps the per-plugin contract library tree at ~/.sponsio/plugins/, gener
Install, observe, tune, and enforce Sponsio: a runtime contract layer for LLM agents that blocks unsafe tool calls and scores output quality against declared rules. Use when the user wants to set up / add / install Sponsio, add guardrails or runtime safety to an LLM agent, genera
Make a project ready for AI agentic engineering by converging it toward a canonical agent-neutral structure — a lean AGENTS.md index with progressive disclosure, shared skills and gitignore hygiene. Re-runnable, and doubles as an audit.
Check how much of a ticket is already implemented — split it into requirement blocks, judge each against the code, and save a human-readable TICKET-STATUS report in the planning dir.
Draft, rewrite, or refine a doc for maximum token economy without losing any rule or intent. Use for docs kept in version control and regularly re-read by agents; skip throwaway docs like plans.
Author or refine a skill for maximum token economy without losing intent. Use when creating any new skill or editing an existing `SKILL.md`.
Audit what auto-loads into an agent session's context window and suggest lean, reversible fixes to cut startup tokens.
Turn a refined requirements document into a structured implementation PLAN.md a fresh session can execute. Planning only — decides the "how", not the "what". Invoke manually only.
Turn a ticket or requirements document into a concise QA manual-test file a non-author can follow. Invoke manually only.
Execute one task from a plan's task breakdown, verify it, tick it off, and hand back for review before the next one.
Fetch all reviewer comments from a pull request URL (GitHub, Azure DevOps, …) and save them as a self-contained markdown PR-REVIEW file in the task's planning directory. Fetch only — no fixing or replying.
Fetch one or more tickets/issues from their tracker (Azure DevOps, Jira, GitHub, …) and save each as a self-contained markdown ticket file. Fetch only — no analysis or planning.
Fresh-eyes review of a changeset by a fresh-context agent — catches regressions and correctness issues the authoring context reads past.
Use when handing finished work over to code review — writing a PR description or packaging a change for review by a human, an agent, or both.
Review someone else's pull request as the maintainer deciding whether it merges — every prior comment walked, every claim verified, and nothing posted without your go-ahead.
Audit the current project's agent-memory and, block by block, relocate each entry into a user-controlled home (project doc/skill/rule or user-level skill/rule) or archive it — draining memory so nothing uncontrolled accumulates in the agent's context.
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.
/deploy-software
Deploy software
Stage and reconcile an ImmyBot desired-state software deployment to a tenant or computer
/list-computers
List computers
List and filter ImmyBot-managed computers, optionally scoped to a tenant
/maintenance-status
Maintenance status
Show ImmyBot maintenance session status — active sessions, or detail and logs for a specific session
/run-script
Run script
Find and execute an ImmyBot PowerShell script on a target computer (destructive, SYSTEM context)
/search-software
Search software
Search the ImmyBot software catalog (per-tenant + global)
/drift-report
Drift report
Portfolio-wide Inforcer baseline drift report — every managed tenant's alignment vs its assigned baseline, classified aligned / semi-aligned / drifted and sorted drifted-first, with secure score
/tenant-posture
Tenant posture
Single-tenant Microsoft 365 posture snapshot from Inforcer — secure score plus alignment score, band, and the per-policy drift detail against the tenant's assigned baseline
/classify-email
Classify email
Get an Ironscales AI verdict on a raw email, then act on it with a remediation action
/triage-incidents
Triage incidents
Triage open Ironscales phishing incidents — list by status and severity, investigate, and remediate
/get-quote
Get quote
Get a Kaseya Quote Manager quote with its sections and line items
/get-sales-order
Get sales order
Get a Kaseya Quote Manager sales order with its lines and payments
/list-quotes
List quotes
List Kaseya Quote Manager quotes, optionally scoped to a recent window
/add-note
Add note
Add a note or comment to an existing Autotask ticket
/check-contract
Check contract
View contract status, entitlements, and remaining hours for a company or specific contract
/check-pricing
Check pricing
Check pricing details for an Autotask product or service from price lists
/create-quote
Create quote
Create a new Autotask quote with line items for products, services, and service bundles
/create-ticket
Create ticket
Create a new service ticket in Autotask PSA
/expenses
Expenses
Use this skill when working with Autotask expense reports - creating reports, adding expense items, searching by status or submitter, and tracking reimbursable and billable expenses
/lookup-asset
Lookup asset
Search for Autotask configuration items/assets by name, serial number, or company
/lookup-company
Lookup company
Search for Autotask companies by name, ID, or other attributes
面向中文开发者的 Claude Code Skills / Agents / Plugins 精选与原创技能库|按场景分类|复制即装|持续更新
17 views 0 likes原生 macOS Git 客户端,以 Agent 驱动仓库管理、审阅与协作。
15 views 0 likesA 股短线复盘看板:涨停池·连板梯队·龙虎榜·板块资金一屏看完,赚钱效应/晋级率/梯队断层/情绪周期等派生指标纯计算直出(不经过 AI),AI 只把数据串成能读的盘面研判。全本地运行,可用 Claude/Codex 订阅免 API key。| A-share short-term daily-review dashbo…
6 views 0 likes禁漫天堂 Agent Skills / AI 原生 JMComic 助手:通过 MCP 与 Skills 将 JMComic 注入你的 AI Agent. / AI-powered JMComic assistant for seamless integration with AI Agents via MCP & S…
13 views 0 likesPairlet (formerly CC Pocket / cc-pocket) — Continue your local AI coding tasks from phone, tablet, or desktop.
16 views 0 likesSelf-hosted Personal AI + agent runtime in .NET (NativeAOT-friendly)
7 views 0 likesA self-hosted knowledge platform for humans and AI agents — publish wikis, blogs, and portable Agent Skills.
14 views 0 likesNotion CLI with AI agent support. Smart queries, Obsidian sync, batch ops, backups, validation and more.
8 views 0 likesAI Coding Agent Multiplexer
16 views 0 likesIndependent executor–verifier orchestration for software changes.
9 views 0 likesAI-native, local-first video editor by Ribbi — runs entirely in the browser. Rust/WASM engine, WebGPU compositing, WebCodecs export; humans and LLM agents edit…
8 views 0 likesDistill your knowledge, memories, and decisions into an open-source, inspectable AI Agent Twin.
11 views 0 likes🔬 Harness Vibe Research with Self-evolving AI Scientists
3 views 0 likesPersonal AI desktop agent for Windows, macOS, Linux, Android & iOS. Set a goal, it works on its own. Teams (pair two desktops, agents + humans), Agent2Agent, Wo…
5 views 0 likesRun agents like a company. AgentOS is the native control plane for OpenClaw — manage agents, tasks, models, context, approvals, and runtime visibility from one…
15 views 0 likesCreate Agentic admin panels faster on TypeScript and Vue.js with AdminForth Framework. Setup main CRUD pages within minutes, extend as you need
9 views 0 likesOpenJudge: A Unified Framework for Holistic Evaluation and Quality Rewards
18 views 0 likesAn ebook reader with a self-evolving agent: it remembers your reading across books, and plugins extend the reader and the agent alike.
12 views 0 likesA curated list of awesome resources for vibe coding
14 views 0 likesAgentic Voice Notes for iPhone and macOS - Rust, Dioxus, LanceDB + RIG + SQLite
9 views 0 likes