Total 54,003 skills, Automation has 1594 skills
Showing 12 of 1594 skills
Automatic response rules, patterns, and scheduled messages
Slack 이모지 반응자를 Google Calendar 이벤트에 자동 초대. "슬랙 캘린더", "이모지 반응 초대", "slack to gcal", "/slack-gcal" 요청에 사용.
Use when setting up or optimizing developer workflows in a monorepo, managing mise tasks, git hooks, CI/CD pipelines, database migrations, or release automation. Invoke for development environment setup, build automation, testing workflows, and release coordination.
Self-evolving Polymarket trading bot. Design strategy with user, run paper trading, auto-improve until edge target met, then ask to switch to live.
Generates the Somnio HandShake Step 3 - Acknowledgement PDF document from raw evaluation notes. Use this skill whenever an Engineering Manager (EM) wants to create, generate, or produce one or more HandShake Acknowledgement documents, career review PDFs, seniority evaluation documents, or anything related to the Somnio bi-annual performance review process. Trigger even if the user says things like: generar el documento del handshake, armar el PDF de la evaluacion, crear el acknowledgement para un dev, generar el informe del career path, procesar estas fichas, or similar. The skill handles both single and batch (multiple devs) generation: it reads all attached ficha files, pre-fills what it can infer, confirms all data with the EM in a single table, then generates one PDF per dev.
Set up and run an autonomous experiment loop for any optimization target. Use when asked to start autoresearch or run experiments.
Connect sales tools with webhooks, Zapier/Make, native integrations, and custom API pipelines — CRM sync, event triggers, data mapping, and error handling. Use when connecting Mailshake/Apollo/Salesloft to CRM, setting up webhook pipelines, building Zapier/Make automations for sales workflows, syncing data between tools, or troubleshooting integration issues. Do NOT use for Qwilr-specific automations (use /sales-qwilr-automation), general CRM platform config (use /sales-apollo or /sales-salesloft), or marketing automation flows (use /email-sequence).
Execute a single task from a Jira task plan using a structured pipeline of specialist subagents: planning, testing, refactoring, implementation, documentation, code-quality review, architecture review, security audit, and requirements verification. The user must specify which task number to execute. Use when the user says "execute task 3", "work on task 2", "implement task 1", "start task 5 for PROJECT-1234", or "run task N". Also triggered by the orchestrating-jira-workflow skill as Phase 5 of the end-to-end pipeline (called once per task). Requires that the task plan exists at docs/<TICKET_KEY>-tasks.md. Executes ONLY the specified task — never continues to the next one without explicit user approval.
Use Tabbit with agent-browser by reading Tabbit's live DevToolsActivePort file, deriving the browser wsEndpoint, and routing browser actions through agent-browser --cdp.
White Swan integration. Manage data, records, and automate workflows. Use when the user wants to interact with White Swan data.
TriNet integration. Manage data, records, and automate workflows. Use when the user wants to interact with TriNet data.
Design and implement end-to-end client onboarding workflows from prospect intake through funded account, covering KYC verification, document collection, e-signature, and custodian submission. Use when the user asks about building a digital onboarding flow, integrating identity verification or CIP checks, reducing NIGO rejection rates, opening complex account types like trusts or entities, connecting to custodian APIs, designing suitability questionnaires, or comparing advisor-assisted vs self-service models. Also trigger when users mention 'new account opening', 'onboarding bottleneck', 'KYC integration', 'beneficial ownership', 'OFAC screening', 'account funding', or 'onboarding automation'.