npx skills add smithery/omer-metin --skill control-systems
omer-metin/skills-for-antigravity
control-systems
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.
Installation
npx skills add omer-metin/skills-for-antigravity --skill control-systems
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Configures AWS Application Recovery Controller (ARC) for operational resilience: routing contro…
2.3K installsAnalyzes Axiom query patterns to find unused data, then builds dashboards and monitors for cost…
1.7K installsBuild a safe recommendation plan for PlanetScale Postgres Database Traffic Control budgets and …
12 installsPose-conditioned generation on RunComfy via the `runcomfy` CLI. Routes across Kling 2-6 Motion …
354.3K installsControl mouse, keyboard, and screen for desktop automation tasks
4K installsExpert UI/UX design guidance for unique, accessible interfaces. Use for visual decisions, color…
3.9K installsAlso in this package
Other skills from omer-metin/skills-for-antigravity · top by installs.
npx skills add omer-metin/skills-for-antigravity
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,156 B -
docs
SUMMARY.md286 B
History
- First seen on skills.sh
- First recorded snapshot · 105 installs
SKILL.md
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.