kumo-assistant
Kumo development assistant for MySQL database management tool. Use when working on Kumo features, understanding architecture, writing tests, or navigating the codebase. Helps with React components, API endpoint...
Discover Data & AI skills, compare source repositories and read the instructions for each workflow.
Kumo development assistant for MySQL database management tool. Use when working on Kumo features, understanding architecture, writing tests, or navigating the codebase. Helps with React components, API endpoint...
Expert assistant for Kumo's Query Module (src/features/query). Use when working with SQL Editor, Monaco editor integration, query execution, result grids, tabs management, AI features, or any query-related comp...
Convert experiment results to Markdown research notes and optionally update research state with evidence
Analyze SAE decoder weights - output influence, feature importance, and decoder similarity
Run credibility checks on feature interpretations including split-half stability and shuffle null tests
Reference skill for Splatoon ability families, AP rungs, token constraints, and domain rules for mechinterp experiments
Manage research state for SAE feature analysis including hypotheses, evidence tracking, and research history
Propose next mechanistic interpretability experiments based on research state, hypotheses, and existing evidence
Domain expert for Splatoon 3 competitive gear abilities and weapon meta. Use when: (1) Labeling or classifying gear build features from SAE analysis, (2) Understanding why specific ability combinations appear i...
Orchestrate a systematic research program to investigate and meaningfully label SAE features
Manage feature labeling workflow - queue management, label storage, similar features, progress tracking
Quick "first look" overview of SAE features - top tokens, activation stats, weapons, families, sample contexts
Reference catalog of recurring SAE feature patterns - check when labeling new features, add new patterns as discovered
Analyze relationships across multiple SAE features - co-activation patterns, shared drivers, and subsystem identification
Execute mechanistic interpretability experiments from JSON specs - family sweeps, itemsets, interactions, minimal cores, validation
Match SAE features between Ultra (24K) and Full (2K) models based on activation patterns and token overlap
Reference for ability family semantic groupings and gameplay meanings
Use ALWAYS. Core development rules for production-ready code - guard clauses, no shortcuts, no mocking.
Use when creating, reviewing, or merging pull requests. Includes CI checks, review requirements, and merge approval rules.
Use when implementing ANY new feature or fixing bugs. Test-Driven Development - write tests BEFORE implementation code.
Use before claiming ANY work is complete. Evidence before claims, always. Non-negotiable verification gate.
PFLICHT bei JEDER Antwort mit Code-Änderungen! Die 8-Punkt-Checklist MUSS als ERSTES in der Response stehen. Keine Ausnahmen.
Use when deciding whether to delegate work to subagents. Lists available agents with triggers and capabilities. Delegate aggressively.
Use when facing ANY technical issue. Systematic debugging - root cause investigation BEFORE attempting fixes.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.