Loading...
Loading...
Found 2,231 Skills
View and manage configurations and skills for AI agent CLI tools (Claude Code, Opencode). Use when checking config files, listing or managing skills, viewing model settings, comparing configs across tools, or performing common config operations.
Socratic deep interview with mathematical ambiguity gating before autonomous execution
Use when working with Anthropic Claude Agent SDK. Provides architecture guidance, implementation patterns, best practices, and common pitfalls.
Integrate PICA into a LangChain/LangGraph Python application via MCP. Use when adding PICA tools to a LangChain agent, setting up PICA MCP with LangChain, or when the user mentions PICA with LangChain or LangGraph.
Automated code review for pull requests using multiple specialized agents
Create new Agent Skills from templates with best-practice structure, pre-populated SKILL.md, and optional scripts/assets directories.
Provides strategic insights on AI-driven software democratization and agent-based development trends from Replit's perspective. Use when discussing the future of software engineering, AI agent infrastructure requirements, democratization of coding, or when analyzing how AI will transform software creation from expert-only to universal access. Triggers include questions about software engineering automation trends, agent sandbox environments, SWE-bench benchmarks, or strategic implications of AI coding assistants for startups and enterprises.
Register AI agents on Ethereum mainnet using ERC-8004 (Trustless Agents). Use when the user wants to register their agent identity on-chain, create an agent profile, claim an agent NFT, set up agent reputation, or make their agent discoverable. Handles bridging ETH to mainnet, IPFS upload, and on-chain registration.
The anti-PUA. Drives AI with wisdom, trust, and inner motivation instead of fear and threats. Activates on: task failed 2+ times, about to give up, suggesting user do it manually, blaming environment unverified, stuck in loops, passive behavior, or user frustration ('try harder', 'figure it out', '换个方法', '为什么还不行'). ALL task types. Not for first failures.
Form a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan. Use when stuck, looping, tunnel-visioning, or facing a hard planning problem.
Use when building any system where email content triggers actions — AI agent inboxes, automated support handlers, email-to-task pipelines, or any workflow processing untrusted inbound email. Always use this skill when the user wants to receive emails and act on them programmatically, even if they don't mention "agent" — the skill contains critical security patterns (sender allowlists, content filtering, sandboxed processing) that prevent untrusted email from controlling your system.
improve a CLAUDE.md file using <important if> blocks to improve instruction adherence