Claude Skills by dinglebear-ai

tailscale-rmcp MCP server — query and manage your Tailscale network from Claude. Use this skill whenever the user mentions Tailscale devices, tailnet status, VPN nodes, MagicDNS, Tailscale ACL, access control policy, subnet routes, tailnet members, API keys, or wants to authorize or delete a device. Trigger phrases include: "list my Tailscale devices", "show tailnet status", "what's on my tailnet", "check my VPN devices", "Tailscale ACL", "MagicDNS", "Tailscale DNS", "tailnet users", "authori...

RAG synthesis prompt for axon ask — source-grounded, depth-adaptive, injection-hardened. Loaded at runtime by src/vector/ops/commands/ask/synthesis_prompt.rs.

Route web search, source indexing, extraction, RAG, jobs, and watch tasks through the local Axon CLI.

Use when extracting structured company lists from public or authorized directories into JSON, CSV, CRM-ready lists, or research tables.

Monitor competitor pricing, features, changelogs, dashboards, and product changes with Axon. Use for recurring competitive intelligence, pricing tier extraction, feature change tracking, or structured competitor alerts.

Use Axon site-scope source indexing to capture many pages from a site or scoped documentation section.

Use when the user needs dashboard reporting from authorized browser-accessible pages; use external browser automation for login/UI interaction and Axon for public scrape/screenshot captures or exported artifacts.

Use when the user explicitly needs a rigorous, cited, formal research report on a complex scientific, technical, policy, or market topic.

Use when the user needs a product walkthrough from authorized browser automation, with Axon used for public page scrape/screenshot evidence or captured URLs.

Save website or documentation content locally with Axon map, scrape, site-scope source indexing, output-dir, and screenshots.

Use Axon extract for schema-shaped, LLM-assisted structured extraction from one or more URLs.

Use when crawling docs, ingesting source families, building or refreshing a Qdrant-backed RAG corpus, capturing docs sections, or producing LLM-ready markdown.

Use when indexing docs portals where Axon Chrome rendering, capture-time automation scripts, or host browser-assisted URL discovery are needed.

Use when generating CRM-ready lead lists from public or authorized sources with axon search, research, scrape, map, or extraction.

Produce pre-meeting lead intelligence briefs with Axon. Use when the user needs company research, person research, recent news, talking points, pain points, or outreach preparation before a sales call, partnership meeting, investor conversation, or customer interview.

Use Axon map to discover URLs on a site before scraping, crawling, or extracting.

Use for informational market, industry, company, earnings, or public financial research with Axon, not personalized investment advice.

Use Axon source watches and job monitoring to track recurring source changes and observe durable job activity.

QA test a live website with Axon discovery/content evidence plus browser automation when interaction is required. Use when the user wants exploratory QA, form testing, navigation/link checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.

Use when the user wants a literature review, paper summary, research landscape, or sourced synthesis from papers, reports, abstracts, or converted PDFs.

Use Axon scrape to turn one or more known URLs into markdown, HTML, JSON, or saved artifacts.

Use Axon search and research to discover current web sources and queue bounded indexing when available.

Use when auditing SEO with axon map, scrape, search, rendered checks, metadata review, sitemap/site analysis, SERP comparison, or scraped-page findings.

Use when the user wants Axon-backed product research, product comparisons, review synthesis, budget-aware recommendations, or cart preparation without checkout.

Use Axon for RAG, web search, source indexing, extraction, memory, and grounded answers over indexed docs, repos, feeds, or web content.

Use when the user wants an agent-ready DESIGN.md derived from a site's observable visual language using Axon brand, scrape, and screenshot evidence.

Route outcome-focused Axon requests only when no more specific bundled workflow skill is already selected.

Use when the user wants to inspect or manage Arcane Docker resources through rarcane, including projects, containers, images, networks, volumes, registries, vulnerability scans, image updates, environments, system operations, or GitOps syncs.

This skill should be used when the user asks to "search logs", "check errors", "tail logs", "show recent logs", "find log entries", "correlate events", "list hosts", "log stats", "syslog", "check homelab logs", or mentions system logs, syslog, log analysis, or log intelligence across homelab hosts.

This skill should be used after running cortex action=abuse_investigate to analyze the resulting evidence bundle. Use when the user asks to assess frustration incidents, evaluate abuse signals, analyze agent or user friction, produce a frustration report, or follow up on abuse_investigate results.

