code-explainer
Explains code in beginner-friendly terms. Use when user asks 'what does this do', 'how does this work', 'explain this code', or needs to understand generated code. Breaks down complex code into simple explanati...
Discover devops knowledge base skills, compare source repositories and read the instructions for each workflow.
Explains code in beginner-friendly terms. Use when user asks 'what does this do', 'how does this work', 'explain this code', or needs to understand generated code. Breaks down complex code into simple explanati...
Search conversation history for research context - papers discussed, citations analyzed, discoveries made, or questions explored.
Collaboratively create and refine new skills through iterative design - validate needs, design structure, draft content, test, and refine.
Defragment and clean research agent memory - consolidate paper info, organize research domains, remove redundancy from research tracking.
Set up effective automated discovery - from vague idea to working system in one streamlined conversation.
Initializes and updates screen specification documents. Use as a foundation skill for all screen documentation workflows.
Defines accessibility requirements for UI elements including semantic markup, ARIA attributes, focus management, and screen reader support. Updates the "アクセシビリティ" section in screen spec.md.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow help...
Classify support tickets by urgency and category. Use when analyzing tickets, determining priority, routing customer requests, or when user asks to classify, triage, or categorize support tickets.
TODO - Describe when to use this skill. Make it specific so Claude knows when to apply it (e.g., "Classify support tickets by urgency and category. Use when analyzing tickets, determining priority, or routing c...
Gather and create documentation files for libraries and frameworks using Exa's code search. Creates organized markdown docs in config/claude/docs/ for future reference.
Analyze coding sessions to detect corrections and preferences, then propose targeted improvements to Skills used in the session. Use this skill when the user asks to "learn from this session", "update skills",...
Guide for creating Claude Code subagents (custom agents) - specialized AI assistants with isolated context. Use when the user wants to create, add, or configure a subagent/custom agent for Claude Code.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge or workflows.
Recall and save insights using sage_recall_knowledge and sage_save_knowledge MCP tools. INVOKE WHEN: user asks "what do we know about", "recall", "remember this"; starting research on a topic that may have prio...
Auto-save research progress using sage_autosave_check MCP tool. INVOKE WHEN: user asks to research, compare, analyze, or investigate topics; after completing web searches; when synthesizing conclusions ("theref...
Systematic debugging framework with root cause investigation, tracing, defense-in-depth validation, and verification. Use when: 'bug', 'test failure', 'unexpected behavior', 'error', 'not working', 'broken', be...
Brainstorm ideas and design workflows with a beads expert. Use when: 'help me plan', 'how should I structure this', 'what beads features', 'brainstorm', 'before I create tasks', 'design my workflow'. For ideati...
Problem-solving frameworks for breakthrough thinking - collision zones, simplification cascades, meta-patterns, scale testing, inversion, and dispatch guide. Use when: 'stuck', 'can't find solution', 'too compl...
Generate and review documentation for competition organizers using Diataxis framework. Use when writing docs for organizer workflows like creating competitions, managing divisions, scheduling heats, handling re...
Centralizes Diataxis documentation framework guidance so Claude can write, review, or improve documentation following the four distinct types (tutorials, how-to guides, reference, explanation).
Guide for debugging issue on a specific code sections, pattern, or files. Used this skill when user asking for assistant when debugging an issues or explaining a code.
Diagnose system performance issues including CPU, memory, disk, and network. Use when the user says "server is slow", "high CPU", "out of memory", "disk full", "performance issues", or asks to debug system perf...
Parse and analyze system and application logs. Use when the user says "find errors in logs", "analyze logs", "check journalctl", "what's in the logs", "debug from logs", or asks to investigate log files.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.