Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

E20 Converter Control Loop Stability

ASecurity

Use when evaluate the closed-loop stability of a spacecraft power converter or regulator under ECSS-E-ST-20C clause 5.7.5: categorize the loop as a switching converter, a linear regulator or a bus control loop, set the phase-margin and gain-margin targets that category carries unless the project requirement overrides them, enumerate the worst-case corner set from the temperature, input-voltage and load extremes, build the open-loop frequency response from the direct-current gain, poles, zeros...

2 stars
0 votes
0 copies
0 views
Added 9/27/2026
ai-agentspythongogit

Works with

claude code

Security Analysis

A100/100

Scanned 9/27/2026

Install to Claude Code

$npx -y skills add ashfordeOU/aero-agent-skills --skill e20-converter-control-loop-stability --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E20 Converter Control Loop Stability?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for E20 Converter Control Loop Stability
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e20-converter-control-loop-stability/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e20-converter-control-loop-stability)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: e20-converter-control-loop-stability
description: "Use when evaluate the closed-loop stability of a spacecraft power converter or regulator under ECSS-E-ST-20C clause 5.7.5: categorize the loop as a switching converter, a linear regulator or a bus control loop, set the phase-margin and gain-margin targets that category carries unless the project requirement overrides them, enumerate the worst-case corner set from the temperature, input-voltage and load extremes, build the open-loop frequency response from the direct-current gain, poles, zeros, any right-half-plane zero and the modulator transport delay, locate the gain- and phase-crossover frequencies, and confirm every corner holds both margins rather than the nominal point alone. Trigger: ecss, e-st-20c-clause-5-7-5, converter-control-loop-stability, phase-margin-target, gain-margin-target, gain-crossover-frequency, phase-crossover-frequency, worst-case-corner-stability, closed-loop-regulator-margin."
license: Apache-2.0
compliance: STANDARDS-REF
standards:
  - id: ecss
    reference-only: true
gated: false
domain: space-systems
pack: space-systems
compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"
metadata:
  domain: space-systems
  subdomain: ecss
  tags: [ecss, e-st-20-electrical-scope, e20-converter-control-loop-stability, converter-control-loop-stability, phase-margin-target, gain-margin-target, gain-crossover-frequency, worst-case-corner-stability, closed-loop-regulator-margin]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Electrical Engineering -- Converter Control Loop Stability (space-systems/ecss/e20-converter-control-loop-stability)

Use when the task is the clause 5.7.5 stability demonstration of
ECSS-E-ST-20C -- showing that every closed control loop inside a power
converter or regulator keeps a stated phase margin and gain margin,
and showing it at the corners of the operating envelope rather than at
the nominal operating point.

## Domain quick reference

- A control loop is categorized once by what it regulates: a switching
  converter loop (buck, boost, buck-boost, flyback, point-of-load,
  battery charge regulator, shunt regulator), a linear regulator loop
  (series regulator, shunt regulator, low-dropout regulator), or a bus
  control loop (main bus voltage control, maximum-power-point
  control). The category sets the default margin pair the leaf
  applies when the project requirement is silent; a stated project
  requirement always overrides the default, and a requirement that
  asks for a negative margin is rejected rather than accepted.
- The demonstration point is not a single frequency response. The
  envelope is swept as a corner set: each declared axis (temperature,
  input voltage, load) must carry both of its extremes, and the corner
  set is the full combination of them. A corner with no loop model on
  record is a finding in itself -- the margin was never shown there --
  and a model offered under a label that matches no enumerated corner
  is equally a finding, because it cannot be traced to an envelope
  point.
- The open-loop response is assembled from a direct-current gain, a
  set of left-half-plane poles, a set of left-half-plane zeros, an
  optional right-half-plane zero and a transport delay. The
  right-half-plane zero and the delay both add phase lag without
  removing gain, which is why a boost-derived topology and a
  digitally sampled loop lose margin where a buck loop does not.
- Phase margin is read at the gain-crossover frequency, where the
  open-loop magnitude passes unity: it is one hundred and eighty
  degrees plus the open-loop phase there. Gain margin is read at the
  phase-crossover frequency, where the open-loop phase passes minus
  one hundred and eighty degrees: it is the attenuation below unity at
  that frequency. A loop whose phase never reaches minus one hundred
  and eighty degrees inside the analysis band has no phase crossover
  and an unbounded gain margin; that is a result, not a failure.

## Workflow

1. Categorize the loop kind; reject a kind that is not a clause 5.7.5
   converter or regulator loop before any response is built.
2. Take the default margin pair for that category and apply the
   project requirement over it, field by field, rejecting a negative
   or non-numeric target.
3. Enumerate the worst-case corners from the declared envelope axes.
   Reject an axis list that is missing a required axis, carries an
   unrecognized axis, or offers a single value where two extremes are
   needed.
4. For each enumerated corner, take its loop model and locate the
   gain-crossover frequency inside the analysis band by bisection on
   the magnitude, rejecting a band that starts below unity gain or
   ends above it.
5. Read the phase margin at that crossover. Locate the phase crossover
   the same way and read the gain margin there, treating the absence
   of a phase crossover in the band as an unbounded gain margin.
6. Compare both margins against the targets with a representation
   tolerance, so a corner that sits exactly on the target is reported
   as compliant rather than a few bits short.
7. Aggregate the coverage findings and the per-corner margin findings;
   the loop is stable to clause 5.7.5 only when both lists are empty.

## Pitfalls

- Demonstrating the margins at the nominal operating point and
  declaring the loop stable -- clause 5.7.5 asks for the worst case,
  and the worst case is normally cold temperature at maximum input
  voltage and minimum load, where the gain is highest and the
  crossover has moved up into the delay-dominated region.
- Reading phase margin at the phase crossover and gain margin at the
  gain crossover, which silently swaps the two numbers; the phase
  margin belongs at unity gain and the gain margin at minus one
  hundred and eighty degrees of phase.
- Omitting the modulator and sampling delay because it adds no
  magnitude. It adds phase lag in proportion to frequency, so it costs
  nothing at low frequency and can consume the entire margin once the
  crossover is pushed up by a high-gain corner.
- Modelling a boost-derived or buck-boost-derived topology without its
  right-half-plane zero; the magnitude then looks the same while the
  phase is optimistic by tens of degrees near crossover.
- Searching for a crossover in a band that does not bracket it and
  taking the band edge as the answer -- a band whose lower edge is
  already below unity gain, or whose upper edge is still above it,
  gives no crossover and must be rejected, not clamped.
- Treating an unbounded gain margin as a missing result and failing
  the corner; a loop whose phase stays above minus one hundred and
  eighty degrees across the analysis band has no phase crossover, and
  the gain margin is genuinely unbounded there.

## Behavior contract (gate 3)

The loop categorization, margin-target, corner-enumeration,
frequency-response, crossover-search and margin-comparison logic is
exercised by the gate 3 contract test:
scripts/test_e20_converter_control_loop_stability.py against
scripts/e20_converter_control_loop_stability_logic.py (stdlib
unittest, offline). Run:
python3 scripts/test_e20_converter_control_loop_stability.py

## Compliance

- ECSS standards are freely downloadable (ESA); cite the source and
  paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.

Attribution

ashfordeOUashfordeOU
View sourceMore from ashfordeOU →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

694821 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →