claude-scholar

Run the full post-experiment workflow in one command: strict statistical analysis, real scientific figures, and a decision-oriented results report. Uses results-analysis + results-report as a two-stage workflow.

Incrementally fix Python type and lint errors:

Create or verify a checkpoint in your workflow.

Comprehensive security and quality review of uncommitted changes:

Commit changes following Conventional Commits format (local only, no push).

Create a new project from template with uv and Git initialization

Analyze the current session and extract any patterns worth saving as skills.

Read one or more papers and update the global paper-miner writing memory with reusable writing patterns, structure signals, reusable phrasing, venue-specific signals, and rebuttal-friendly language.

Ingest a new Markdown file or folder into the bound Obsidian project knowledge base by classifying it, deciding durable vs raw, and routing it to the right canonical destination

Bootstrap an Obsidian project knowledge base for the current research repository, either as a fresh project or by importing an existing code plus Markdown folder

Repair or strengthen Obsidian wikilinks across canonical project notes without requiring canvas, bases, or extra concept/dataset trees

Manage a single canonical note lifecycle inside the bound Obsidian project knowledge base, including archive, purge, rename, and candidate lookup

Normalize paper notes inside an Obsidian project knowledge base, enrich metadata, and connect them primarily to project knowledge plus the default literature canvas

Manage an Obsidian project knowledge base lifecycle for the current repository: detach, archive, purge, or rebuild

Generate a literature review and project-linked synthesis from paper notes already stored in the Obsidian project knowledge base

Force a filesystem rescan or incremental repair sync between the current research repository, its project memory, and the bound Obsidian knowledge base

Generate optional Obsidian .base views and, when explicitly requested, project or experiments canvas files for the bound project knowledge base

Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code.

Design academic poster for conference

Create conference presentation slides quickly

Generate promotion content for multiple platforms

Start systematic review response workflow for professional rebuttal writing

Safely identify and remove dead code with test verification:

Initialize a research project with Zotero-integrated literature review. Creates Zotero collections, searches and imports papers, analyzes content, and generates literature review and research proposal.

This directory contains slash commands that are installed to `~/.claude/commands/sc/` when users run `superclaude install`.

name: sc:agent

Comprehensive code analysis across quality, security, performance, and architecture domains

Interactive requirements discovery through Socratic dialogue and systematic exploration

Build, compile, and package projects with intelligent error handling and optimization

