Individual skill
stepinfo-3d
Use this skill when computing 3D step-response performance metrics for point-to-point drone flight — rise time, settling time, percent overshoot, and steady-state error based on Euclidean distance to the final target. Use instead of 1D stepinfo for any flight where all three position axes move simultaneously.
tasks/drone-planning-control/environment/skills/stepinfo-3d/SKILL.md
Source commit f860ecf02ef53412a030f8661c83d644b739ff01
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,911
- Repository last updated
- Nov 4, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- benchmark Repository topic
- skillsbench Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 3D Step-Response Metrics (stepinfo_3d)
## When to Use
| Scenario | Metric to use |
|---|---|
| Pure z-step (hover, takeoff, land) | 1D `stepinfo` on `z` signal |
| Diagonal flight (x, y, z all change) | `stepinfo_3d` on 3D Euclidean distance |
| Circular / figure-eight trajectory | Neither — use RMS error or cumulative error |
1D metrics break for diagonal flight because the axes are coupled — thrust that corrects x also affects y and z.
## Metrics Defined
