Loading...
Loading...
Found 28 Skills
Design, build, run, and test Restate durable services, virtual objects, workflows, and AI agents across TypeScript, Python, Java, and Go. This skill should be used when the user mentions "restate", "durable execution", "virtual object", "restate service", "restate workflow", or "durable agent" or wants to build resilient backend services, AI agents, or workflows with automatic failure recovery. Also use when converting existing applications or migrating from workflow orchestrators to Restate. Use proactively when a project contains restate dependencies in package.json, requirements.txt, pyproject.toml, pom.xml, build.gradle, or go.mod.
This skill should be used when working with Restate durable execution framework, building workflows, virtual objects, or services that need automatic retries, state management, and fault tolerance. Use when the user mentions "restate", "durable execution", "durable workflows", needs to build resilient distributed systems, or when they invoke /restate.
restate to say the last message again in plain words, catch the user up since their last message, and summarize any decision they need to make.
Review amendments to SEC filings using Octagon MCP. Use when tracking material changes, corrections, restatements, and updates to previously filed documents including 10-K/A, 10-Q/A, 8-K/A, S-1/A, and Form 144/A filings.
Implement, review, or improve SwiftUI gesture handling. Use when adding tap, long press, drag, magnify, or rotate gestures, composing gestures with simultaneously/sequenced/exclusively, managing transient state with @GestureState, resolving parent/child gesture conflicts with highPriorityGesture or simultaneousGesture, building custom Gesture protocol conformances, or migrating from deprecated MagnificationGesture/RotationGesture to MagnifyGesture/RotateGesture.
Turns raw sales call notes into a structured recap email with agreed next steps - every action item carrying an owner, a date, and a deliverable - plus mutual close plan (mutual action plan) items when the deal warrants one. Restates the buyer's pain in their own words and never invents a commitment the notes don't contain. Covers complex B2B committee deals and transactional or B2C motions. Use whenever the user mentions a recap email, follow-up after a sales call, next steps email, post-call summary, or a mutual action plan, even without the word recap. Do NOT use for judging how the call went (mbfinotti/sales-skills@sales-call-review).
Clearly restate a human's request so they can confirm alignment before work begins. Use when the human explicitly invokes /readback or $readback after a long, dictated, unclear, or complex prompt; never invoke automatically.
Trim and freshen technical documents, READMEs, design notes, PR descriptions, internal messages, and source-code comments or docstrings. Uses independent fresh-reader reviews to expose author-context bias, then deletes repetition, defensive caveats, filler, decorative structure, and code restatements while preserving facts, decisions, actions, constraints, and necessary rationale. Use when text is overexplained, repetitive, hard to scan, written while thinking, or when comments restate code or have drifted out of sync with it.
Flag comments that merely restate the code instead of explaining why, and remove only those the user approves. Use when asked to remove dumb, redundant, or obvious comments, clean up comments, or invoke `/remove-dumb-comments [<number>|all]`.
Manual secondary interface for enforcing formal, textbook-grade written register across agent output. Use when the user explicitly invokes `/skill:be-serious` to load or restate the register policy.
Use when asked to compress, tighten, shorten, condense, or de-slop a design doc, PRD, RFC, architecture note, or similar prose "without losing information". Removes only provable redundancy — filler, hedging, LLM-slop, restated content — never a fact, number, decision, or caveat, and flags every judgment call for the author. Returns a compressed document, a categorized removal log, and a shareable scorecard.
Restate the previous answer — or the connected thread of answers — as something shorter and easier to act on: the bottom line first, only what matters, and anything to decide at the end.