Prerender Automation
Automate Prerender tasks via Rube MCP (Composio). Always search tools first for current schemas.
Choose a skill to see what it does, what you need, and how to start.
Automate Prerender tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Prisma tasks via Rube MCP (Composio). Always search tools first for current schemas.
Use this skill to work the open PR queue end-to-end: assess merge readiness, run security gates, selectively request Claude Opus review on substantial PRs, merge eligible PRs, and hand off release PRs to /release.
Automate Procfu tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Productlane tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Proofly tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Proxiedmail tasks via Rube MCP (Composio). Always search tools first for current schemas.
Diagnose an already failed LLM interaction from the original request, visible context, actual reply or artifact, and expected outcome; propose the smallest communication repair and a controlled rerun. Use when a reply ignored constraints, answered the previous task, caused repeated rework, or remained impossible to accept. Do not use for an untried vague request, ordinary copy editing, platform troubleshooting without interaction evidence, or general prompt-template generation.
Turn an untried, low-risk request for LLM help into one short, copy-ready first-turn dialogue brief with a stated outcome, audience, supplied inputs, constraints, output shape, acceptance check, and stop boundary. Use when the user has a roughly defined communication goal but needs a clear first message; do not use for coaching, research, a task with files or external effects, or repairing an already failed reply.
Automate Pushbullet tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Pushover tasks via Rube MCP (Composio). Always search tools first for current schemas.
Obfuscate / protect Python source before shipping it, and verify the obfuscated output still runs. Use when the user wants to protect, obfuscate, harden, or "make it hard to read / reverse-engineer" a Python package, CLI, or service before publishing to PyPI, sending a build to a client, or shipping an evaluation copy — especially when they want confidence the transform didn't break the code. Powered by pyobfus (an AST-based, framework-aware, AI-debuggable obfuscator). Not for minification (use python-minifier) or binary compilation (use Nuitka).
Review a Python project for source-protection readiness without changing anything: what would break under obfuscation, which framework preset fits, which files the current config already excludes, and exactly which artifacts a build would emit. Use when the user asks "is this safe to obfuscate?", "what would protecting this break?", "review before we ship", or wants a pre-merge / CI check. Read-only by design — it never obfuscates, never writes deliverables, and never runs project commands. To actually produce a protected build, use the pyobfus-protect skill instead.
Automate Quaderno tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Qualaroo tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Radar tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Rafflys tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Ragic tasks via Rube MCP (Composio). Always search tools first for current schemas.
Ruby on Rails development following Rails Way conventions, RSpec testing, and security best practices. Use when working on Rails projects requiring MVC architecture, Active Record, or API development. Do NOT use for other programming languages or frameworks.
Automate Raisely tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Re Amaze tasks via Rube MCP (Composio). Always search tools first for current schemas.
Expo and React Native mobile development for iOS and Android. Use when building cross-platform mobile apps, native modules, or mobile-specific UI. Covers React Navigation, platform-specific code, and mobile performance. Do NOT use for React web development.
Use before building, changing, or reviewing any client screen, or the design itself — it points at the state inventory a screen is built from and at the artboard files behind it.
Automate Recallai tasks via Rube MCP (Composio). Always search tools first for current schemas.