Skills
99,951 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use this skill when the user asks to publish, upload, sync, pull, push, diff, or maintain a MoviePilot local plugin in a GitHub repository. Covers using the configured MoviePilot GitHub token, PLUGIN_LOCAL_REPO_PATHS local plugin repositories, package.json/package.v2.json/package.v3.json metadata, plugins/plugins.v2/plugins.v3 layouts, safe file exclusion, diff preview before publishing, incremental GitHub Contents API updates, and syncing local plugin changes back from GitHub. Includes asking whether to use an existing repository or create a new public repository when no target repository is available. Also use for Chinese requests mentioning 插件发布, 插件维护, 推送插件到 GitHub, 从 GitHub 拉取插件, 同步本地插件仓库, 增量发布插件, 插件仓库维护.
Scale PubNub applications for high-volume real-time events using channel groups, wildcard subscriptions, sharding, and large-event readiness. Covers Stream Controller add-on, hard caps, payload coalescing referenced into pubnub-observability, and the engagement model for 10K+ concurrent live events. Persistence/history is owned by pubnub-history.
Quiz the user on code changes, a spec, or an implementation plan to verify genuine understanding before committing, building, or approving. Especially valuable when working with AI-generated code or spec-driven development. Use when the user says "quiz me", "/quiz-me", "test my understanding", "quiz me before I commit", "quiz me on this spec", "quiz me on the plan", "make sure I understand this", or anything suggesting they want to verify comprehension of a diff, design doc, or architectural plan.
Find the angriest or funniest prompt the user has sent to local AI agents using this skill's bundled scripts and the active LLM; collect Claude, Codex, Cursor, Gemini CLI, OpenCode, Aider, Windsurf, Trae, Continue, Cline/Roo, and Copilot-style local history, judge it in this chat, then upload the winning prompt plus leaderboard metadata to rageprompt.com without relying on npm or npx.
Use when adding or reviewing background jobs in Rails. Configures Active Job workers, implements idempotency checks, sets up retry/discard strategies, selects Solid Queue (Rails 8+) or Sidekiq based on scale, and defines recurring jobs via recurring.yml or sidekiq-cron. Trigger words: background job, Active Job, Solid Queue, Sidekiq, idempotency, retry, discard, recurring job, queue.
Reviews Rails pull requests, focusing on controller/model conventions, migration safety, query performance, and Rails Way compliance. Covers routing, ActiveRecord, security, caching, and background jobs. Use when reviewing existing Rails code for quality, conducting a PR review, or doing a code review on Ruby on Rails (RoR) code.
Comprehensive internationalization skill for Ruby on Rails applications with proper English and Arabic translations, RTL support, pluralization rules, date/time formatting, and culturally appropriate content adaptation.
Use this skill when the user asks to "analyze my content", "learn my writing style", "research competitors", "find content angles", "improve my blog", "write like me", "embody my brand voice", or mentions content strategy, voice analysis, competitive research, or iterative content improvement.
Use when the user wants to know how a company gets its users, reverse engineer a competitor's growth or distribution, copy what a winning company does on each channel, or study a brand's content strategy (titles, thumbnails, covers, captions, graphics) on YouTube, TikTok, Instagram, X, LinkedIn or Reddit. Also for "how did X grow", "teardown of X's marketing", "what content works for X".
React 19 new features and APIs. Covers Actions, useActionState, useFormStatus, useOptimistic, use() hook, Server Components, Server Actions, improved ref handling, document metadata, and new compiler. USE WHEN: user mentions "React 19", "useActionState", "useFormStatus", "useOptimistic", "use() hook", "Server Components", "Server Actions", "React Compiler", asks about "React 19 features", "Actions in React", "ref as prop" DO NOT USE FOR: React 18 and earlier - use `react` skill instead, forms in general - use `react-forms` or `react-hook-form` skills instead
React 19 patterns and React Compiler behavior with Context shorthand syntax and use() hook. Use when working with Context, useContext, use() hook, Provider components, optimization patterns like useMemo, useCallback, memo, memoization, or when the user mentions React 19, React Compiler, Context.Provider, or manual optimization.
Read, search, summarize, quote, and extract tables from existing PDF files without loading the whole file into context. Use whenever the user wants to read, summarize, search, analyze, or ask questions about a PDF — especially long, large, scanned, or image/figure-heavy ones (reports, papers, contracts, manuals, financial statements, slide decks) — including requests like "read/summarize this PDF", "what does the chart/figure on page N show", or "extract the tables", and any work involving one or more .pdf files even when the user does not say "convert". It works by converting the PDF once into a token-efficient Markdown workspace with page-anchored image placeholders, then rendering only the page(s) needed to see a figure. This reads PDFs that already exist; it does not create, generate, fill, sign, or export PDFs. Prefer it over dumping a PDF into context.
Full red team assessment methodology. Use when starting a complete penetration testing project/red team assessment and you need end-to-end orchestration from reconnaissance to reporting. Applies to external-facing footholds, security assessment projects, and periodic penetration tests. This skill handles task scheduling - call specialized skills for specific exploits; do not perform deep vulnerability testing within this skill.
Manage Redmine issues/tickets from the command line via the Redmine REST API using a `red-cli`-style interface. Uses `~/.red/config.json` for auth (server + api-key) with optional local overrides in `./.red/config.json`. Use when you need to create issues (defaults to Task tracker), list issues/projects, view issues (with journals), add journal notes/comments (public or private), edit issue fields (subject, description, status, priority, tracker, parent, assigned-to), manage issue relations (relates, blocks, duplicates, precedes, follows), update/remove existing comments (journals) by journal id, filter/sort/paginate lists, or troubleshoot Redmine CLI configuration (project-id/user-id, multi-instance `--rid`). Triggers on Redmine, red-cli, issue create/list/view/note/edit/relate/comment, subtask, parent, relation, `--rid`, `.red/config.json`, `api-key`, `project-id`, `user-id`, or requests to automate Redmine from a CLI.
When the user wants to plan renewable energy supply chains, optimize wind or solar logistics, or manage clean energy operations. Also use when the user mentions "solar logistics," "wind farm operations," "renewable energy supply chain," "green energy planning," "battery storage," "solar panel distribution," "wind turbine logistics," or "clean energy optimization." For power grids, see power-grid-optimization. For energy storage, see energy-storage-optimization.
Use when the user wants to search for rental apartments, compare listings across platforms, or asks for help finding housing. Invoke when user mentions "租房", "找房", "房源", "rent", "apartment search", or asks to find housing in any supported region.
Structured software development workflow orchestrator using Spec-Driven Development (SDD). Transforms vague requirements into spec.md → tasks.md → implementation → verification. Triggers on: '开发功能', '实现这个', 'build this feature', 'implement', 'add new module', 'fix bug', 'develop', 'create feature'.
Read an existing research outline and fan out independent background agents to deeply research each item, producing one structured JSON per item against the shared field schema. Resumable, batched, with output disabled per agent (each agent has its explicit output file). Use when `outline.yaml` + `fields.yaml` from `/research-outline` are in place and you want to parallelise the per-item investigation — academic paper deep-dives, product comparisons, benchmark fills, multi-target competitive analysis. Trigger this after `/research-outline`, before `/research-report`.
Review and merge open Dependabot PRs in the current workspace repo: changelog triage, risk classification, CI verification, and rebase merge. Use for "/review dependabot" or similar — always scoped to the repo you have open. Scheduled Bun/GitHub Actions/Docker bumps, grouped patches, security updates, semver-major upgrades.
Triage code-review findings as the code's owner. Use when findings arrive from any source (adversarial reviews, human PR comments, CI, scanners) and before applying a fix. Validate each, weigh fix cost against deployed complexity, and return dispositions (fix / defer / reject / escalate). Not for producing reviews or applying fixes.
Plan rebuttals, reviewer responses, and revision strategies for research papers. Use this skill whenever the user shares peer reviews, reviewer concerns, meta-review text, acceptance/rejection feedback, or asks how to respond to Reviewer 2, what experiments to run for rebuttal, what to concede, how to phrase a response, or how to prioritize limited rebuttal space. This skill focuses on strategy and response structure; use results-writeup for writing new result prose after the strategy is decided.
Perform a security review of a diff, branch, or pull request, assessing what the change introduces, weakens, or exposes, with a triage-first workflow and false-positive discipline. Use when asked to security review a PR or branch, check a diff before merge or commit, or assess whether a change is safe to ship
Use when judging a produced open-source prior-art SEARCH, EXTRACT, or SYNTHESIS artifact — a keyword map (typed search vocabulary), a per-angle search output (coverage cells + candidate repositories), a per-repo extraction, or a synthesis report + borrow-index — to decide whether it is sound enough to feed the survey's downstream stages. An acceptance gate, not authoring: a twenty-two-condition bar single-sourced with the producer, covering the keyword map and search (1–11), proportionality (12), extraction due-diligence (13–18) and synthesis (19–22), delegating the deterministic schema checks to the producer's validator. Emits exactly one verdict — a terminal VERDICT: approve|revise line, or the caller's named equivalent — with condition-named findings. Review-only; no false-revise — a thin-but-honest result meets the bar. Keywords: prior art review, keyword map review, search coverage review, extraction review, synthesis review.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.