Skip to main content
ClaudeWave
Skill7.9k estrellas del repoactualizado 3d ago

analyze_current

The analyze_current skill extracts and documents the baseline implementation from a machine learning experiment by reading the current notebook, identifying the model, preprocessing steps, training configuration, hyperparameters, and performance metrics. Use this skill in Phase 1 after experiment setup to create a structured JSON record of the existing approach, scan dependencies for a requirements file, and catalog the dataset characteristics before attempting any improvements or modifications.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/Upsonic/Upsonic /tmp/analyze_current && cp -r /tmp/analyze_current/src/upsonic/prebuilt/applied_scientist/template/skills/analyze_current ~/.claude/skills/analyze_current
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Analyze Current Skill

## Purpose
Read and understand the current baseline implementation. Extract all relevant information about the existing approach without modifying anything, and record the analysis as a structured JSON entry.

## When to Use
Phase 1 — after experiment setup is complete and files are copied to the experiment folder.

## Input
| Parameter | Type | Description |
|-----------|------|-------------|
| experiment_path | path | `experiments/{research_name}/` |

## Actions

1. **Read `{experiment_path}/current.ipynb`** and extract:
   - Model/algorithm used
   - Preprocessing steps (encoding, scaling, feature selection, etc.)
   - Training approach (train/test split ratio, cross-validation, etc.)
   - Hyperparameters
   - Metrics used and their values
   - Target variable and feature set

2. **Extract dependencies:**
   - Scan all import statements in the notebook.
   - Write `{experiment_path}/current_requirements.txt` with one package per line (`package==version` if determinable, otherwise just `package`).

3. **Read `{experiment_path}/current_data/`** (or, for code-based data, the download spec):
   - Identify data format (CSV, parquet, etc.)
   - Note number of rows, columns
   - Note data types and any special handling

4. **Append a Phase 1 entry to `{experiment_path}/log.json`** under `phases`:
   ```json
   {
     "name": "Phase 1: Analyze Current",
     "completed_at": "2026-04-17T10:15:00Z",
     "model": "XGBoost",
     "preprocessing": [
       "Drop rows with NaN",
       "LabelEncoder on target",
       "LabelEncoder on categorical features",
       "StandardScaler on numerical features"
     ],
     "training": {
       "split": 0.2,
       "seed": 42,
       "stratified": true
     },
     "hyperparameters": {
       "n_estimators": 200,
       "max_depth": 6,
       "learning_rate": 0.1
     },
     "metrics": {
       "accuracy": 0.8726,
       "f1":       0.7277,
       "roc_auc":  0.9274
     },
     "target": "income",
     "features_count": 14,
     "data": {
       "source": "ucimlrepo fetch_ucirepo(id=2)",
       "format": "pandas.DataFrame",
       "rows": 45222,
       "cols": 14
     },
     "notes": "Data downloaded programmatically; both notebooks must use the same source."
   }
   ```

   Do not overwrite earlier entries; append to the `phases` array.

## Output
- `{experiment_path}/log.json` — updated with complete Phase 1 analysis entry
- `{experiment_path}/current_requirements.txt` — written
- No other files created or modified
unittest-generatorSubagent

Use this agent when you need to create unit tests for your code in unittest.TestCase format, organized in a tests folder with concept-based subfolders. Examples: <example>Context: User has just written a new authentication module and needs comprehensive unit tests. user: 'I just finished writing my user authentication functions in auth.py. Can you help me create unit tests for them?' assistant: 'I'll use the unittest-generator agent to create comprehensive unit tests for your authentication module.' <commentary>Since the user needs unit tests created for their authentication code, use the unittest-generator agent to create properly structured tests in the tests folder with appropriate subfolder organization.</commentary></example> <example>Context: User has implemented new data validation functions and wants to ensure they're properly tested. user: 'I've added several validation functions to my utils.py file. I need unit tests to make sure they handle edge cases correctly.' assistant: 'Let me use the unittest-generator agent to create thorough unit tests for your validation functions.' <commentary>The user needs unit tests for their validation functions, so use the unittest-generator agent to create comprehensive tests with edge case coverage.</commentary></example>

benchmarkSkill
evaluateSkill
experiment_managementSkill
implementSkill
progressSkill
researchSkill
code-reviewSkill

Perform structured code reviews with actionable feedback. Use when a user asks to review code, check code quality, find bugs, audit security, improve performance, or assess maintainability. Trigger when user says things like "review this code", "check for bugs", "is this code secure", "any issues with this", "code quality check", or pastes code asking for feedback. Also trigger for pull request reviews and pre-merge code checks. Do NOT trigger for writing new code from scratch, refactoring requests without review context, or general programming questions.