Loading...
Loading...
Found 5,651 Skills
Use this skill when the user wants to analyze Claude token usage, understand Claude API spending, check cache hit rates, review Claude Code workflow patterns (skills, agents, hooks), or get cost optimization recommendations.
Exabeam integration. Manage data, records, and automate workflows. Use when the user wants to interact with Exabeam data.
Slope integration. Manage data, records, and automate workflows. Use when the user wants to interact with Slope data.
Kandy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kandy data.
Create and manage AI-powered GitHub workflows that autonomously maintain repositories, review code, update docs, and handle developer tasks.
Router skill for LLMQuant hedge-fund and PM strategy workflows. Use when the user needs equity long/short, long-biased, event-driven, macro, quant, or multi-strategy playbooks.
Router skill for LLMQuant portfolio workflows. Use when the user needs company profiles, thesis tracking, theme research, watchlist monitoring, or alert management.
Budget Insight integration. Manage data, records, and automate workflows. Use when the user wants to interact with Budget Insight data.
Install Zero and load version-matched workflows with zero skills.
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Add automatic stream recovery to AI chat with WorkflowChatTransport, start/resume API endpoints, and the useResumableChat hook.
Intelligent agent for interpreting vague ERPNext development requests and producing concrete technical specifications. Use when receiving unclear requirements like 'make invoice auto-calculate', 'add approval workflow', 'sync with external system'. Triggers: user gives vague requirement, need to clarify scope, translate business need to technical spec, determine which ERPNext mechanisms to use, create implementation plan.