Loading...
Loading...
Found 2,897 Skills
Retrieve the latest Runway API reference from docs.dev.runwayml.com and use it as the authoritative source before any integration work
Set up and maintain a persistent, LLM-managed knowledge base for a digital health project — turning clinical observations, papers, interviews, and planning docs into a compounding, interlinked wiki.
Rewrite AI-generated developer text to sound human — fix inflated language, filler, tautological docs, and robotic tone. Use after review-ai-writing identifies issues.
Generates professional Statements of Work from a project brief. Use when a user needs to create an SOW, scope a project, define deliverables and milestones, or produce a consulting engagement document.
Document a recently solved problem to compound your team's knowledge
Create domain-specific quality checklists validating spec completeness and clarity
Documents backlog refinement session outcomes including stories refined, estimates, questions raised, and decisions made. Use during or after refinement to capture the results and share with absent team members.
Draft structured handover notes for transitioning a PostHog account from one TAM or CSM to another. Use this skill when a TAM needs to hand over an account, prepare a transition briefing, write handover notes, create an account summary for a new owner, or any request involving account transitions between TAMs or CSMs. Triggers on "hand over this account", "transition account to", "draft handover notes", "account briefing for new TAM", "prepare account transition", or when a TAM names an account and says they're leaving or reassigning it.
Write structured experiment report documents from ML/research experiment notes, configs, logs, metrics, tables, and figures. Use this skill whenever the user asks to write an experiment report, research update, mentor update, weekly experiment summary, result analysis document, or presentation-ready experiment writeup, especially when the output should explain motivation, setup, algorithms, metrics, results, figures, interpretation, conclusions, limitations, and next steps.
Standardize the article editing process to ensure clear modification scope, trackable progress, and documented changes. Use this skill when the user says "edit article", "revise article", "adjust content", or "modify this piece".
Collaborative design exploration for new features and architecture decisions. Triggers: 'brainstorm', 'ideate', 'explore options', or /ideate. Presents 2-3 approaches with trade-offs, documents chosen approach. Do NOT use for implementation planning or code review. Requires no existing design document — use /plan if one exists.
Generate a SYSTEM_OVERVIEW.md that orients a senior engineer new to an unfamiliar codebase, with a Mermaid architecture diagram, a sequence diagram for data flow, and a legacy-pattern assessment. Use when user says 'give me a system overview', 'onboard me on this repo', 'walk me into this legacy codebase', 'document the high-level architecture', or 'create a SYSTEM_OVERVIEW.md'. Do NOT use for code walkthroughs (use explain), persistent architecture chapters (use arc42), or ADRs (use document-decision).