Plisio Automation
Automate Plisio tasks via Rube MCP (Composio). Always search tools first for current schemas.
Browse verified SKILL.md agent skills and workflows. Open any skill to see when to use it, copy its install command, and run a starter prompt.
Automate Plisio tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Polygon tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Polygon IO tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Poptin tasks via Rube MCP (Composio). Always search tools first for current schemas.
PostgreSQL database architecture, optimization, and AWS Aurora expertise. Use when working on schema design, query optimization, migrations, or database operations. Do NOT use for application code or other databases.
Automate Postgrid tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate Precoro tasks via Rube MCP (Composio). Always search tools first for current schemas.
Manual only. Invoked by the owner to cut a MailFathom release — composes the changelog, raises the declared version, settles the milestones and the next release's tracking issue, and states the order the two pull requests and the tag have to land in.
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.
Install @pyric/live from npm or from a local Pyric checkout, start live mode in a project, verify which Firebase project it is on, and exercise it. Use to test live mode, where the app's own Firebase SDK talks to a real Firebase project and Pyric shows each Firestore, Realtime Database, Cloud Storage, AI Logic and Auth call, and a Node backend's firebase-admin calls, with production's answer. Don't use for ordinary Pyric sandbox work (use pyric) or to test Node host mode (use pyric-node-host).
Move a project that already runs Pyric's SharedWorker sandbox to Node host mode, carrying its sandbox data across and keeping a way back. Use when an existing Pyric app should share one durable sandbox across browsers, Studio, and tools. Don't use to start Pyric in a project for the first time (use pyric), or only to try Node host mode in a scratch project (use pyric-node-host).
Automate Quaderno tasks via Rube MCP (Composio). Always search tools first for current schemas.