Loading...
Loading...
Found 6,710 Skills
Instruments an existing Android project (Kotlin or Java) with the Dynatrace Mobile Agent for basic monitoring. Covers zero-to-first-event setup only: Gradle plugin, agent config, and user privacy opt-in. Do not use for advanced Dynatrace configuration beyond initial instrumentation.
Scaffolds new sub-agent definitions. Automates the entire process from category selection, file creation, model/tools least privilege configuration, to quality checks. Can be used with commands like "Make an Agent", "Add sub-agent", "create-agent".
Use when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits. Covers payment setup, policy, session budgets, and troubleshooting. Triggers on: "my agent hit a 402 while calling an API", "a tool call returned 402 Payment Required", "my agent needs to pay for x402-protected content", "let the agent pay for content, capped at $5 per session", "set a spend limit for the agent", "ProcessPayment failed", or "why did my agent refuse to pay". Not for BUILDING payment capability for end users, including wallets and framework middleware; use agents-build and references/payments.md. For non-paid APIs via Gateway use agents-connect. For inbound auth use agents-harden. For project scaffolding use agents-get-started.
Conventions for writing sharp, concise prose and Markdown, for human readers and AI agents. Read before writing or editing documentation, READMEs, instructions, agent skills, or any prose text.
Build AI agents with structured access to Sanity content via Sanity Context. Use when setting up a Sanity-powered chatbot, connecting an AI assistant to Sanity content, or adding client-side tools to an agent. Covers Studio setup, agent implementation, and advanced patterns. Always use this skill when users mention building a chatbot with Sanity, creating an AI assistant for their content, setting up the Sanity Context MCP server, integrating Sanity with Claude/GPT/any LLM, making content searchable by AI, implementing semantic search over Sanity data, or connecting their CMS to an AI agent.
Use when an agent session ran outside the repo whose commits should record it — e.g. launched from a higher-level folder, a non-Entire repo, or one repo but editing another — to attach the session to each affected Entire-enabled repo's HEAD commit.
Measure whether a repository's AI instructions still earn their place, by running the same real task many times with the layer intact and with it stripped, then grading every rule against what actually changed. Runs both arms itself in throwaway git worktrees and never touches the working tree. Agent-agnostic across CLAUDE.md, AGENTS.md, .claude/, .agents/, .cursor/rules, .clinerules, .windsurfrules and copilot-instructions. Use when the user wants to prune, audit, clean up, shrink or "delete" their CLAUDE.md, AGENTS.md, cursor rules, agent instructions or AI layer; when they ask whether their rules are still needed, whether their context is bloated, or what to cut; or when they mention ablating, ablation, or testing their agent without its instructions.
Active, Socratic teacher for the LangChain Academy Deep Agents course — drives the student through the curriculum with a calibrated interaction density, explain-then-check dialogue at load-bearing moments, and misconception-targeted questioning
Design lightweight eval harnesses for coding or workflow agents, especially when testing whether agents follow steering docs, use tools correctly, preserve user edits, recover from failures, and produce the intended artifact.
The session loop that makes agentmemory pay off, recall before starting work, save at decision points, learn from corrections. Use when starting a nontrivial task, after settling a decision or debugging a gotcha, or whenever deciding if something belongs in memory.
Guides the agent through connecting an MCP client to the hosted Capawesome MCP server, which exposes always-current Capawesome documentation search and the Capawesome Cloud management API. Covers setup for Claude Code, Claude Desktop, Cursor, and VS Code, API token creation, toolset selection, read-only mode, secret handling, verification, and troubleshooting. Do not use for installing Capacitor plugins, migrating apps or plugins to a newer version, running Capawesome CLI commands, or MCP servers other than Capawesome.
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.