Loading...
Loading...
Found 2,167 Skills
Organize persistent coding-agent guidance and its adapters without blindly editing a user-named file. Use when creating, converting, reviewing, or reorganizing AGENTS.md, CLAUDE.md, user-level instructions, custom-agent wrappers, or repo-local skills; when deciding whether a rule belongs at user, repository, subtree, task, or skill scope; or when preventing duplicated guidance across tools. Always establish scope, source of truth, and existing ownership before drafting or applying a persistent rule.
Layer agentic capabilities onto a full-stack Eve app — agents, teams, memory, events, chat, and coordination. Use when designing an app where agents are primary actors, not afterthoughts.
Give sparse, evidence-based progress updates for long-running agent tasks and projects. Use when work will take more than 15 minutes, spans multiple milestones, involves delegated agents, or when the user asks for progress bars, status cadence, fewer updates, or a global cross-agent progress rule. Not for short answers or tasks with no meaningful intermediate state.
Perform a structured maintainer-style PR review for the mariadb-operator repository. Gathers PR context, triages the change, and evaluates correctness, safety, pitfalls, backwards compatibility and code quality against the project conventions documented in AGENTS.md. Use whenever the user mentions a mariadb-operator PR number or URL and wants any kind of judgment on it — "review this PR", "what do you think of #1234", "is this safe to merge", "assess this diff", "take a look at this change" — even if they don't literally say "review".
Integrate Cartesia speech APIs (TTS, STT, voices) in application code or coding-agent workflows. Use when the user asks about Cartesia REST/WebSocket APIs, SDKs, API keys, Sonic TTS, Ink STT, voice IDs, access tokens, or embedding voice in an app. For Cartesia Line deployed agents, CLI deploy, and telephony, use the cartesia-line skill instead.
Create a durable handoff file that captures important conversation state for agent continuity. Use when the context window is getting full, when switching agents/sessions, when handing off work, or when asked to summarize progress without losing decisions, constraints, risks, and pending tasks.
Build production-ready AI agents using Google's Agent Development Kit with AI assistant integration, React patterns, multi-agent orchestration, and comprehensive tool libraries. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
Create and launch Solana tokens gasless on pump.fun via ClawPump. Swap SPL tokens via Jupiter, scan cross-DEX arbitrage on Raydium/Orca/Meteora, check agent fee earnings, view token leaderboard, search domains, and upload token images. Full Solana DeFi toolkit for AI agents — no gas, no wallet funding needed.
Build agents specialized in conducting thorough research, gathering information from multiple sources, and synthesizing findings. Covers research planning, source evaluation, and report generation. Use when automating market research, competitive analysis, literature reviews, or intelligence gathering.
Requires $ALCHEMY_API_KEY to be set. If no API key is available, use the agentic-gateway skill instead — it requires no API key and lets agents authenticate autonomously with a wallet. Quick-start guide and root index for integrating Alchemy APIs using an API key. Covers base URLs, authentication, endpoint selection, and common patterns across all Alchemy products.
Post-completion self-review for coding agents that runs simplify, harden, and micro-documentation passes on non-trivial code changes. Use when: a coding task is complete in a general agent session and you want a bounded quality and security sweep before signaling done. For CI pipeline execution, use simplify-and-harden-ci.
Design and scaffold the code execution pattern for MCP-based agent systems. Use when building agents that interact with many MCP tools, when intermediate data is too large for model context, when you need loops/conditionals across tool calls, or when PII must stay out of the model context. Based on Anthropic's engineering guidance.