claude-brainlab

Use when the user wants to log meeting or call notes for a project — task assignments per student, follow-ups, deadlines. Creates Operon file-tasks in the vault (one .md per task, assigned to the person) and interleaves them on the project hub card via Task Wikilink Overlay. Trigger on: "запиши звонок", "записать встречу", "call notes", "что сделать студентам", "задачи после звонка".

Use when the user wants to set up the Operon task manager in their Obsidian vault the way this lab does it, or reproduce that setup on a fresh machine — flat project tags (no parentTask hierarchy), a "my tasks" table dashboard, service-link badges on project pages, emoji task icons, and day-boundary auto-archiving. Applies plugin settings (data.json), templates, a CSS snippet, optional main.js display patches, and an optional macOS launchd archiver. Trigger on "set up Operon", "настрой Operon как у тебя", "operon setup", "воспроизведи таск-систему Obsidian", "как у тебя задачи и страницы проектов в Obsidian".

This skill should be used when the user wants to write a peer-review of a research paper for any conference or journal, to the standard of a strong reviewer at a top venue. Trigger on "напиши ревью на статью", "write a review", "review this paper", "прогони ревьюера/теоретика/литератора", or when handed a paper PDF to review. Runs a thorough reviewer + theoretician (appendix/proofs) + literature-scout (related work, uncited papers) + experiments-auditor (numbers, hyperparameter search, released code) pass, extracts the user's own PDF annotations, surfaces a weakness skeleton in chat first, then writes one review markdown file per paper in the Summary / Strengths-and-Weaknesses / Questions / Limitations format. Handles prompt injections inside PDFs safely. Venue-agnostic.

Use when the user gives a code repository (a GitHub URL or a local/server path) and wants it added to the Obsidian Code library — a one-time deep analysis that produces a structured set of Markdown notes mapping how the repo works (entrypoint, modules, where to look to change X), without copying the code. Trigger on "add this repo to the code library", "разбери этот репозиторий", "code-ingest <url>", "задокументируй код", or when a project starts using an external repo that is not yet in Code/.

Reference for how the user runs and documents code. Use when an agent needs to understand the user's code workflow — which coding skills and rules apply, how the Obsidian Code library works, how a project hub card records the repo it uses and the project-specific edits, and how experiments are monitored (graphs + tables + loop). Trigger on "how do we work with code here", "что у меня есть для кодинга", "code workflow", before running experiments for a project, or when onboarding to a project that has code.

Use when the user wants to create a new research project, set up a new paper project, initialize a project folder, or says "create project", "new project", "setup project". Creates the standard ~/Papers/<project>/ folder structure with .claude/CLAUDE.md configured for SSH servers and code paths.

Use when the user wants to read/edit Google Docs from Claude, refresh expired Google Workspace MCP tokens, troubleshoot google-workspace MCP errors, change OAuth scopes, or says "переавторизуй google", "google docs не работает", "fix google mcp", "re-auth google", "обнови токены google". Knows the OAuth gotchas (Web vs Desktop client, restricted scope, browser cache, Test users) and the operational recipes.

Use when the user wants to track a new research idea or paper project in Obsidian without setting up a code folder. Use when user says "new paper", "new idea", "add project", or describes a research idea with students and organization. Creates Obsidian hub card + people cards. No filesystem folder created.

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. Covers both the note structure and the operational workflow for launching, monitoring, and post-mortem of multi-hour ML runs on shared servers.

Ingest papers from AlphaXiv/arXiv into Zotero + Obsidian. Trigger when user provides an arXiv URL or AlphaXiv folder link and wants a full literature note created. Handles BibTeX from external APIs, PDF download, tex-source figure/table extraction, creation of a proper Zotero parent paper item with child PDF attachment, duplicate prevention, and an especially detailed Obsidian note with 8-section AI Explanation (incl. Prerequisites) written by haiku, plus a strict BibTeX audit at the end.

This skill should be used when the user asks to "найди новые статьи", "поищи свежие статьи по моей теме", "scan for new papers", or wants a library-aware arXiv shortlist written into the Obsidian literature inbox.

This skill should be used when the user wants to turn a research paper into social-media posts to promote it, on Telegram, Twitter/X, or Habr (LinkedIn is paused by user request). Trigger on "сделай пост по статье", "напиши пост в тг/твиттер/хабр", "post about this paper", "promote this paper", "оформи статью в пост", "тред по статье", or a request for any single one of those platforms. Produces copy-paste-ready posts in the project's Obsidian folder, with figures pulled from the arXiv version, in the user's voice (never AI-sounding).

This skill should be used when the user asks to create presentation slides, rewrite or polish a Beamer deck, prepare a lecture or conference talk, fix slide layout, improve mathematical slides, use terminal style, make slides clearer, combine or split slides, or otherwise work on a presentation in LaTeX Beamer.

Use when the user wants to process want_2_read.md. Parse raw paper entries, fully ingest them through Zotero and Obsidian, classify them into the current Literature folders, and update want_2_read.md with final wiki-links, Zotero links, and detailed descriptions.

This skill should be used when the user asks to "prepare conference presentation", "create presentation slides", "make a Beamer talk", "use terminal style", "терминальный стиль", "design poster", "make academic poster", "write promotion content", or mentions post-acceptance conference preparation. Provides workflows for Beamer presentations, posters, and promotion content.

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.

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 "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.

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.

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.

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.

This skill should be used when the user asks to "read this PDF", "extract text from PDF", "what's in this PDF", or provides a PDF file path and wants to understand its contents. Extracts structured text from PDF files using PyMuPDF with pypdf fallback.

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.

Use when the user asks to "restore session", "continue previous conversation", "recall what we discussed", "load past context", or wants to resume work from a prior Claude session. Lists saved conversations and loads selected one as context.

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 "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. 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.