This skill should be used after running cortex assess hooks [--hook <name>] (or the underlying hook_investigate MCP action that produces HookIncidentEvidence) to analyze why a Claude Code/Codex/Gemini hook failed, timed out, misfired, or otherwise degraded the agent session. Use when the user asks to assess hook reliability, evaluate why a PreToolUse/PostToolUse/Stop/SessionStart hook failed or blocked a flow, propose hook script or hook-config changes, or follow up on hook incident evidence.

Triage and manage cortex-detected incidents — unacknowledged error signatures, recent notification firings, similar past incidents, and full incident context around a time window. Use whenever the user asks "what errors haven't been addressed", "what's still firing", "have we seen this before", "ack this error", "acknowledge this signature", "what notifications went out recently", or wants a full picture of what happened around an incident.

Tail or follow cortex service logs from Docker Compose. Use when the user asks for cortex service logs, startup logs, crash logs, plugin deployment logs, Docker logs, or follow mode. This is for the service's stdout/stderr, not client syslog entries.

This skill should be used after running cortex assess mcp <tool-or-server> (or the underlying cortex sessions mcpinvestigate pipeline that produces McpIncidentEvidence) to analyze why an MCP tool or server call failed, misfired, or confused the agent. Use when the user asks to assess MCP tool reliability, evaluate why a tool call failed or was misused, propose tool-doc or server-config changes, or follow up on MCP incident evidence.

This skill should be used when the user asks for a homelab health report, syslog summary, fleet status report, log analysis summary, 'what happened in the last 24 hours', 'show me this week's errors', 'summarize recent activity', or any time-bounded log analysis that should produce a written markdown report.

Search and explore AI/Claude/Codex conversation history stored in cortex. **Trigger when:** the user asks to "search sessions", "find conversations", "what did I work on", "session history", "past conversations", "ask history", "when did I last use X", "show recent sessions", "list AI projects", "what tools have I used"; OR when **referencing past work** like "we've done this before", "we fixed something similar", "haven't we implemented this", "this was already working", "why did we do that ...

This skill should be used after running cortex assess skill <skill> (or the cortex sessions skillinvestigate pipeline that produces PR 3's SkillIncidentEvidence) to analyze whether a Claude Code/Codex/Gemini skill performed well. Use when the user asks to assess skill quality, evaluate why a skill failed or underperformed, propose SKILL.md doc changes, or follow up on skill incident evidence.

Answer homelab topology and cross-host correlation questions using cortex's graph-backed inventory — what services run on a host, what depends on what, fleet-wide heartbeat state, correlating events across hosts around a point in time, and graph entity/neighborhood/explanation queries. Use whenever the user asks "what's running on <host>", "what depends on <service>", "fleet health", "what else happened around this time", "correlate this across hosts", or wants an evidence-backed explanation ...

Troubleshoot cortex connection failures, missing logs, unhealthy containers, restart loops, or vague "logs aren't working" reports.

Check whether the running cortex Docker container matches the local Compose image. Use when the user asks whether cortex is current, stale, deployed, updated, running the latest plugin image, or needs a restart/recreate after an upgrade. Supports an optional --pull mode for Docker image comparison.

Use this skill whenever the user asks about their UniFi network — connected clients, who's on the WiFi, which devices are online, access points, switches, gateways, network health, site health, active alarms, network events, WiFi configurations (SSIDs), controller sysinfo, or their authenticated UniFi identity. This skill covers the unifi-rmcp MCP server, a Rust bridge to official and internal UniFi APIs via X-API-KEY. Legacy convenience actions are read-only; mutating actions require explici...

Send push notifications through apprise-rmcp — a standalone Rust MCP bridge to the Apprise universal notification library (Slack, Discord, email, Telegram, and 100+ more). Use this skill whenever the user wants to send a notification, push an alert, notify a service, fire off a push message, or use Apprise in any way — even if they just say "send me an alert" or "let me know when X is done". Covers three tiers: MCP tool (preferred), CLI binary, and direct REST API curl calls. Trigger phrases ...

How to interact with the Gotify self-hosted push notification server via the gotify-mcp MCP tool, CLI binary, or direct REST API. Use this skill whenever the user wants to send a push notification, check notification history, manage Gotify applications or clients, check Gotify server health, delete messages, or do anything with Gotify — even if they just say "send an alert" or "notify me when X is done". Also invoke this when the user asks about notification history, wants to know if their Go...