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/tolerance-tuning.md
View on GitHub# Cycling: Tune Tolerance (Route A, on Phase 4 failure)
Load this in addition to `references/cycling-pipeline.md` only when `verifySegmentation` returns `TuningRecommended == true`. For a user-provided schedule, use `references/cycling/schedule-verification.md` instead. Skip this file entirely when the user has already fixed Tolerance in an earlier turn and the current call is a re-run.
## Phase 5 — Log-scale Tolerance sweep
Load `references/parameter-tuning.md` and run the log-scale Tolerance sweep described there (§ Tolerance Log-Scale Sweep). Pick the largest Tolerance value that drops `TuningRecommended` back to `false`, apply it (`parser.Tolerance = <value>`), re-segment, and re-verify:
```matlab
tolCandidates = [5e-5, 1e-5, 5e-6, 1e-6, 5e-7, 1e-7];
for t = tolCandidates
parser.Tolerance = t; % invalidates cached segmentation
report = verifySegmentation(parser);
if ~report.TuningRecommended % largest passing value wins
break;
end
end
segmented = segmentData(parser); % re-segment with the chosen Tolerance
```
Report the chosen value as "tuned from Phase 5 sweep" in the Phase 7 summary, then continue with Phase 4b in `references/cycling-pipeline.md`.
### Sweep has no effect — check for tester-inserted artifact steps first
If `MismatchFraction` is identical at every Tolerance, inspect `MismatchGroups` before stopping. When every mismatch is a **tester-inserted artifact step** (1-3 samples per cycle between stages), no Tolerance can classify it: `segmentData` correctly leaves it `Undefined` and it contributes no features. This is a benign verifier finding, not a mis-set Tolerance. Keep the default Tolerance, continue with Phase 4b, extract, and name the artifact steps in the Phase 7 report.
### STOP: still recommends tuning after sweeping
**Still `TuningRecommended == true` after sweeping down to 1e-7, with mismatches on substantive steps** → STOP. Present the `MismatchGroups` table, the achieved `MismatchFraction`, the tried Tolerance values, and the `DiagnosticDt`. The data may be pre-averaged or the chemistry may need a different classifier — ask the user before proceeding with a Tolerance choice.
## IC / DV / DT smoothing
If curves look noisy or peaks look flattened, tune the differential-curve smoothing parameters — see `references/parameter-tuning.md` § Differential Curve Parameters.
----
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 |