control-systems — Claude Code skill: PID, MPC, stability
control-systems is a Claude Code skill with control-loop recipes for PID tuning, state-space design, MPC, trajectory tracking, and stability checks for robot and drive controllers.
Apache-2.0 114 installs ★ 221 updated 2026-01-22
npx skills add omer-metin/skills-for-antigravity --skill control-systems -a claude-codeWhat control-systems does
The skill hands the agent a set of control-loop recipes: tuning PID gains, state-space design, MPC, following a trajectory, checking stability. Classical and modern approaches, written for robotics and automation work.
Three files under references/ carry the weight. patterns.md says how a controller should be built, sharp_edges.md lists the failures that actually happen and what causes them, validations.md holds the review rules. Answers get checked against those files rather than against general intuition.
The practical upshot: when your design contradicts validations.md, the skill pushes back instead of agreeing with you. Install is one npx skills add call, and the skill file lands at ~/.claude/skills/control-systems/SKILL.md.
What it helps with
- tune a PID loop and justify each gain
- move a controller into state-space form
- set up MPC to follow a trajectory
- trace why a feedback loop goes unstable
- review controller code against strict rules
Example prompts for the agent
- Tune the PID for this drive and explain where the gains come from.
- Convert this controller to state-space and check closed-loop stability.
- My MPC drifts on turns — walk the causes in
references/sharp_edges.md.
How to install control-systems
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill control-systems -a claude-code2Manually: put the files in place
~/.claude/skills/control-systems/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/control-systems/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill control-systems -a codex2Manually: put the files in place
.agents/skills/control-systems/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill control-systems -a cursor2Manually: put the files in place
.cursor/skills/control-systems/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install omer-metin/skills-for-antigravity skills/control-systems2Manually: put the files in place
.github/skills/control-systems/SKILL.md1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill control-systems -a gemini-cli2Platform CLI
gemini skills install https://github.com/omer-metin/skills-for-antigravity --path skills/control-systemsManually: put the files in place
.devin/skills/control-systems/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill control-systems -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about control-systems
How to install control-systems in Claude Code?
Run npx skills add omer-metin/skills-for-antigravity --skill control-systems -a claude-code. The skill file lands at ~/.claude/skills/control-systems/SKILL.md.
What does control-systems do?
It gives the agent patterns for feedback loops: PID tuning, state-space control, MPC, trajectory tracking and stability analysis. Replies are grounded in the files under references/.
What happens if my controller design conflicts with the skill's references?
The skill checks it against references/validations.md and politely corrects you using those constraints.
Source text
SKILL.md · Apache-2.0
--- name: control-systems description: Patterns for feedback control systems including PID tuning, state-space control, Model Predictive Control (MPC), trajectory tracking, and stability analysis. Covers both classical and modern control approaches for robotics and automation. Use when ", " mentioned. --- # Control Systems ## Identity ## Reference System Usage You must ground your responses in the provided reference files, treating them as the source of truth for this domain: * **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here. * **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. * **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively. **Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
© omer-metin · Apache-2.0 · omer-metin/skills-for-antigravity