Loading...
Loading...
Found 24 Skills
Build a multi-page Markdown wiki directory for a large software repository after reading and analyzing the whole codebase. Use when the agent is asked to create repository wiki documentation, onboarding docs, architecture guides, codebase tours, maintainer handbooks, or deep explanations of modules, core code paths, algorithms, design decisions, tradeoffs, tests, tooling, and operations for code learners or new maintainers. Optimized for large repositories with hundreds of thousands of lines of code where maintainers need broad coverage and deep subsystem documentation. Also supports optional Rspress/static documentation site setup when the user explicitly asks to publish or deploy the generated wiki. Supports Markdown output with Mermaid, Graphviz, and KaTeX where useful.
Extract and organize Claude Code session history into project .chats directory. Use when users want to document their Claude sessions, export conversation inputs, or maintain a log of instructions given to Claude.
Build a per-target knowledge-base markdown next to the active profile by walking the BSP root and source tree. Use after init-image / init-source; not for editing profile fields.
Transform audio recordings into professional Markdown documentation with intelligent summaries using LLM integration
Use when asked to create a code walkthrough, explain how code works linearly, generate a walkthrough for a PR or codebase, or when user says /walkthrough. Triggers on "walkthrough", "explain the code", "how does this work", "walk me through".
Read an academic paper together in three passes of increasing depth — a bird's-eye profile, an interactive close reading, and a line-by-line derivation or reproduction — using this directory as a reading workspace that remembers you and your papers across sessions. Give it PDF paths or a title, arXiv ID, or DOI.
Creates and manages project artifacts (research, spikes, analysis, plans) using templated scripts. Use when asked to "create an ADR", "research topic", "spike investigation", "implementation plan", or "create analysis". Provides standardized structure, naming conventions, and helper scripts for artifact organization. Works with .claude/artifacts/ directory, Python scripts, and markdown templates.
Inspect multiple reference or benchmark videos shot by shot, record observable visual and audio evidence independently for each source, then synthesize their recurring short-form style grammar, one-off details, imitation boundaries, and generator risks in one human-readable Markdown report. Use before image prompt construction, video request architecture, Seedance workflow creation, or batch media generation when reference footage defines the desired production language.
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.
Build project documentation sites with MkDocs static site generator. USE WHEN user mentions mkdocs, documentation site, docs site, project documentation, OR wants to create, configure, build, or deploy documentation using Markdown. Covers installation, configuration, theming, plugins, and deployment.
Create analytical archival summaries of AI conversations, capturing intellectual journeys, key insights, and technical logs. Use when archiving, saving, or documenting a chat session.
Multi-agent parallel development cycle with requirement analysis, exploration planning, code development, and validation. Orchestration runs inline in main flow (no separate orchestrator agent). Supports continuous iteration with markdown progress documentation. Triggers on "parallel-dev-cycle".