
Review and refactor code for top-down readability by reorganizing functions, grouping related helpers, and rewriting noisy comments without changing behavior.
Write small, readable, testable Python functions with clear names and explicit inputs and outputs.
Create operational handoff markdowns that capture what was completed, what is stopped, what remains pending, which artifacts matter, and which commands the next agent should run next.
Generate beginner-friendly Moodle programming questions with tags clarification, partial answer preload scaffolding, auto-created test cases, actionable hints, and feedback about common beginner mistakes.
Write clear, structured, beginner-friendly README files for GitHub repositories that explain purpose, setup, and usage.
Generate beginner-friendly Moodle programming questions with tags clarification, partial answer preload scaffolding, auto-created test cases, actionable hints, and feedback about common beginner mistakes.
Plan, launch, monitor, and document long-running experiments or validation sweeps with smallest-real-data smoke scopes, fresh experiment prefixes, live status artifacts, rolling logs, and promotion to full runs only after explicit pass criteria are met.
Write small, readable, testable Python functions with clear names and explicit inputs and outputs.
Create focused Python classes and choose matching snake_case module filenames when adding or refactoring class-based code.
Review per-subject performance to identify likely outliers, distinguish bad data from difficult but valid cases, and document whether subject exclusion is justified before any filtered rerun.
Review and refactor code for top-down readability by reorganizing functions, grouping related helpers, and rewriting noisy comments without changing behavior.
Write precise, specific descriptions for agent skills, tools, and functions so that AI agents can route to them accurately.
Resume repository work from an existing handoff markdown by reading it first, executing pending tasks in order, and marking completed tasks with `Done? = Yes` only when concrete evidence exists.
Resume repository work from an existing handoff markdown by reading it first, executing pending tasks in order, and marking completed tasks with `Done? = Yes` only when concrete evidence exists.
Plan, launch, monitor, and document long-running experiments or validation sweeps with smallest-real-data smoke scopes, fresh experiment prefixes, live status artifacts, rolling logs, and promotion to full runs only after explicit pass criteria are met.
Turn ambiguous, half-baked, or outdated plans into living planning docs aligned with code, config, paths, naming contracts, execution flow, caches, EDA outputs, and debugging navigation.
Choose efficient hyperparameter search strategies for finding optimal parameter sets or parameter pairs, favoring random search, Bayesian optimization, successive halving, evolutionary methods, or population-based training over brute-force grids. Use when an experiment, detector, or training pipeline must tune parameters under compute and evaluation-cost constraints.
Write precise, specific descriptions for agent skills, tools, and functions so that AI agents can route to them accurately.
Create operational handoff markdowns that capture what was completed, what is stopped, what remains pending, which artifacts matter, and which commands the next agent should run next.
Turn ambiguous, half-baked, or outdated plans into living planning docs aligned with code, config, paths, naming contracts, execution flow, caches, EDA outputs, and debugging navigation.
Choose efficient hyperparameter search strategies for finding optimal parameter sets or parameter pairs, favoring random search, Bayesian optimization, successive halving, evolutionary methods, or population-based training over brute-force grids. Use when an experiment, detector, or training pipeline must tune parameters under compute and evaluation-cost constraints.
Curate manuscript results directly in LaTeX from experiment artifacts, including tables, plots, graphs, images, and detailed scientific interpretation tied to concrete outputs.
Generate an MNE Report HTML that plots blink windows one by one from epoch-based blink data, including true positives, false negatives, false positives, or all blinks, with configurable padding before and after each blink. Use when the user wants the same kind of per-blink sanity-check plotting as the Strategy C Approach 3 report or asks for reusable blink-report plotting from MNE epoch files and blink tables.
Curate manuscript results directly in LaTeX from experiment artifacts, including tables, plots, graphs, images, and detailed scientific interpretation tied to concrete outputs.
Create focused Python classes and choose matching snake_case module filenames when adding or refactoring class-based code.
One-sentence description of what this skill does and when to use it.
Turn complex execution paths into line-by-line IntelliJ IDEA debugging flows with serial tutorial entrypoints, smallest-real-input reruns, exact breakpoint order, and deliberate stepping into editable local dependencies.
Validate data or ML pipelines on the smallest real dataset scope first, then promote to staged batches and full sweeps with the same code path, editable local dependencies, artifact checks, and honest residual-risk reporting.
Validate data or ML pipelines on the smallest real dataset scope first, then promote to staged batches and full sweeps with the same code path, editable local dependencies, artifact checks, and honest residual-risk reporting.
Record and track strategy proposals, code changes, performance metrics, issues encountered, and their cumulative effects on final results to maintain a durable audit trail of what was tried, what worked, and what didn't.
Turn complex execution paths into line-by-line IntelliJ IDEA debugging flows with serial tutorial entrypoints, smallest-real-input reruns, exact breakpoint order, and deliberate stepping into editable local dependencies.
Review per-subject performance to identify likely outliers, distinguish bad data from difficult but valid cases, and document whether subject exclusion is justified before any filtered rerun.
Record and track strategy proposals, code changes, performance metrics, issues encountered, and their cumulative effects on final results to maintain a durable audit trail of what was tried, what worked, and what didn't.
Write clear, structured, beginner-friendly README files for GitHub repositories that explain purpose, setup, and usage.
One-sentence description of what this skill does and when to use it.