motorcontrol / temp / motor
General SOP for common requests related to motorcontrol, temp, motor.
npx skills add ECNU-ICALK/AutoSkill --skill motorcontrol-temp-motor --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.
# motorcontrol / temp / motor General SOP for common requests related to motorcontrol, temp, motor. ## Prompt Follow this SOP (replace specifics with placeholders like <PROJECT>/<ENV>/<VERSION>): 1) 1.0 2) 编制：李小海 3) 时间：2014年04月02日 4) 本程序为电机控制相关程序 5) 修改记录 6) 2014.04.02 建立文件 7) include "global_variable.h 8) include "hardware_config.h 9) include "function_config.h 10) include "sin256.h For each step, include: action, checks, and failure rollback/fallback plan. Output format: for each step number, provide status/result and what to do next. ## Triggers - Use when the user asks for a process or checklist. - Use when you want to reuse a previously mentioned method/SOP. ## Examples ### Example 1 Input: Break this into best-practice, executable steps.
- Prompt
- Triggers
- Examples
- Example 1
What does the motorcontrol / temp / motor skill do?
General SOP for common requests related to motorcontrol, temp, motor.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill motorcontrol-temp-motor --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.