Skills
100,696 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Meta-gateway for experience feedback. Collects from three sources (session reviews/article scans/manual input) → distills and anonymizes → categorizes → handles in three ways (publish an issue/store locally/do not store). Trigger terms: feedback experience, save experience, submit experience, experience review, capture lessons, lessons learned
Functional language runtime reverse engineering (Haskell/OCaml): closure/heap object models, calling conventions, and a dataflow-first strategy. Triggers: Haskell reverse engineering, OCaml reverse engineering, GHC RTS, thunk, STG, OCaml runtime, closure, functional language artifacts.
Physical-layer hardware reverse engineering: decapsulation, die analysis, probes and FIB, PCB circuit analysis, and hardware Trojan detection. Trigger terms: chip reverse engineering, decapsulation, decapping, PCB, hardware Trojan, circuit analysis, die, FIB, side channel, SPA, DPA, fault injection, clock glitch, voltage glitch
Java Card / SIM applet reverse engineering: parse CAP file components (12 components per the specification), reconstruct CAP bytecode (Java subset), analyze AID and installation parameters, and trace process(APDU) dispatch. Trigger terms: Java Card, javacard, CAP file, SIM card, USIM, applet, AID, bank card, JCVM
Malware analysis gateway. Orchestration: default sandbox → initial static analysis → behavior analysis → C2/protocol → IOC/report. Sub-skills: [[re-sandbox]] [[re-behavior]] [[re-ioc]] [[re-ransomware]] [[re-loader]] [[re-fileless]], [[re-doc-malware]], [[re-sample-acquire]]. Trigger terms: malware, sample behavior, callback, C2, IOC, malware analysis
RISC-V architecture reverse engineering: RV32/RV64, compressed instructions (RVC), gp-relative addressing, ABI and ecall system call conventions, and toolchain fingerprinting. Triggers: RISC-V, riscv, RV32, RV64, RVC, compressed instructions, ecall, ESP32-C3, GD32V.
Design and restyle React Native and Expo UI with a real visual direction: themes and color tokens, palettes from brand colors, screen layouts, and design audits of existing screens. Measures WCAG contrast with a bundled script and applies the platform rules that web habits get wrong (shadows, gradients, edge-to-edge, safe areas, blur). Use when the task is about how a screen or component looks or is laid out: a new theme, a new screen, a UI that feels off, a web or Figma design to translate. Not for data fetching, state management, navigation wiring, or non-visual bugs.
Use when building video automation workflows — creating AI-powered short clips from long-form videos, adding captions, reframing for different aspect ratios, dubbing audio into multiple languages, generating transcriptions, or publishing clips to social media platforms (YouTube, Instagram, TikTok, LinkedIn, X).
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization.
Stress-test a research idea before major investment. Use to expose hidden assumptions, weak novelty, confounders, and the cheapest decisive experiment. Use before starting a project, writing a proposal, scaling experiments, or committing major compute/resources.
Open or update a pull request with a scannable description (compact trees and diffs) plus a screenshot, recording, or command-output image. Use when opening a PR, creating a pull request, adding screenshots or a video to a PR, filing a PR with a demo, writing a visual PR description, attaching evidence to a pull request, or /reveal.
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
Guide wanderers to the right animal for their journey. Perch, tilt your head, chatter about the forest, present the options, and warble the recommendation. Use when helping users choose which skill to use, discovering capabilities, or navigating the ecosystem.
Use when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test isolation, external HTTP mocks, or CI-ready cargo verification for Actix, Axum, Warp, Rocket, or similar Rust web frameworks.
Use when adding, changing, testing, or reviewing security-sensitive Rust web service behavior, especially login flows, password hashing, credential checks, session cookies, flash messages, admin route protection, auth middleware, user enumeration defenses, or moving CPU-heavy password work off async executors.
Optimizes BUYER-side checkout pages, upsells, order bumps, payment collection, and cart abandonment recovery — increase average order value and reduce checkout friction. Use when checkout conversion rate is too low, cart abandonment is high, average order value isn't growing, not sure which checkout platform to pick, payment plans not converting, or buyers dropping off at the payment step. Do NOT use for full funnel strategy (use /sales-funnel), email follow-up after purchase (use /sales-email-marketing), affiliate tracking on sales (use /sales-affiliate-program), or supply-side / seller-side marketplace payouts to 1099 workers, sellers, drivers, or creators (use /sales-marketplace-payouts). For Groove-specific help, use /sales-groove.
Lemlist platform help — multichannel sequences, lead database, enrichment, Lemwarm, unified inbox, AI personalization, LinkedIn automation, calls, WhatsApp, API, integrations. Use when Lemlist sequences not sending, emails landing in spam despite Lemwarm, leads not importing correctly, integrations not syncing, People Database search returning poor matches, or Lemlist API calls failing. Do NOT use for building prospect lists (use /sales-prospect-list), designing cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), or enriching contacts outside Lemlist (use /sales-enrich).
Salesloft platform help — config, Rhythm, Conversations, Deals, Forecast, Analytics, Drift, integrations, admin, API. Use when Salesloft settings aren't configured right, Rhythm signals feel noisy or unhelpful, Analytics dashboards don't show what you need, Drift chatbots aren't converting, or Salesloft integrations are broken. Do NOT use for building cadences (use /sales-cadence), reviewing calls (use /sales-call-review), inspecting deals (use /sales-deal-inspect), or forecasting (use /sales-forecast).
This skill should be used when the user asks to "perform vulnerability scanning", "scan networks for open ports", "assess web application security", "scan wireless networks", "detect malware", "check cloud security", or "evaluate system compliance". It provides comprehensive guidance on security scanning tools and methodologies.
AI-driven presentation generation system using Touying/Typst. Converts source documents (PDF/DOCX/URL/Markdown) into high-quality Typst slides through either a multi-role Full Mode workflow or direct existing-theme Quick Mode authoring, and exports to PDF/PNG/PPTX. Use this skill whenever the user wants to create slides, make a presentation, build a deck, convert a PDF/document to slides, turn notes into a presentation, or anything involving Typst/Touying slide generation. Trigger phrases include: "create slides", "make presentation", "generate slides", "convert to slides", "turn into a deck", "keynote", "PPT", "slide deck", "生成PPT", "做幻灯片", "制作演示文稿", "用Typst做演示", "做个汇报", "转成幻灯片", or mentions "seaslides-typst-slides-skill". Even if the user does not explicitly say "slides" or "presentation", use this skill when the intent is clearly to create visual presentation materials from source content.
Every shot carries its own timecode and shows one visible change on a body. The dread comes from the chain — a look, veins, a bite, the next person — and the ending seals a door without settling anything. Use when the user wants a Seedance 2.5 / 2.0 video prompt for this kind of clip (Horror and suspense; 中文触发词: 恐怖悬疑短片, 恐怖, 悬疑, 惊悚), or asks how published cases of this type were prompted. Read references/cases.md before drafting.
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge is outdated or incorrect, (6) A better approach is discovered for a recurring task. Also review learnings before major tasks.
Act as a Senior Backend Developer expert to design system architectures, build production-grade APIs (REST, GraphQL, gRPC), write optimized database schemas and queries, perform rigorous code reviews, and enforce engineering best practices. Supports Node.js/TypeScript, Python, Java/Spring Boot, Go, and Rust. Produces production-ready code, architecture docs with Mermaid diagrams, migration files, and actionable code-review feedback. Use whenever a user needs backend engineering guidance, code generation, refactoring, or architectural decisions.
Serenity's (@aleabitoreddit) thinking framework and way of expressing. Based on 6-dimensional deep research (1700+ tweets, Substack long interviews, third-party analyses, critics' views), distills 5 core mental models, 8 decision heuristics, and a complete expression DNA. Purpose: as a thinking advisor for AI/semiconductor supply chain investing, analyze investment targets, review decisions, and provide feedback from Serenity's perspective. Use when the user mentions "from Serenity's perspective", "what would aleabitoreddit think", "Serenity mode", "Serenity perspective", or "from aleabitoreddit's angle". It should also trigger even if the user just says "help me think from Serenity's angle", "what would Serenity do", or "switch to Serenity".
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.