Loading...
Loading...
Found 6,152 Skills
A/B Tasty integration. Manage data, records, and automate workflows. Use when the user wants to interact with A/B Tasty data.
Vext integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vext data.
Sorry integration. Manage data, records, and automate workflows. Use when the user wants to interact with Sorry data.
Scrapin.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Scrapin.io data.
SAP Ariba integration. Manage data, records, and automate workflows. Use when the user wants to interact with SAP Ariba data.
Worldline integration. Manage data, records, and automate workflows. Use when the user wants to interact with Worldline data.
Command-line interface for n8n workflow automation platform. Manages workflows, executions, credentials, variables, and tags. Based on n8n Public API v1.1.1 (n8n >= 1.0.0).
Jumio integration. Manage data, records, and automate workflows. Use when the user wants to interact with Jumio data.
SerwerSMS.pl integration. Manage data, records, and automate workflows. Use when the user wants to interact with SerwerSMS.pl data.
Seam integration. Manage data, records, and automate workflows. Use when the user wants to interact with Seam data.
Shared kernel design workflow across all supported languages and DSLs. Provides language selection table, naming conventions, versioning rules, KernelPlan structure, composition patterns, clone workflow, implementation workflow, devlog template, and designer output contract. Use when: (1) choosing which language-specific kernel design skill to load, (2) the intended implementation language is not fixed yet, (3) you need naming or versioning guidance before selecting a DSL, (4) you are implementing any kernel regardless of DSL, (5) you are updating docs that refer to kernel design skills.
Phase 2 of the feature workflow —— Write code according to the implementation sequence in {slug}-design.md, and submit a completion report in a unified format for user review after finishing. Prerequisites: {slug}-design.md has been approved (standard design includes test design, or fastforward design includes acceptance criteria), and {slug}-checklist.yaml exists in the same directory. Trigger scenarios: User says "The plan is confirmed, start implementation", "Write code according to the plan", "Start working". If you encounter situations not covered by the plan during implementation (new concepts, out-of-scope files, need for patch branches), proactively stop and go back to discuss the plan instead of pushing forward blindly.