Loading...
Loading...
Found 890 Skills
Analyze, describe, read, or extract content from any screenshot, image, photo, picture, pic, snap, screen grab, or screen capture the user shares. Triggers when users ask about images ("what's in this", "what can you see", "what does this show", "what am I looking at", "tell me about this", "can you read this"), request review ("check this", "look at this", "review these", "analyze this"), request extraction ("extract text", "convert to markdown", "transcribe this", "parse this", "pull the data"), or describe attachments ("here's a screenshot", "I pasted this", "see attached"). Works with single or multiple images. Converts UI data into clean, structured markdown.
Read Discord for financial research using the discord-cli tool (read-only). Use this skill whenever the user wants to read Discord channels, search for messages in trading servers, view guild/channel info, monitor crypto or market discussion groups, or gather financial sentiment from Discord. Triggers include: "check my Discord", "search Discord for", "read Discord messages", "what's happening in the trading Discord", "show Discord channels", "list my servers", "Discord sentiment on BTC", "what are people saying in Discord about AAPL", "monitor crypto Discord", "export Discord messages", any mention of Discord in context of reading financial news, market research, or trading community discussions. This skill is READ-ONLY — it does NOT support sending messages, reacting, or any write operations.
One sentence — what this skill does and when Claude should use it.
Search Twitter for trending promotional posts related to coding/AI agent tools, generate reply drafts with the pikiclaw GitHub card, and push the results to Feishu Doc along with bot notifications. Does NOT auto-post to Twitter.
Deep contextual grep for codebases. Expert at finding patterns, architectures, implementations, and answering "Where is X?", "Which file has Y?", and "Find code that does Z" questions. Use when exploring unfamiliar codebases, finding specific implementations, understanding code organization, discovering patterns across multiple files, or locating functionality in a project. Supports three thoroughness levels quick, medium, very thorough.
Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn't work", "failing", "investigate bug".
Extends Claude Code's built-in skill dispatch with CoVe (Chain-of-Verification), dynamic skill discovery via skills.sh, and a toolkit knowledge base for MCP servers and configurations Claude doesn't natively know about. Use for any non-trivial task.
Must be followed when writing error handling code that includes try-catch. Ensure that the catch block has substantial processing logic, is not empty, does not only log information, and must handle or re-throw exceptions. Trigger keywords: try-catch specification, error handling best practices, exception handling review.
Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance. Use when the user asks for an SEO audit, technical SEO review, ranking diagnosis, on-page SEO review, meta tag audit, or SEO health check. This skill identifies issues and prioritizes actions but does not execute changes. For large-scale page creation, use programmatic-seo. For structured data, use schema-markup.
Test-Driven Development methodology and red-green-refactor workflow (formerly test-tdd). This skill should be used when practicing TDD, writing tests first, designing tests before implementation, or reviewing test-first approaches. Triggers on "write tests first", "test before code", "red green refactor", "test driven development". This skill does NOT cover Vitest framework specifics (use vitest skill) or API mocking with MSW (use msw skill).
Render DNA codes to Pencil .pen frames. Does ONE thing well. Input: DNA code + component type (hero, card, form, etc.) Output: .pen frame ID + screenshot Use when: design-exploration or other orchestrators need to render visual proposals using Pencil MCP backend.
Guide learning and deep understanding through proven methodologies (Socratic, Feynman, Problem-Based). Use when user says "help me understand", "teach me", "explain this", "learn about", "socratic", "feynman", "problem-based", "I don't understand", "confused about", "why does", or wants to truly grasp a concept.