analyze_current
Read and understand the current baseline implementation. Extract all relevant information about the existing approach without modifying anything, and record…
Create a new Jupyter notebook implementing the method from the research paper, using the same data as the baseline. Record implementation details and measured metrics as a structured JSON entry.
$ npx -y skills add Upsonic/Upsonic --skill implement --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/implementContext preview
The summary Claude sees to decide when to auto-load this skill.
Create a new Jupyter notebook implementing the method from the research paper, using the same data as the baseline. Record implementation details and measured metrics as a structured JSON entry.
Create a new Jupyter notebook implementing the method from the research paper, using the same data as the baseline. Record implementation details and measured metrics as a structured JSON entry.
Phase 4 — after benchmark metrics are defined and baseline values are extracted.
| Parameter | Type | Description | |-----------|------|-------------| | experiment_path | path | `experiments/{research_name}/` |
1. **Install dependencies:**
2. **Write `{experiment_path}/new_requirements.txt`:**
3. **Create `{experiment_path}/new.ipynb`** with this structure:
[Markdown] # {Research Name} - New Method Implementation
[Markdown] ## 1. Setup & Imports
[Code] import statements + dependency checks
[Markdown] ## 2. Data Loading
[Code] load from experiments/{research_name}/current_data/
(use the SAME data loading logic as current.ipynb)
[Markdown] ## 3. Data Preprocessing
[Code] preprocessing as required by the new method
(note any differences from baseline preprocessing)
[Markdown] ## 4. Model Implementation
[Code] implement the new method from the paper
[Markdown] ## 5. Training
[Code] train the model
(use same train/test split as baseline for fair comparison)
[Markdown] ## 6. Evaluation
[Code] compute ALL comparison metrics defined in Phase 3
[Markdown] ## 7. Results Summary
[Code] print all metrics in a structured format4. **Implementation rules:**
5. **Run the notebook** end-to-end and verify it executes without errors.
6. **Append a Phase 4 entry to `{experiment_path}/log.json`** under `phases`:
{
"name": "Phase 4: Implement",
"completed_at": "2026-04-17T11:30:00Z",
"new_dependencies_installed": [
{"name": "catboost", "version": "1.2.5"}
],
"training": {
"split": 0.2,
"seed": 42,
"stratified": true
},
"metrics": {
"accuracy": 0.8721,
"f1": 0.7310,
"roc_auc": 0.9288,
"training_time_seconds": 45.2
},
"notebook_executed": true,
"errors": [],
"warnings": []
}Do not overwrite earlier entries; append to the `phases` array.
Read and understand the current baseline implementation. Extract all relevant information about the existing approach without modifying anything, and record…
Define the comparison metrics and extract baseline values from the current implementation. Record them as a structured JSON entry so downstream phases and…
Compare baseline and new implementation results. Produce the machine-readable final report `result.json`, update `experiments.json`, and append a row to…
Set up and manage the experiment folder structure. This is Phase 0 — it runs before any analysis begins. All bookkeeping files are JSON (never markdown).
Maintain a **machine-readable** progress file so dashboards, CLIs, and notebooks can poll the experiment's state at any time. The file is a JSON document —…