data / radar / self
General SOP for common requests related to data, radar, self.
npx skills add ECNU-ICALK/AutoSkill --skill data-radar-self --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Describes a general SOP for common requests related to data, radar, self. It guides how to use a set of radar toolbox utilities and configurations to handle data and radar-related tasks.
How it works
- Follow the SOP with placeholders like <PROJECT>/<ENV>/<VERSION>.
- The SOP references a set of modules and files within radar_toolbox, including capturing configuration, loading I/Q data, and transforming radar data into usable formats.
- It lists interactions with a module named radar_toolbox and describes classes such as Frame and RadarDataSaver, as well as functions for loading I/Q data and preparing binary data for numpy conversion.
- It emphasizes using these utilities to interface with FMCW radar hardware, manage radar configurations, process captured radar signals, and transform them into analytical forms for object detection or tracking.
When to use it
Use when the user asks for a process or checklist or when you want to reuse a previously mentioned method/SOP.
What it can touch
The skill references the following: radar_toolbox module, including fmcw_utils.py, utils.py, adc.py, raw_data/adc.py, raw_data/raw_bin_to_numpy.py, capture_session/main.py, and associated configuration and data flow components. It indicates the use of the claude-code tool for implementation.
Caveats
The content is a high-level SOP description and references several components within the radar_toolbox. It does not provide concrete, executable steps outside placeholders and documented function/module names. No outcomes are promised beyond guidance to use the listed utilities and data flow.
# data / radar / self General SOP for common requests related to data, radar, self. ## Prompt Follow this SOP (replace specifics with placeholders like <PROJECT>/<ENV>/<VERSION>): 1) a2fdf42e0ad0be2f6a734526bebf98a0.json#conv_1 2) Use the user questions below as the PRIMARY extraction evidence 3) Use the full conversation below as SECONDARY context reference 4) In the full conversation section, assistant/model replies are reference-only and not skill evidence 5) Primary User Questions (main evidence 6) module": "radar_toolbox", "module_structure": "radar_toolbox\\conf/capture_conf.json;radar_toolbox\\conf/profile_vs1642_exp.cfg;radar_toolbox\\conf/raw_bin_to_numpy.json;radar_toolbox\\TI_data/sensor_com.py;", "module_files_already_generated_doc": [{"file": "radar_toolbox\\fmcw_utils.md", "doc": "# radar_toolbox/fmcw_utils.py Documentation\n\n## Overview\nfmcw_utils.py is a part of the radar_toolbox module and provides utility functions, classes, and constants specifically for frequency modulated continuous wave (FMCW) radar systems. This file is crucial for managing radar models, loading and processing radar data, and preparing captured raw data for analysis.\n\n## Classes\n\n### Ra
- Prompt
- Triggers
- Examples
- Example 1
What does the data / radar / self skill do?
General SOP for common requests related to data, radar, self.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill data-radar-self --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.