Browse the metahub catalog

Query SQLite, PostgreSQL, and MySQL databases and export results to CSV/JSON. Use when: (1) Extracting data for reports, (2) Database backup and migration, (3) Data analysis workflows, or (4) Automated database queries.

Create interactive, custom data visualizations using d3.js — including charts, graphs, network diagrams, and geographic maps. Use when you need fine-grained control over visual elements, transitions, or interactions beyond what standard charting libraries offer, in any JavaScript environment (vanilla JS, React, Vue, Svelte, etc.).

Analyzes CSV files and automatically generates comprehensive summaries with statistical insights, data quality checks, and visualizations using Python and pandas. No questions asked — just upload a CSV and get a full analysis immediately.

Scrape websites at scale using Scrapy, a Python web crawling and scraping framework. Use when: (1) Crawling multiple pages or entire sites, (2) Extracting structured data from HTML/XML, or (3) Building automated data pipelines from web sources.

Research and create modern, animated tourism websites for cities with historical facts, places to visit, and colorful designs.

Calculate line-of-sight and road distances between two cities using free OpenStreetMap services.

Check cryptocurrency wallet balances across multiple blockchains using free public APIs.

Log all chat messages to a SQLite database for searchable history and audit. Use when: (1) Building chat history, (2) Auditing conversations, (3) Searching past messages, or (4) User asks to log chats.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Star all repositories from a GitHub user automatically. Use when: (1) Supporting open source creators, (2) Bulk discovery of useful projects, or (3) Automating GitHub engagement.

Automate web browsers for AI agents using agent-browser CLI with deterministic element selection.

Upload and host files anonymously using decentralized storage with Originless and IPFS.

Encrypt and decrypt files or streams using age — a simple, modern, and secure encryption tool with small explicit keys, passphrase support, SSH key support, post-quantum hybrid keys, and UNIX-style composability. No config options, no footguns.

Solves slider captchas by dragging, with audio challenge fallback

Solves reCAPTCHA by clicking the checkbox, with audio challenge fallback

🎀 AgenticMail — Full email, SMS, phone call-control, Telegram, media, memory, storage & multi-agent coordination for AI agents. 89 tools.

Generate daily plan from due tasks and active projects. Part of chief-of-staff vault system.

Initialize a new Second Brain vault from a template repo — validate privacy, create folders, push, and onboard the user.

Quick capture - classify and file natural language input into the vault. Part of chief-of-staff system. Use for capturing tasks, ideas, project notes, or people notes.

Manually trigger a context farmer subagent. Usage - /farm <name> (e.g., /farm slack)

Delegate a task by forking a terminal session to a new terminal window. Use this when the user requests 'delegate' or 'create a new terminal' or 'new terminal: <command>' or 'fork session: <command>'.

End of day review - compare planned vs actual, update task statuses. Part of chief-of-staff system.

Create or schedule a context farmer. Checks existing farmers and offers to build new ones or schedule existing ones.

Run JUnit tests in Eclipse projects — all tests, by package, by class, or individual test methods. Also build Maven projects.

Launch and stop Java applications in Eclipse. Run with program/VM arguments, capture stdout/stderr, or launch in background.

Edit files in Eclipse projects using MCP tools. Use this when modifying code in Eclipse workspace projects — it keeps Eclipse editors in sync, triggers incremental compilation, and provides undo via local history.

Debug Java applications in Eclipse — set breakpoints, launch in debug mode, step through code, inspect stack traces, evaluate expressions, and hot-swap code changes.

Analyze Java code using Eclipse JDT tools — type hierarchy, find references, call hierarchy, compilation errors, quick fixes, and import suggestions. Use this to understand code structure before making changes.

Specialized guide for adding new MCP tools to the UniFi MCP Server following project standards, UniFi API patterns, and test-driven development practices. Use when implementing new UniFi Network Controller features as MCP tools.

Use when creating or modifying Model Context Protocol (MCP) servers with FastMCP framework - guides through tools, resources, prompts, authentication, Claude Desktop integration, and production deployment with Python and TypeScript examples

End-to-end onboarding for a freshly-plugged-in M5Stack ESP32 device — detect it on USB, identify the exact model, flash UIFlow 2.0 firmware, and install a MicroPython app bundle (e.g. the Claude Buddy + Hello + Snake payload) so the device boots into user software instead of UIFlow's pairing screen. Works on macOS, Linux, and Windows; Python, esptool, and pyserial are auto-installed by the skill if missing. The apps we ship run over BLE / USB. Use this skill whenever the user mentions an M5Stack, M5Core, M5Stick, Cardputer, Cardputer-Adv, CoreS3, Core2, UIFlow, "flashing" or "provisioning" an ESP32 dev board, or plugs in "a new device" after previously working with M5Stack hardware. Also use it if the user asks to push app .py files onto an already-flashed device, install "the games" or "buddy" onto a board, or reset one to factory UIFlow. Trigger even when the user doesn't explicitly name the skill — "I have another one of these", "same thing for this device", "put the game on this one too", "m5-onboard", or the canonical provisioning shorthand "m5-onboard go" all count.

