4,247 artifacts
Every listing is pinned to a commit and evaluated before it goes public.
Julian project tools — deploy, manage, and interact with Julian instances
Vibes is for people who use Claude Code, but don't know how to code.
Natural language interface for Apple Mail — search, compose, triage, organize, and analyze email with 24 MCP tools and an expert email management skill
🎀 AgenticMail — Full email, SMS, phone call-control, Telegram, media, memory, storage & multi-agent coordination for AI agents. 89 tools.
MCP server for AgenticMail — give any AI client real email, SMS, and phone call-control capabilities
Sanity plugin for Claude Code with MCP server, agent skills, agent rules, and slash commands.
OpenAI Codex CLI integration for AgenticMail — surfaces every AgenticMail agent as a native Codex subagent and wires the dispatcher daemon to the Codex SDK
Claude Code integration for AgenticMail — surfaces every AgenticMail agent as a native Claude Code subagent so any Claude Code session can delegate to them with the Agent tool
Drive the ServiceGraph API — metrics-enriched business datasets for founders (agencies, directories, newsletters, and more). Ships a branded servicegraph skill that works against any dataset, plus 14 specific skills for the US professional-services catalog (law, marketing, consulting, accounting, IT services, engineering, HR, PR, design, and more) and 3 product-directory skills for where to launch a software product and earn backlinks (general product/SaaS directories, MCP-server registries, and AI-tool/agent directories).
Email, SMS & phone-call infrastructure for AI agents — real email addresses, phone numbers, and agent-driven outbound voice calls
AST-aware Go code analysis for AI agents. Provides 57 semantic query tools covering call graph traversal, blast radius analysis, interface resolution, type usage, architecture boundary enforcement, static policy checks, Mermaid architecture diagrams, error flow tracing, and workflow telemetry. Replaces grep-based file exploration with precise, token-efficient structural queries over your Go repository. Respects .gitignore and skips AI agent worktree directories automatically.
A personal AI tutor based on Bloom's 2-sigma research: it generates a structured syllabus, teaches one adaptive lesson at a time, and tailors each next lesson to the learner's highlights and feedback. Bundles the bloom-tutor tutoring skill plus six learn-* learning-method skills.
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.
Connect Claude Code to Outline for document search, reading, creation, and management
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)
PMAT - Zero-config AI context generation and code quality toolkit with Claude Code Agent Mode
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.
Project Analysis and Intelligence Modeling Toolkit
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.
Antigravity CLI plugin for safe Google Apps Script development via ggsrun MCP and sandbox guardrails.
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.
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.
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.
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.
Domscribe is a pixel-to-code development tool that maps running UI elements to their exact source locations, capturing runtime context (props, state, DOM) for handoff to coding agents via MCP.
Modular iOS development automation suite. 8 workflow-specific MCP servers (600-3500 tokens) with 23 tools across Xcode, Simulator, and IDB. Enable only what you need!
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
Excel MCP Server & CLI - 23 tools, 214 operations for AI-powered Excel automation via COM API
AI efficiency framework. Smarter output, intelligent routing, persistent memory, context discipline, project workflows. One install. Zero config. It just fucking works.
Cross-platform persistent memory server for IJFW. 14 MCP tools (memory + admin/update + brain). Works with 15 platforms: 14 via MCP (Claude Code, Codex, Gemini CLI, Cursor, Windsurf, Copilot, Hermes, Wayland, OpenCode, QwenCode, Cline, KimiCode, OpenClaw, Antigravity) plus Aider via the rules-only tier.
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.
One-command installer for IJFW -- the AI efficiency layer. One install, every AI coding agent, zero config.
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 dockerproxy, kubernetesproxy, EndpointList, GetAllKubernetes, StackList, StackCreateKubernetes, StackDelete, CreateKubernetes, snapshot, Helm, or any other mcpportainer 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.