```yaml

Systematically clean up code, remove dead code, and optimize project structure

Design system architecture, APIs, and component interfaces with comprehensive specifications

Generate focused documentation for components, functions, APIs, and features

Provide development estimates for tasks, features, or projects with intelligent analysis

Provide clear explanations of code, concepts, and system behavior with educational clarity

Git operations with intelligent commit messages and workflow optimization

List all available /sc commands and their functionality

Feature and code implementation with intelligent persona activation and MCP integration

Apply systematic improvements to code quality, performance, and maintainability

Repository Indexing - 94% token reduction (58K → 3K)

Generate comprehensive project documentation and knowledge base with intelligent organization

Session lifecycle management with Serena MCP integration for project context loading

Project Manager Agent - Default orchestration agent that coordinates all sub-agents and manages workflows seamlessly

Ultra-intelligent command recommendation engine - recommends the most suitable SuperClaude commands for any user input

Task reflection and validation using Serena MCP analysis capabilities

Deep web research with adaptive planning and intelligent search

Session lifecycle management with Serena MCP integration for session context persistence

SuperClaude command dispatcher - Use /sc [command] to access all SuperClaude features

Intelligent MCP tool selection based on complexity scoring and operation analysis

Meta-system task orchestration with intelligent breakdown and delegation

Multi-expert specification review and improvement using renowned specification and software engineering experts

Execute complex tasks with intelligent workflow management and delegation

Execute tests with coverage analysis and automated quality reporting

Diagnose and resolve issues in code, builds, deployments, and system behavior

Generate structured implementation workflows from PRDs and feature requirements

Configure your preferred package manager (npm/pnpm/yarn/bun)

Enforce test-driven development workflow. Scaffold interfaces, generate tests FIRST, then implement minimal code to pass. Ensure 80%+ coverage.

Commit changes with Conventional Commits format and push to GitHub remote repository.

Check and update CLAUDE.md memory based on changes to skills, commands, agents, and hooks.

Update README documentation and push changes to GitHub.

Run comprehensive verification on current codebase state.

Batch read papers from Zotero and create/update detailed reading notes, preferably inside the bound Obsidian project knowledge base

Read and analyze papers from a Zotero collection, then synthesize them into the bound Obsidian project knowledge base or markdown review outputs

ML project architecture specialist for code structure, module design, and pattern consistency. Use PROACTIVELY when modifying code structure, adding new modules, or maintaining architectural patterns. Provides ML project framework with factory/registry patterns.

Expert debugger specialized in deep code execution flow analysis and root cause investigation. Use when you need to analyze code execution paths, build execution chain diagrams, trace variable state changes, or perform deep root cause analysis.

Build and Python type error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.

Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.

You are an expert Development Planning specialist focused on translating requirements into structured, actionable development plans. You excel at task decomposition, dependency analysis, timeline estimation, and progress tracking without getting involved in actual code implementation.

You are the Kaggle Knowledge Miner, specializing in extracting and organizing technical knowledge from Kaggle competition winning solutions.

You are a literature review specialist operating inside an Obsidian project knowledge base.

You are a literature review specialist focusing on academic research in AI and machine learning. Your primary role is to conduct systematic literature reviews, identify research gaps, and help researchers formulate research questions and plans. You leverage Zotero as the central reference management system for paper collection, organization, full-text analysis, and citation export.

You are the Academic Writing Knowledge Miner.

Use this agent when the user asks to "write rebuttal", "respond to reviewers", "analyze review comments", or needs help with academic paper review response. This agent specializes in systematic rebuttal writing with professional tone and structured responses.

Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (vulture, pip-audit, pyflakes) to identify dead code and safely removes it.

You are the default Obsidian knowledge curator for research projects.

You are a Senior Product Analyst specializing in translating requirements into structured user stories with acceptance criteria. Your expertise lies in extracting user value from technical implementations, conversations, and documentation while maintaining a strict user-centric perspective.

Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.

Universal UI Blueprint Engineer that transforms any functional requirement into visual ASCII interface designs, user stories, and interaction specifications. Excels at converting brief descriptions into comprehensive user journeys with spatial layout visualization.

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.

This skill should be used when the user asks to "learn from Kaggle", "study Kaggle solutions", "analyze Kaggle competitions", or mentions Kaggle competition URLs. Provides access to extracted knowledge from winning Kaggle solutions across NLP, CV, time series, tabular, and multimodal domains.

Organize messy conference LaTeX template .zip files into clean Overleaf-ready structure. Use when the user asks to "organize LaTeX template", "clean up .zip template", or "prepare Overleaf submission template".

This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.

Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, conducting literature reviews, finding related work, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, citation verification workflows, and paper discovery/evaluation criteria.

Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.

Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.

This skill should be used when the user asks to co-author documentation, draft a proposal, write a technical spec, create a decision doc or RFC, or structure a substantial document through iterative collaboration and reader testing.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team collaboration.

This skill should be used when the user asks to "brainstorm research ideas", "use 5W1H framework", "identify research gaps", "conduct gap analysis", "start research project", "conduct literature review", "define research question", "select research method", "plan research", or mentions research project initiation phase. Provides comprehensive guidance for research startup workflow from idea generation to planning.

This skill should be used when the user asks to "analyze experimental results", "run strict statistical analysis", "compare model performance", "generate scientific figures", "check significance", "do ablation analysis", or mentions interpreting experiment data with rigorous statistics and visualization. It focuses on strict analysis bundles, not Results-section prose.

This skill should be used when the user asks to "write an experiment report", "summarize experimental results", "do experiment retrospection", "write a results report", "写实验总结报告", "写实验复盘", or mentions turning completed experiment artifacts into a structured, decision-oriented research report. It assumes strict analysis should come from `results-analysis` first.

Systematic review response workflow from comment analysis to professional rebuttal writing. Use when the user asks to "write rebuttal", "respond to reviewers", "draft review response", or "analyze review comments". Improves paper acceptance rates.

This skill should be used when the user asks to create a new skill, repair an existing skill, improve trigger descriptions, reorganize skill structure, or make a Claude skill more reusable and internally consistent.

This skill should be used when the user asks to "apply skill improvements", "update skill from plan", "execute improvement plan", "fix skill issues", "implement skill recommendations", or mentions applying improvements from quality review reports. Reads improvement-plan-{name}.md files generated by skill-quality-reviewer and intelligently merges and executes the suggested changes to improve Claude Skills quality.

This skill should be used when the user asks to "analyze skill quality", "evaluate this skill", "review skill quality", "check my skill", or "generate quality report". Evaluates local skills across description quality, content organization, writing style, and structural integrity.

This skill should be used when the user asks to design or review a UI, create a landing page or dashboard, choose colors or typography, improve accessibility, or implement polished frontend interfaces with a clear design system.

Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimizing Python development workflows with uv.

This skill should be used when the user asks to "verify code", "run verification", "check quality", "validate changes", or before creating a PR. Provides comprehensive verification including build, type check, lint, tests, security scan, and diff review.

This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

This skill should be used when the user asks to "remove AI writing patterns", "humanize this text", "make this sound more natural", "remove AI-generated traces", "fix robotic writing", or needs to eliminate AI writing patterns from prose. Supports both English and Chinese text. Based on Wikipedia's "Signs of AI writing" guide, detects and fixes inflated symbolism, promotional language, superficial -ing analyses, vague attributions, AI vocabulary, negative parallelisms, and excessive conjunctive phrases.

Use this skill when papers are collected in Zotero but the user wants detailed reading notes, project-linked literature synthesis, collection-wide paper-note coverage checks, and a connected knowledge map inside the bound Obsidian project knowledge base.

Use this skill when the user discusses experiment design, ablations, training runs, evaluation, baselines, metrics, failures, or result interpretation that should be logged into Obsidian experiment and result notes.

This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

Use for everyday coding tasks that involve writing or modifying source code.

Use when the user asks to "generate daily paper", "search arXiv for EEG papers", "find EEG decoding papers", "review brain-computer interface papers", or wants to create paper summaries for EEG/brain decoding/speech decoding research. This skill automates searching arXiv for recent papers on EEG decoding, EEG speech decoding, or brain foundation models, reviewing paper quality, and generating structured Chinese/English summaries.

Use when creating or configuring Claude Code agents and their frontmatter.

Use only when creating new registrable ML components that require Factory or Registry patterns.

This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem", "something is broken", "this isn't working", "why is this failing", or reports errors/exceptions/bugs. Provides systematic debugging workflow and common error patterns.

This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed verification principles and common error patterns.

Use this skill when the user wants to repair or strengthen Obsidian wikilinks among existing canonical project notes, especially across papers, knowledge notes, experiments, results, and writing.

Use this skill when the user keeps paper notes inside an Obsidian project knowledge base and wants filesystem-first literature review, explicit agent-first Zotero ingestion, `Papers/` plus `Knowledge/` synthesis, collection-wide normalization, and a default literature canvas without Obsidian MCP.

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

This skill should be used when the user asks to start a new research project, import an existing code-plus-Markdown repository into Obsidian, or bind the current repository to a compact research knowledge base for future syncing.

Use this skill when the user wants to detach, archive, purge, or otherwise change the lifecycle state of an Obsidian project knowledge base.

This skill should be used when the user asks to maintain an Obsidian knowledge base for a research project, import an existing research repository into Obsidian, keep project memory or daily notes synchronized, summarize project context into durable notes, or update experiments, results, papers, writing, and plans in an Obsidian vault without requiring MCP.

Use this skill when the user is discussing daily research work, TODOs, plans, standups, meetings, milestones, or general project progress that should be reflected in Obsidian daily notes, plan notes, and hub updates.

Use this skill when generating higher-level synthesis notes such as literature reviews, comparison matrices, project summaries, or other cross-note summaries inside the project knowledge base.

This skill should be used when the user asks to "review paper quality", "check paper completeness", "validate paper structure", "self-review before submission", or mentions systematic paper quality checking. Provides comprehensive quality assurance checklist for academic papers.

Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.

This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.

This skill should be used when the user asks to "prepare conference presentation", "create presentation slides", "design poster", "make academic poster", "write promotion content", "create Twitter thread", or mentions post-acceptance conference preparation. Provides comprehensive workflow for presentation, poster, and promotion content creation.

5 hooks across 5 events