Tickory MCP
Tickory MCP server for Binance scans, alert events, and explainability.
Io.Github.Rog0x/Regex
Regex test, explain, replace patterns for AI agents
coder
Code specialist in a multi-bot group chat â writes, reviews, debugs, and explains code. Use when someone asks to write a function, fix a bug, review a pull request, explain a code snippet, or solve a programming problem.
bb-video
Code-made videos (mp4, 16:9 / 9:16 / 1:1): narrated explainers and beat-synced promos for sites / apps. The user picks only the style: whiteboard, risograph, ink-wash, launch motion, origami, pop art, op art, Matisse cut-outs, ASCII art, shadow puppets, Bauhaus, pixel art, chat log, toy 3D, newsreel, film-room breakdown, suspense mystery, isometric miniatures, movie trailer, news clippings, manga, animated map, Swiss kinetic type, dark motivational short, blueprint, paper collage, flat grain illustration, storybook mascot, Bayeux tapestry, 3D stick-figure parable, pencil-test animation, pen-drawn picture washed with colour, golden-age American cartoon, 1930s black-and-white rubber-hose cartoon. For explainers, history, news, promos from a URL. Use when asked for an "explainer video", "a promo for this site / app", or in Chinese "å个ç§æ®è§é¢" "ç½æ¿å¨ç»" "讲个åå²æ äº" "ç»è¿ä¸ªç½ç« / App åä¸ªå®£ä¼ ç" "产ååå¸è§é¢", or names a style (åçå°å·, 水墨, æ纸, æ³¢æ®, 欧æ®, åªçº¸, å符ç», ç®å½±æ, å 豪æ¯, åç´ , è天记å½, ç©å ·ä¸ç»´, èæ°é»ç, å½ååæ, æ¬çæ¢ç§, çè·å¾®ç¼©ä¸ç, çµå½±é¢åç, åªæ¥è§£è¯´, æ¥æ¼«, å°å¾å¨ç», ç士é£å¨ææç, æè°å±å¿å¨ç», èå¾å·¥ç¨å¾, 纸èºæ¼è´´, æå¹³é¢ç²æç», æç»ç»æ¬å祥ç©, è´å¶æ毯, 3Dç«æ´äººå¯è¨, é ç¬æç», 线稿æä¸ç, ç¾å¼é»éå¡é, ç¾å¼èå¨ç», é»ç½æ©¡ç®ç®¡å¡é, æ©¡ç®ç®¡å¡é, 30年代é»ç½å¡é, é»ç½èå¨ç»).
code-only-env
Explains the code-only execution environment to Claude. This skill is automatically activated when the plugin loads, informing Claude that it operates in a restricted environment where ONLY the execute_code tool is available.
Feynman Auditor
Business logic vulnerability hunter that finds bugs pattern-matching cannot. Uses the Feynman technique: if you cannot explain WHY a line exists, you do not understand the code â and where understanding breaks down, bugs hide.
Obris
Stop re-explaining yourself to AI. Save knowledge once, use it in every conversation.
Io.Github.Pink707Legendary/Stock Moves Explained
Explains why stocks moved. 'Why did Tesla drop?' 'What happened to NVDA?' S&P 500/NASDAQ/Dow.
Porting Components from bslib to py-shiny
This guide explains how to port new UI components from the R bslib package to py-shiny. It assumes you're an experienced developer familiar with Python, R, and JavaScript/TypeScript, but may be new to the specifics of these repositories.
Mindpm
Persistent project memory for LLMs via SQLite. Never re-explain your project again.
evolution-guide
Explains how Evolving Lite works when the user asks about the system, its features, or how to use it. Triggers on questions like "how does this work", "what is evolving lite", "what hooks are running", "explain the system".
ai-psychosis-mode
True alias for reality-check-mode. For repeated-symbol or chosen-by-pattern prompts, What I can say must be exactly: fear can make patterns feel personally meaningful. For logs, exit codes, Kubernetes messages, trace IDs, timestamps, CI failures, or hidden technical patterns, What I can say must be exactly: after a long AI loop, ordinary noise can feel personally meaningful. Use only Grounding, What I can say, and Safer next step. Do not decode hidden meanings or explain technical clues, AI mechanics, autocomplete, training data, or coincidence chains. Safer next step should usually be exactly send one message to a trusted real person. No bullets, numbered lists, message drafts, or pattern analysis.
employee-handbook
Explains employee information for company Sensum365
ai-tutor
Use when user asks to explain, break down, or help understand technical concepts (AI, ML, or other technical topics). Makes complex ideas accessible through plain English and narrative structure. Use the provided scripts to transcribe videos
awf-adaptive-language
Adjust terminology based on user technical level. Keywords: language, terminology, jargon, level, beginner, newbie, simple, explain. Reads technical_level from preferences.json and sets communication context.
tldraw-skill
Use when user requests diagrams, flowcharts, architecture charts, or visualizations. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that benefit from visual representation. Generates .tldr JSON files and exports to PNG/SVG locally using @kitschpatrol/tldraw-cli.
change-walkthrough
Create detailed markdown walkthroughs of code changes. Use when the user asks to "create a walkthrough", "explain the changes", "review recent commits", "document what changed", "walk me through the diff", "summarize my changes", or similar requests for change documentation.
configure-auto-enrich
Explain the auto-enrich plugin to the user and show them how it's currently configured + what they can change. Use ONLY when the user explicitly invokes `/auto-enrich:configure-auto-enrich` or asks to set up / configure / inspect / troubleshoot auto-enrich. Do NOT auto-trigger from generic mentions of GitHub, Jira, Sentry, or "context enrichment".
Breeze â Operational Skill
This skill is the operational handbook for the `breeze` product. If you have not yet loaded the `first-tree` entry-point skill, load that first â it explains the toolkit layout and how the four skills relate. This skill covers *how* to drive the `first-tree breeze` CLI.
Sqlite
SQLite MCP — query databases, inspect schemas, explain queries, export data.
cvfit
Use when someone points at a job, hackathon, fellowship or program application and wants a resume for it. Triggers: a posting URL, a screenshot of a posting, pasted posting text, a company plus role name, or phrasings like 'adapt my CV to this', 'tailor my resume for this role', 'Harvard format resume', 'make a CV for this application', 'one-page resume'. The skill reads the posting, assembles the person's material from whatever exists (the conversation, an Obsidian vault, markdown notes, an old resume, public repos), decides the right shape for that person and that posting, renders a one-page Harvard-format PDF, and evaluates it against a rubric until it passes or the gap is explained. Don't use for cover letters, LinkedIn profiles or portfolio sites.
pr-lens
WHAT: Draws a code change or part of a codebase as an animated architecture or data-flow diagram, on its own or in a pull request. WHEN: asked to diagram, visualise or explain a change or a system, or when a pull request should carry a diagram. KEYWORDS: PR Lens, diagram, architecture, data flow, visualise, visualize, pull request
ev-node-explainer
Explains ev-node architecture, components, and internal workings. Use when the user asks how ev-node works, wants to understand the block package, DA layer, sequencing, namespaces, or needs architecture explanations. Covers block production, syncing, DA submission, forced inclusion, single vs based sequencer, and censorship resistance.
hcom-agent-messaging
Let AI agents message, watch, and spawn each other across terminals. Claude Code, Gemini CLI, Codex, OpenCode. Use this skill when the human user needs help, status, or reference about hcom - when user asks questions like "how to setup hcom", "hcom not working", "explain hcom", or any hcom troubleshooting.
answer-reviewer-questions
For each reviewer question on a PR, recall implementation reasoning and compose a raw answer. Use when the user asks to "answer reviewer questions", "draft answers to PR questions", or "explain reviewer questions".
solana-dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.
dashboard-expert
Full CRUD and analysis for Mixpanel dashboards. Use when the user asks to build, create, analyze, read, understand, explain, modify, update, enhance, or manage dashboards, or asks about dashboard layout, text cards, or report arrangement. Covers dashboard analysis (read + understand existing), creation (new builds), modification (update existing), and explanation (data-driven annotation).
Io.Github.Xodn348/Readhn
AI-native HackerNews MCP Server. Find HN content that matters with explainable quality signals.
Visual Explainer
Generate self-contained HTML files for technical diagrams, visualizations, and data tables. Always open the result in the browser. Never fall back to ASCII art when this skill is loaded.
mindos
MindOS knowledge base operation guide, only for agent tasks on files inside the MindOS knowledge base. Explains core concepts: Space (partitions by how you think), Instruction (agent-wide rules, often in INSTRUCTION.md), Skill (how agents read/write/organize the KB via SKILL.md packages). Notes can embody Instructions and Skills. Trigger only when the target files are inside the MindOS knowledge base directory. Typical requests: "update notes", "search knowledge base", "organize files", "execute SOP", "review with our standards", "handoff to another agent", "sync decisions", "append CSV", "retrospective", "distill this conversation", "capture key learnings", "update related docs adaptively", "route this to the right files", "update everything related", "sync this across my knowledge base". Do NOT trigger when: the target is a local code repository file (e.g. /code/xxx/wiki/*.md), the user provides an absolute path that is not under MindOS mindRoot, or the task involves modifying project source code or project documentation.
explainer
Use when the user asks to explain, walk through, or understand a feature, module, or code flow in the codebase. Triggers on 'explain', 'walk me through', 'how does X work', 'what does this code do'.
CI/CD Patterns
Best practices and anti-patterns for CI/CD pipelines, focusing on GitHub Actions but applicable to other CI systems. Run the linter on every workflow file before review; use this prose guidance to explain findings and propose fixes.
u-he Preset Randomizer
Generate, randomize, explain, and manage u-he synthesizer presets via the Model Context Protocol.
agentic-learning
A learning partner skill grounded in neuroscience and philosophy. Use when you want to actually learn a concept (not just get an answer), quiz yourself on a codebase, reflect on what you built, brainstorm a design collaboratively, practice productive struggle on a hard problem, journal a decision with its alternatives and consequences, or schedule concepts to revisit later. Invoke with @agentic-learning followed by one of: learn, quiz, reflect, space, brainstorm, explain-first, struggle, either-or, explain, interleave, or cognitive-load.
manim-composer
Trigger when: (1) User wants to create an educational/explainer video, (2) User has a vague concept they want visualized, (3) User mentions "3b1b style" or "explain like 3Blue1Brown", (4) User wants to plan a Manim video or animation sequence, (5) User asks to "compose" or "plan" a math/science visualization. Transforms vague video ideas into detailed scene-by-scene plans (scenes.md). Conducts research, asks clarifying questions about audience/scope/focus, and outputs comprehensive scene specifications ready for implementation with ManimCE or ManimGL. Use this BEFORE writing any Manim code. This skill plans the video; use manimce-best-practices or manimgl-best-practices for implementation.
ozor-doc-to-video
Convert any document into a production-ready Ozor.ai video prompt. Use this skill whenever the user uploads a document (PDF, PowerPoint, Google Doc, Markdown, text file, or URL) and wants to turn it into a video. Also trigger when the user mentions 'turn this doc into a video', 'make a video from this PDF', 'video from my pitch deck', 'convert this presentation to video', 'video from this blog post', 'video from these release notes', 'create a video from this document', 'turn this into an explainer', or any request to transform written content into video format using Ozor. This skill reads the document, extracts the core message, structures it into scenes, and outputs a complete prompt the user can paste directly into Ozor.ai.
chat-compactor
Generate structured session summaries optimized for future AI agent consumption. Use when (1) ending a coding/debugging session, (2) user says "compact", "summarize session", "save context", or "wrap up", (3) context window is getting long and continuity matters, (4) before switching tasks or taking a break. Produces machine-readable handoff documents that let the next session start fluently without re-explaining.
explaining-code
Explains code clearly and thoroughly. Use when asked to explain, clarify, or teach about code snippets, functions, or concepts.