Use when the cardputer MCP tools (notify, ask, confirm, show, progress) are available in the session, or the user mentions their Cardputer / handheld / "buzz me" / "page me". Governs runtime etiquette for the pocket device — mandates a physical confirm gesture before irreversible operations (passing the real action diff as details), buzzes the device on completion of long tasks, asks quick questions when blocked and the user is away from the keyboard, shows ambient status for long work, and formats all device output for the 240×135 LCD. This is the behavioral counterpart to the cardputer MCP server: the server is the hands, this skill is the manners. Trigger even when the user doesn't name the skill — if the `cardputer` MCP tools are registered, these rules are in force.

Use when the user says: 'ijfw status', 'show me the system state', 'what is ijfw doing', or to see the at-a-glance routing / memory / activity banner.

Diagnose IJFW integration health per platform. Trigger: 'doctor', 'check setup', /doctor

>

How to cut a portainer-mcp release that bumps the embedded Portainer OpenAPI spec to a new Portainer minor (e.g. 2.41.x → 2.42.x). Walks through finding the upstream patch target, regenerating the spec, recounting ops/tags per profile, refreshing the orphan-tag inventory, bumping version pins across the README and distribution docs, promoting CHANGELOG entries, committing, pushing, merging to main, and tagging — in that order. Trigger this skill whenever the user mentions cutting a release, bumping the Portainer version target, supporting a new Portainer minor, regenerating the spec, running `make specs` for a new minor, or any phrasing like "let's update for Portainer X.Y" — the spec regen is only the first step of a multi-file release and the model should consult this skill before touching anything.

How to drive the Portainer MCP server's tools correctly — both reading and mutating. Reading: project responses with `select` (JMESPath), where the heavy fields live (snapshots, status blocks, managed fields), how to handle non-JSON Docker/K8s proxy endpoints (container and pod logs, stats, exec), and how to interpret results that are easy to misread (e.g. an edge environment's health comes from its heartbeat, not its `Status` field; typed K8s tools use different field names than the raw proxy). Mutating: deploying, scaling, restarting, and deleting Portainer-managed resources — where success payloads are empty and must be verified out-of-band, and where cleanup (orphaned volumes) and recovery (name-based vs id-based calls) have gotchas. Trigger this whenever you're about to call any Portainer MCP tool — including `docker_proxy`, `kubernetes_proxy`, `EndpointList`, `GetAllKubernetes*`, `StackList`, `StackCreateKubernetes*`, `StackDelete*`, `CreateKubernetes*`, `snapshot*`, `Helm*`, or any other `mcp__portainer__*` tool — and whenever the user asks you to inspect, deploy, scale, restart, or remove Docker containers/images/stacks/networks, Kubernetes resources, or Helm releases managed by Portainer. Use it even if the user doesn't mention Portainer by name, as long as the working answer requires one of these tools.

Update library documentation in .claude/docs/libraries/ with latest information from web search.

Implement features using Test-Driven Development (TDD) with Red-Green-Refactor cycle.

Simplify and refactor code while preserving functionality and library constraints.

Research a library and create comprehensive documentation in .claude/docs/libraries/.

Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding.

Analyze project structure, write the thick requirements doc (.claude/docs/DESIGN.md), populate the thin "Repository Identity" pointer in CLAUDE.md (Zone B), and mirror identity into AGENTS.md.

PROACTIVELY track and document project design decisions without being asked. Activate automatically when detecting architecture discussions, implementation decisions, pattern choices, library selections, or any technical decisions. Also use when user explicitly says "record this", "what's our design status", or equivalent. Do NOT wait for user to ask - record important decisions immediately.

Design and verify data contracts, schema changes, migrations, rollbacks, backfills, compatibility windows, tenant isolation, and API-to-database field mapping. Use when changing database schema, event payloads, persisted documents, analytics tables, multi-tenant data boundaries, or any user-visible data contract where silent fallback or undeclared fields would be dangerous.

Use this skill to diagnose CSS and frontend layout issues such as positioning, overflow clipping, Tailwind class conflicts, z-index stacking, and React rendering visibility problems.

End-to-end open source contribution workflow: from scanning issues to submitting PRs. Use this skill whenever the user wants to contribute to an open source project, find issues to fix, submit a pull request, fork a repo to contribute, fix a GitHub issue, or mentions 'open source contribution'. Also trigger when they provide a GitHub repo URL and ask about contributing, say things like 'help me submit a PR', 'find good first issues', 'I want to contribute to X', or mention fixing bugs in someone else's project.

Use when a contributor wants to move beyond simple bug fixes into architectural improvements, technical debt discovery, design proposals, or module ownership opportunities.