Loading...
Loading...
Found 358 Skills
Expert n8n workflow automation consultant for B2B sales and GTM teams. Use when the user asks about n8n workflows, n8n nodes, n8n triggers, n8n webhooks, n8n credentials, n8n self-hosting, n8n Docker setup, n8n queue mode, n8n error handling, n8n sub-workflows, Clay + n8n integration, n8n CRM automation, n8n pricing, n8n vs Zapier vs Make, or building automations with n8n. Also triggers on "n8n workflow", "n8n automation", "n8n webhook", "n8n node", "n8n self-host", "n8n Docker", "n8n queue", "n8n Clay", "n8n HubSpot", "n8n Salesforce", "n8n vs Zapier", "n8n pricing", "workflow automation". Do NOT use for Clay-only questions without n8n context or general automation strategy without n8n.
Python development best practices including PEP 8 style guidelines, type hints, docstring conventions, and common patterns. Use when writing or modifying Python code.
Senior Python developer. Use when writing, reviewing, or refactoring Python code. Enforces idiomatic Python, type hints, and modern patterns.
Senior Node.js developer. Use when building, reviewing, or refactoring Node.js applications. Enforces modern Node.js 22+ patterns, native APIs, performance, and production-ready practices.
Master third-party API integration in ANY language with best practices and patterns
Express.js REST API patterns and best practices. Trigger: When building Express.js REST APIs.
JavaScript language fundamentals. Covers ES6+, modules, async patterns. Use when working with plain JS projects without TypeScript. USE WHEN: user mentions "javascript", "ES6", "async/await", "promises", "modules", asks about "destructuring", "spread operator", "arrow functions", "ESM vs CommonJS" DO NOT USE FOR: TypeScript projects - use `typescript` skill instead DO NOT USE FOR: Node.js runtime - use `nodejs` skill instead DO NOT USE FOR: Browser APIs - use framework-specific skills
Code quality standards. Defines complexity management, modular design, code smell detection. Applied automatically when writing or reviewing code.
Unix-composable CLI design patterns. Use when building CLI tools, designing command trees, implementing output layers, or testing CLI behavior. Covers stream separation (stdout/stderr), format flags (--json/--plain), exit codes, TTY detection, composability, and error design. Language-agnostic principles; TypeScript implementation patterns in resources/. For API design (REST, HTTP), see api-design.
Shared Epismo operating model: CLI/MCP surface conventions, workspace and project scope, share URL resolution, selective fetch and pack reuse patterns, pack aliases, credits/payment handling, and common auth or permission errors. Load this alongside any Epismo skill, or trigger on Epismo usage questions, alias/credit issues, share URLs, workspace scope, or setup/auth problems blocking another Epismo task.