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

Magnetorquer Control

ASecurity

Use when the task is magnetorquer control, dipole moment calculation, B-dot detumbling, cross-product torque steering, detumbling rate damping, or torque authority limits. Compute the magnetic dipole moment for spacecraft magnetic attitude control with magnetorquers: solve torque = m x B for the required dipole from a torque demand and the local magnetic field vector, apply the B-dot detumbling law to damp body rates, check the achievable torque against the magnetorquer torque authority limit...

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

Works with

claude codecli

Security Analysis

A100/100

Scanned 9/27/2026

Install to Claude Code

$npx -y skills add ashfordeOU/aero-agent-skills --skill magnetorquer-control --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Magnetorquer Control?

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

Security grade badge for Magnetorquer Control
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-magnetorquer-control/badge)](https://www.skillsdirectory.com/skills/ashfordeou-magnetorquer-control)

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

Download with Pro
Files
SKILL.md
---
name: magnetorquer-control
description: "Use when the task is magnetorquer control, dipole moment calculation, B-dot detumbling, cross-product torque steering, detumbling rate damping, or torque authority limits. Compute the magnetic dipole moment for spacecraft magnetic attitude control with magnetorquers: solve torque = m x B for the required dipole from a torque demand and the local magnetic field vector, apply the B-dot detumbling law to damp body rates, check the achievable torque against the magnetorquer torque authority limit, warn when the torque demand lies along the field, and size the torque rod coils. Produces the dipole moment vector, the B-dot control dipole, the achievable torque magnitude, the underdetermined-axis warning, the coil sizing, and the orbit-averaged torque authority. Trigger: magnetorquer, dipole moment, B-dot, detumbling, torque authority, cross-product, magnetic field, coil sizing."
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: adcs
  tags: [adcs, magnetorquer, magnetic, dipole, moment, torque, detumbling, b-dot, cross-product, spacecraft, coil, field, torque-authority, b-field]
  version: 0.1.0
  author: Aero Agent Skills
---

# Magnetorquer Control (space-systems/adcs/magnetorquer-control)

Use when the task is spacecraft magnetic attitude control: computing
the magnetic dipole moment that produces a commanded torque through
the cross-product torque = m x B, B-dot detumbling of body rates,
torque authority limits, or torque rod coil sizing.

## Domain quick reference

- A magnetorquer (torque rod) is a coil that produces a magnetic
  dipole moment m (A m^2); the magnetic field B of the Earth exerts
  the control torque torque = m x B (N m) on the spacecraft.
- The torque is always perpendicular to B: m x B is orthogonal to B,
  so a magnetorquer can only produce torque about axes perpendicular
  to the local field. The torque component along B is unachievable,
  which is the underdetermined-axis limit of magnetic control.
- Required dipole: the minimal dipole that produces a torque demand
  perpendicular to B is m = (B x torque) / |B|^2. The component of
  the demand along B is returned as an underdetermined-axis warning.
- Achievable torque magnitude: |m x B| = |m| |B| sin(theta) where
  theta is the angle between m and B; the maximum for a given dipole
  magnitude is |m| |B|, reached when m is perpendicular to B.
- Torque authority: the largest torque a magnetorquer of dipole
  limit m_max can exert in a field B is m_max * |B|. Authority is
  weakest near the magnetic poles and strongest near the equator.
- B-dot detumbling law: damp the body rate omega by commanding
  m = gain * (omega x B), which equals -gain * Bdot because the body
  frame field derivative is Bdot = -omega x B. The resulting torque
  opposes the rate component perpendicular to B and damps it.
- Orbit-averaged authority: over one orbit the mean of m_max * |B|
  over the sampled field vectors estimates the average torque
  capability available for momentum dumping and pointing.
- Coil sizing: the dipole of a torque rod is N * I * A, the product
  of the number of turns, the drive current, and the coil area.
  Required current for a dipole demand is m / (N * A).
- Units: dipole moment in A m^2, field in T, torque in N m, rate in
  rad/s, coil current in A, area in m^2.
- Magnetic attitude control follows ECSS-E-ST-60 ADCS practice.

## Workflow

1. Get the torque demand vector (from the attitude controller or the
   detumbling law) and the local magnetic field vector B in the body
   frame.
2. Compute the required dipole m = (B x torque) / |B|^2 and check the
   underdetermined-axis warning: torque along B is not producible.
3. For detumbling, compute the B-dot dipole m = gain * (omega x B)
   from the measured body rate and field.
4. Compare the demanded dipole and the resulting achievable torque
   magnitude |m x B| against the magnetorquer torque authority
   limit m_max * |B|; clip the dipole to m_max when it exceeds the
   limit.
5. Size the torque rods: current per coil I = m / (N * A) for the
   selected turns and area; verify the coil current is within the
   driver limit.
6. Estimate the orbit-averaged torque authority from the field
   samples along the orbit to confirm the capability budget.

## Pitfalls

- Demanding torque along B: m x B can never produce it; detect the
  underdetermined axis and report it instead of returning a
  meaningless dipole.
- Dividing by a zero field: |B| = 0 makes the dipole formula
  singular; raise instead of returning nan.
- Forgetting that |m x B| depends on the angle: a dipole parallel to
  B produces zero torque even at full authority.
- Using B-dot gain with the wrong sign: m = gain * (omega x B) must
  oppose the rate, otherwise the law spins the spacecraft up.
- Sizing coils without the driver current limit: the required
  current m / (N * A) must be within what the electronics can
  supply.
- Treating the orbit-averaged authority as instantaneous capability:
  the average hides the per-axis gaps where B is nearly parallel to
  the demand.

## Behavior contract (gate 3)

The dipole computation, B-dot law, authority, and coil sizing logic
is exercised by the gate 3 contract test:
scripts/test_magnetorquer_control.py against
scripts/magnetorquer_control_logic.py (stdlib unittest, offline).
Run:
python3 scripts/test_magnetorquer_control.py

## Compliance

- ECSS (European Cooperation for Space Standardization) standards are
  freely downloadable, copyright ESA; cite the source and paraphrase.
  This leaf cites ECSS as reference only per standards-map.yaml; the
  logic here is generic magnetic attitude control physics (torque =
  m x B, B-dot damping), not ECSS text.
- 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 →