Skills
97,725 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use when designing or auditing free samples, lead magnets, trial offers, concessions, referral gifts, favor exchanges, freemium onboarding, consultation offers, or give-first sales strategies where reciprocity, obligation, uninvited gifts, or concession tactics may affect decisions.
A strict editorial reviewer that checks writing principles inspired by George Orwell's "Politics and the English Language" rules and Matthew Butterick's Practical Typography. Use this skill whenever the user says "red pen", "check my prose", "edit this for clarity", "typography check", "tighten this up", "review this draft for style", or wants a rigorous line-edit focused on cutting flab, killing dead metaphors, fixing passive voice, and correcting typographic errors like straight quotes, wrong dashes, and double spaces. Also use when the user asks you to be a "tough editor", "strict editor", or "copy editor", or wants feedback on prose quality rather than content or structure.
Redux Toolkit for React state management. Covers slices, thunks, and RTK Query. Use for complex global state. USE WHEN: user mentions "redux", "redux toolkit", "RTK", "createSlice", asks about "complex state management", "time-travel debugging", "middleware", "thunks", "RTK Query", "global state with DevTools", "enterprise state management" DO NOT USE FOR: simple state - use `zustand`; server data - prefer `tanstack-query`; Vue apps - use `pinia`; small projects - overhead not justified
Use when changing existing structure without changing behavior, adding characterization tests, isolating hard dependencies, consolidating APIs, migrating callers, introducing value objects or domain events, replacing null/string/generic exceptions with typed failure contracts, or removing legacy paths safely. Applies to protected incremental change, not an unverified rewrite or unrelated cleanup.
Builds compliance checklists for business scenarios involving GDPR, PIPL, or advertising/data laws. Outputs a structured checklist with check items, legal basis, risk levels, and actionable recommendations. Triggered by requests like "run a compliance check," "GDPR/PIPL compliance," "pre-launch review," "privacy impact assessment (PIA/DPIA)," or asking if a feature is compliant.
Design and audit release trains, change management, release calendars, risk classification, freeze windows, release notes, staged rollout, owner approvals, dependency readiness, rollback, support/comms, incident handoff, and post-release review. Use when shipping many product changes across apps, SaaS, games, APIs, desktop, or platform surfaces.
Reviews Remix v2 loaders and actions for mutations-in-loader, missing validation, leaked server fields, wrong return helpers, v1 useTransition holdovers, and revalidation traps. Use when reviewing loader/action code in a Remix v2 codebase.
This skill should be used when the user asks to "fix my skill" or "audit this skill". Make sure to use this skill whenever the user mentions skill quality, structural issues, broken skills, or skill diagnostics — even if they don't explicitly say "repair-skill". Not for adding features or improving effectiveness — use improve-skill. Not for agents — use repair-agent.
This skill provides comprehensive guidance for using the Replicate CLI to run AI models, create predictions, manage deployments, and fine-tune models. Use this skill when the user wants to interact with Replicate's AI model platform via command line, including running image generation models, language models, or any ML model hosted on Replicate. This skill should be used when users ask about running models on Replicate, creating predictions, managing deployments, fine-tuning models, or working with the Replicate API through the CLI.
This skill should be used when the user asks to "create a plan for replit", "break down tasks", "create development phases", "checkpoint strategy", or needs to convert a project into iterative development phases that Replit Agent can execute step-by-step with checkpoints.
Audit two or more interdependent repositories for drift, duplication, and practices one repository uses well and another lacks. Verify every finding mechanically, decide with the user, then apply surgical alignment fixes and adapted transfers per repository.
**Financial Report Downloader**: Auto-search and download A-share/HK stock financial report PDFs from Xueqiu (stockn.xueqiu.com) or 同花顺 (notice.10jqka.com.cn). - MANDATORY TRIGGERS: download report, 下载财报, 下载年报, 下载中报, annual report download, financial report PDF, 雪球财报, 同花顺财报
Run a research Workflow end to end when the user requests a survey, brief, review, tutorial, or idea exploration; route an unbound goal, execute one eligible Unit at a time, and stop at checkpoints or diagnosed failures.
Use when the user has a vague topic or area of interest and wants it sharpened into a few strong, novel, feasible research questions. Drafts candidate questions, scores each against a fixed rubric (Specific, Answerable, Novel, Feasible, Significant) with a light literature/web novelty check, and revises the weakest axis until enough questions clear the bar. Not for grading a full written proposal (use the research-proposal loop), and not for turning a question into testable predictions (use the hypothesis-generation loop).
Apply the user's research taste, priors, and critique style to research ideation, paper analysis, experiment design, evaluation planning, strategy, and technical research judgment. Use when the task is about choosing research directions, judging research ideas, designing studies, interpreting results, or deciding what work is worth doing.
(forwward) Performs paranoid code review checking trust boundaries, data integrity, performance, race conditions, error handling, and OWASP security. Triggers on code review, pre-merge checks, security audit, bug hunting, or any request to review, audit, or check code quality.
Reports vendor support phases and end-of-life dates for RHDH and the platforms it runs on: OpenShift, ARO, OSD, ROSA, AKS, EKS, GKE, PostgreSQL, Red Hat build of Keycloak, and Quay. Use for "is OCP 4.16 still supported", "when does PostgreSQL 15 go EOL", "which Kubernetes version should AKS be on", "which OCP versions does RHDH 1.10 support", or an RHBK or Quay lifecycle lookup. Product lifecycle only — RHDH milestone dates such as Code Freeze belong to rhdh-release-schedule.
Routing feature planning through the ring-pm-team pre-dev workflow: choosing the Small Track (4 gates, <2 days) or Large Track (8 gates, 2+ days) and entering via ring:planning-small-features or ring:planning-large-features. Indexes pre-dev gates, standalone utilities, and research agents. Use when starting a feature that needs systematic planning. Skip for quick exploratory work, known-solution bug fixes, or trivial changes.
Using the ring-tw-team plugin and orchestrating its documentation specialists in parallel: guide-writer (guides/concepts/tutorials), api-writer (REST API reference), and docs-reviewer (quality review). Use when creating functional or API documentation, or reviewing doc quality. Skip when writing code (use dev-team) or writing plans (use pm-team).
Writing a rolling-wave phased implementation plan from a spec before coding: a phase-epic-task hierarchy where Phase 1 is detailed into dispatch-ready tasks and later phases stay epic-level for elaboration during execution. Use when a multi-file feature needs decomposition; runs after ring:exploring-codebases or pre-dev gates, hands off to ring:executing-plans or ring:running-dev-cycle. Skip for single-file changes or spikes.
Design and audit product risk registers, decision governance, mitigation ownership, severity/likelihood scoring, control evidence, review cadence, triggers, assumptions, dependencies, AI/safety risk, commercial risk, operational risk, privacy/security risk, and acceptance decisions. Use when a product team needs to track and reduce material risk instead of relying on scattered notes.
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
Strict discipline for runtime verification in PDCA workflows: the AI performs verification itself in an environment — real preferred over simulated, subject to determinism and safety — and never defaults to a human checklist. Attempt first, resolve a pluggable provider (project script/skill → shared capability skill), and hand off to a human only at a true hard boundary with a stated reason. Use at any workflow verify/check stage (bug fix or feature) to decide WHERE verification runs, WHO runs it, and WHETHER it is sufficient. Referenced by PDCA hosts via frontmatter dependencies. Triggers — 「环境验证」「真实环境验证」「真机验证」「真机测试」「模拟环境验证」「AI 验证」「验证分层」「验证充分性」 / runtime verification, environment verification, real vs simulated. When a check opens a UI, cite a saved non-empty screenshot; non-UI checks do not. Do NOT alias completion-evidence-discipline (evidence freshness) or runtime-evidence-debug (debug instrumentation).
Build and review Bevy game asset loading pipelines with typed asset catalogs, path validation, loading states, handle ownership, sprite sheets, audio, and runtime resource checks. Use when organizing Bevy assets, replacing hard-coded paths, adding loading screens, diagnosing missing handles, or packaging Rust game resources.
Design and review Bevy 2D collision broadphase systems with AABB bounds, spatial indexes, typed collision events, and benchmark-driven test beds. Use when replacing O(n^2) collision checks, adding spatial partitioning, diagnosing Bevy collision performance, or separating broadphase, narrowphase, and response systems in Rust games.
Design and review Bevy game state flow with plugins, AppState enums, OnEnter and OnExit setup, state-scoped cleanup, menus, pause screens, transitions, and run conditions. Use when adding reusable Bevy game state management, debugging duplicated entities after transitions, or separating menu, loading, playing, paused, and game-over logic.
Prepare Rust crates for publishing with Cargo metadata, versioning, README and license checks, package dry-runs, feature verification, docs.rs readiness, examples, changelog notes, and secret-safe release gates. Use before cargo publish, crate release PRs, or sharing a reusable Rust library.
Optimize Rust libraries with criterion benchmarks, feature-flag matrices, cargo bench workflows, dependency gating, regression baselines, and evidence-driven API performance tradeoffs. Use when adding or reviewing Rust library benchmarks, cargo features, optional dependencies, or performance claims before publishing.
Write and review Rust library documentation with rustdoc module docs, public API examples, doctests, examples directories, missing-docs gates, docs.rs readiness, and user-first crate narratives. Use when documenting a Rust crate, improving docs before publishing, or turning examples into tested rustdoc.
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.