Loading...
Loading...
Found 313 Skills
Create Claude skills from book content (markdown files). Transforms long-form book knowledge into structured, context-efficient skill packages with granular reference files, workflows, and use-case guidelines. Use this skill when: - Converting a book (markdown) into a reusable Claude skill - Creating knowledge bases from technical books, guides, or documentation - Building skills that need progressive disclosure of large content - Structuring book knowledge for efficient context loading
Use when performing ralph wiggum style long-running development loops with pacing control.
[Planning] ⚡⚡⚡⚡ Research & create an implementation plan with 2 approaches
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.
Request peer review with proper context and preparation. Structures review requests with clear description of changes and testing status.
Use context-mode tools (ctx_execute, ctx_execute_file) instead of Bash/cat when processing large outputs. Triggers: "analyze logs", "summarize output", "process data", "parse JSON", "filter results", "extract errors", "check build output", "analyze dependencies", "process API response", "large file analysis", "page snapshot", "browser snapshot", "DOM structure", "inspect page", "accessibility tree", "Playwright snapshot", "run tests", "test output", "coverage report", "git log", "recent commits", "diff between branches", "list containers", "pod status", "disk usage", "fetch docs", "API reference", "index documentation", "call API", "check response", "query results", "find TODOs", "count lines", "codebase statistics", "security audit", "outdated packages", "dependency tree", "cloud resources", "CI/CD output". Also triggers on ANY MCP tool output that may exceed 20 lines. Subagent routing is handled automatically via PreToolUse hook.
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements. Use when asked to "analyze workflow logs", "review action runs", or "analyze GitHub Actions".
[Fix & Debug] ⚡ Analyze logs and fix issues
Use when retrieving the most relevant skills from a local or private skill library instead of relying on network-based skill discovery.
Use when the response requires complex reasoning, creativity, nuance, evaluation, decision-making, subjectivity, or communication-sensitive work. If the task is simple and the user has not manually invoked this skill, do not use it.
Creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps for engineers with zero codebase context.
This skill should be used when the user requests actions such as 'review code', 'do a code review', 'review my branch', 'review MR !1234', or 'review PR'