Loading...
Loading...
Found 5,653 Skills
Privy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Privy data.
Ably integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ably data.
DroneDeploy integration. Manage data, records, and automate workflows. Use when the user wants to interact with DroneDeploy data.
AWS Well-Architected integration. Manage data, records, and automate workflows. Use when the user wants to interact with AWS Well-Architected data.
PayUmoney integration. Manage data, records, and automate workflows. Use when the user wants to interact with PayUmoney data.
Use when working with n8n workflows in any capacity. The always-on protocol for the n8n-skills plugin, loaded by the SessionStart hook every session. Routes to the right skill, summarizes every n8n MCP tool (closing the deferred-description gap), and lists the cross-cutting rules.
Billsby integration. Manage data, records, and automate workflows. Use when the user wants to interact with Billsby data.
Tableau integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tableau data.
Densify integration. Manage data, records, and automate workflows. Use when the user wants to interact with Densify data.
Webexpenses integration. Manage data, records, and automate workflows. Use when the user wants to interact with Webexpenses data.
End-to-end conference talk pipeline: paper → slide outline → Beamer + PPTX → per-page polish → assurance checks (claim / citation / anonymity) → final export and report. Default-good for academic conference talks (NeurIPS / ICML / ICLR / VALSE / 投稿 talks). Trigger phrases: "做 talk", "做 PPT 全流程", "talk pipeline", "end-to-end slides", "做演讲", "conference talk full workflow". Use when the user wants the complete talk artifact, not just a slide deck.
Patterns for building applications that integrate the Krea API. Auth, polling discipline, error handling, validation, frontend integration (SvelteKit/React/Vue), and the 'prototype in chat, productize in app' workflow. Use when the user is writing code that calls the Krea API directly — building a generator UI, a content pipeline, a creative tool — not when they just want to generate one image. For interactive generation use the sibling krea-ai skill instead.