matlab/matlab-agentic-toolkit / skills-catalog/control-systems/matlab-extract-battery-features
matlab-extract-battery-features
VerifiedExtract battery features in MATLAB from voltage, current, and temperature measurements: multi-cycle cycling tests, HPPC / pulse tests, EIS impedance sweeps, or a single in-field charge or discharge segment. Use when the user asks for battery features, or for SOH, RUL, degradation, internal-resistance, or impedance analysis that needs them. Output is a feature table; does not train SOH / RUL models. Do not trigger only because battery data is present. Triggers on battery* functions such as batteryTestDataParser, batteryTestFeatureExtractor, batteryPulseFeatures, batteryEISFeatures.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.6 KB |
| manifest.yaml | config | 469 B |
| references/cycling-pipeline.md | markdown | 21.1 KB |
| references/cycling/feature-selection.md | markdown | 2.6 KB |
| references/cycling/multi-cell.md | markdown | 5.1 KB |
| references/cycling/postprocess.md | markdown | 2.4 KB |
| references/cycling/schedule-verification.md | markdown | 4.2 KB |
| references/cycling/tolerance-tuning.md | markdown | 2.4 KB |
| references/eis-features.md | markdown | 10.8 KB |
| references/individual-cycling-functions.md | markdown | 10.1 KB |
| references/parameter-tuning.md | markdown | 14.2 KB |
| references/pulse-features.md | markdown | 12.6 KB |
| scripts/checkCyclingProtocol.m | other | 9.2 KB |
| scripts/sweepScheduleAndReport.m | other | 3.7 KB |
| scripts/verifyAgainstSchedule.m | other | 8.5 KB |
| scripts/verifySegmentation.m | other | 6.3 KB |
| scripts/verifySingleSegment.m | other | 3.0 KB |
references/cycling/postprocess.md
View on GitHub# Cycling Postprocessing — Visualization & Feature Ranking
Load this when the user picks **Visualize** or **Rank features** as a next step after cycling feature extraction (see `references/cycling-pipeline.md` Phase 7). Nothing here runs before the feature table is extracted and reported.
## Visualization Options
Offer the plot type that matches what was extracted; roll each with base MATLAB (no skill-owned plot helpers ship on this branch):
| Plot type | Shows | Offer when | One-liner |
|-----------|-------|------------|-----------|
| **Segmented data** | V + I for one cycle, colored by CyclingMode (CC/CV/Rest) | Always — validates segmentation | `gscatter(time, voltage, segmented.CyclingModes)` (or two-panel `tiledlayout` for V and I) |
| **IC/DV/DT curves across cycles** | Overlaid differential curves at regular cycle intervals | When IC/DV/DT extracted | loop `computeDifferentialCurves` across selected cycles, overlay in `tiledlayout` colored by cycle |
| **Feature trends over cycles** | Selected features vs cycle number | Always — degradation trajectory | `tiledlayout` grid, one tile per feature: `plot(featureTable.(cycleVar), featureTable.(name))` |
| **Single feature trend** | One feature vs cycle with trend line | User asks about a specific feature | `plot` + `lsline` |
## Feature Ranking (correlation-based)
When the user has a target variable (capacity, SOH, or cycle number as an age proxy):
```matlab
targetVar = "Discharge_CycleCumulative_capacity"; % or user-specified
cycleVar = parser.CycleIndexVariable;
featureCols = featureTable(:, ~ismember(featureTable.Properties.VariableNames, {targetVar, cycleVar}));
% Drop NaN/constant columns, then correlate with the target
validCols = varfun(@(x) ~all(isnan(x)) & std(x,'omitnan')>0, featureCols, OutputFormat="uniform");
featureCols = featureCols(:, validCols);
corrValues = corr(table2array(featureCols), featureTable.(targetVar), Rows="complete");
[~, sortIdx] = sort(abs(corrValues), 'descend');
rankedNames = featureCols.Properties.VariableNames(sortIdx); % present top-10
```
After presenting the top-N, explain the physical meaning of the leading features using `references/cycling/feature-selection.md`, and compare the ranked list against that file's *expected* top features: agreement means the ranking has physical grounding; a list dominated by "watch for noise" entries means too few cycles, over-smoothing, or a spurious trend.
----
Copyright 2026 The MathWorks, Inc.
----
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |