Loading...
Loading...
Found 10,354 Skills
Convert a course outline into a fully fleshed out intelligent textbook. Use when: (1) User provides a URL containing a course outline/syllabus (2) User asks to "generate a course" or "create a textbook" from an outline (3) User wants to expand a course description into full learning materials Generates: learning graph, chapter structure, MicroSim specifications, quizzes, glossary, and FAQ following the intelligent textbooks framework and evidence-based learning design principles.
Review Code
Systematic codebase investigation to extract architectural patterns and implementation details from an existing project, with findings persisted for long-term reuse. Use when the user wants to explore an open-source or existing codebase to understand how it works and inform the development of a new project. Triggers include: "explore this codebase", "investigate this repo", "how does X implement Y", "I want to build X, study how Y does it", "deep dive into this project", "understand how this works".
Search conversation history and semantic memory to recall previous discussions, decisions, and context. Use when the user asks to "search memory", "what did we discuss", "remember when", "find previous conversation", "check history", or before starting work to recall prior decisions.
Teach Claude ANY topic - code libraries, APIs, concepts, tools, methodologies, or domains. Researches via web and docs, then retains knowledge as a permanent skill. Use when user says "/learn <topic>", "learn about X", "teach yourself Y", "become an expert on Z". Examples - "/learn stripe" for payments, "/learn GTD" for productivity, "/learn israeli-tax-law" for domain knowledge.
Use this to verify whether the work meets requirements when completing tasks, implementing main features, or before merging.
Create and improve OpenAkita skills. It is used when you need to: (1) create new skills for repetitive tasks, (2) improve existing skills, (3) encapsulate temporary scripts into reusable skills. Skills are the core mechanism of OpenAkita's self-evolution.
Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles and branches, persistence with checkpoin...
Orchestration mode for implementation tasks. Manages the plan → code → review loop. Use /orchestrate <requirements> or let /implement invoke it.
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured feature planning or says "use spec-driven" or "follow the spec process".
A guide for creating effective Skills. It is used when users want to create new Skills (or update existing Skills) to extend Claude's capabilities, including professional knowledge, workflows or tool integration.
Manage tasks, track progress, and log daily updates via the ai-todo CLI. Trigger scenarios: 1) EXPLICIT — user mentions tasks, todos, to-do lists, progress tracking, daily standup, sprint planning, project management, work logs, or task completion. 2) POST-ACTION (proactive) — after git commit, git push, deploy to Vercel, merge PR, release, or any significant milestone (feature implemented, bug fixed, refactor done), proactively log progress and update/complete related tasks. When git-tools or vercel:deploy skill finishes, ALWAYS trigger this skill to record what was accomplished. 3) PRE-ACTION (proactive) — when user discusses implementation plans, architecture design, feature breakdown, technical specs, RFC, sprint planning, or requirement analysis, proactively suggest creating tasks to track planned work. When brainstorming skill completes, trigger this skill to convert outcomes into trackable tasks. 4) SESSION-END — when a work session involves substantial code changes, suggest a progress summary before ending. This skill connects to ai-todo (https://ai-todo.stringzhao.life) for persistent task management across sessions.