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

Multi Stage Compressor

ASecurity

Use when you must design or match a multi-stage axial compressor for a gas turbine: compute the overall pressure ratio as the product of the stage pressure ratios, size the stage count required to reach the target pressure ratio from a design stage pressure ratio, account for the reheat factor that inflates the actual work split, size the annulus area from the mass flow, the axial velocity, and the density, distribute the stage work with equal or rising schemes, and correct the rotor speed to...

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

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 multi-stage-compressor --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Multi Stage Compressor?

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

Security grade badge for Multi Stage Compressor
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-multi-stage-compressor/badge)](https://www.skillsdirectory.com/skills/ashfordeou-multi-stage-compressor)

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

Download with Pro
Files
SKILL.md
---
name: multi-stage-compressor
description: "Use when you must design or match a multi-stage axial compressor for a gas turbine: compute the overall pressure ratio as the product of the stage pressure ratios, size the stage count required to reach the target pressure ratio from a design stage pressure ratio, account for the reheat factor that inflates the actual work split, size the annulus area from the mass flow, the axial velocity, and the density, distribute the stage work with equal or rising schemes, and correct the rotor speed to the reference temperature for off-design matching. Produces the stage count, overall pressure ratio, reheat factor, annulus area, and work distribution in SI units that gate the FAR-33 compressor architecture review. Trigger: multi-stage compressor, stage matching, overall pressure ratio, stage count, reheat factor, annulus area, work distribution."
license: Apache-2.0
compliance: STANDARDS-REF
standards:
  - id: far-33
    reference-only: true
gated: false
domain: propulsion
pack: propulsion
compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"
metadata:
  domain: propulsion
  subdomain: axial-compressor
  tags: [multi-stage, multi-stage-compressor, stage-matching, overall-pressure-ratio, stage-count, reheat-factor, annulus-area, work-distribution, corrected-speed, axial-compressor]
  version: 0.1.0
  author: Aero Agent Skills
---

# Multi-Stage Compressor (propulsion/axial-compressor/multi-stage-compressor)

Use when the task is multi-stage axial compressor design and
matching: overall pressure ratio from the stage pressure ratios, the
stage count to meet a target ratio, the reheat factor, the annulus
area layout, the stage work distribution, and the corrected speed for
off-design matching.

## Domain quick reference

- Overall pressure ratio: PR_overall = product of the stage pressure
  ratios, PR_overall = pi_1 * pi_2 * ... * pi_n, dimensionless. Each
  stage pressure ratio must exceed 1. Example: 6 stages at 1.45 give
  1.45**6 = 9.29.
- Stage count: n = ceil(ln(PR_overall) / ln(pi_stage)), with ln the
  natural logarithm. The result is the number of identical design
  stages and is always at least 1. Example: PR_overall 40 with 1.20
  per stage gives ceil(20.23) = 21 stages.
- Reheat factor: RF = W_actual / W_ideal_sum, dimensionless, always
  at or above 1. W_actual is the total work absorbed by all stages,
  W_ideal_sum the sum of the ideal (isentropic) stage works. Each
  stage re-compresses the reheat loss of the previous stage, so the
  actual total work exceeds the ideal sum; typical values run from
  1.01 to 1.06 and grow with the stage count.
- Stage work distribution: W_total = sum of the stage works w_k.
  Equal scheme: w_k = W_total / n for every stage. Rising scheme:
  w_k = W_total * 2*k / (n*(n+1)) for k = 1 to n, a linear ramp that
  puts about twice the first-stage work on the last stage, matching
  the rising back pressure along the flow path.
- Annulus area: A = m_dot / (rho * V_ax) in m^2, with mass flow m_dot
  in kg/s, density rho in kg/m^3, axial velocity V_ax in m/s. Density
  rises through the compressor, so for a constant axial velocity the
  annulus area shrinks toward the rear stages.
- Corrected speed: N_corr = N * sqrt(t_ref / t) in rpm, the rotor
  speed referred to the reference temperature for off-design
  matching. Standard day t_ref = 288.15 K; at t = t_ref the corrected
  speed equals the physical speed.
- Units: pressures dimensionless, work in J/kg (or J), area in m^2,
  flows in kg/s, velocities in m/s, densities in kg/m^3, speeds in
  rpm, temperatures in K.
- FAR-33 (14 CFR Part 33) sets the engine type certification context;
  it calls for demonstrating compression system operability but does
  not prescribe the matching relations above, which are common
  turbomachinery design practice.

## Workflow

1. Fix the design point: mass flow, overall pressure ratio target,
   inlet temperature, axial velocity, and density.
2. Choose the design stage pressure ratio (or a per-stage ratio
   list) and compute the stage count with
   stage_count(total_pressure_ratio, stage_pressure_ratio).
3. Compute the achieved overall pressure ratio from the stage ratio
   list with overall_pressure_ratio and confirm the product meets the
   target.
4. Distribute the total work with stage_work_distribution using the
   equal or rising scheme; prefer rising when the rear stages would
   otherwise be under-loaded at the rising back pressure.
5. Estimate the reheat factor with reheat_factor(actual_work,
   ideal_work_sum) and check it stays at or above 1.
6. Size the annulus at each station with annulus_area(mass_flow,
   axial_velocity, density), letting the local density grow along the
   flow path so the area shrinks.
7. For off-design matching, refer the rotor speed with
   corrected_speed(physical_speed, t_ref, t) before comparing with
   map data.

## Pitfalls

- Adding stage pressure ratios instead of multiplying: the overall
  pressure ratio is the product, so 6 stages at 1.45 give 9.29, not
  8.70.
- Rounding the stage count down: the count is the ceiling of the log
  ratio; 6 stages at 1.45 reach only 9.29, so a target of 10 needs 7
  stages at that loading.
- Trusting a reheat factor below 1: the actual total work can never
  sit below the ideal stage work sum, so such a value is a data
  error; the function raises ValueError instead of returning it.
- Mixing corrected and physical speed: corrected speed equals the
  physical speed only at the reference temperature; comparing raw
  speeds measured on a different day shifts the matching point.
- Passing a stage or total pressure ratio at or below 1: no
  compression happens, and the functions raise ValueError rather than
  divide by zero or return a nonsense count.
- Assuming an equal work split everywhere: rising back pressure
  unloads the rear stages of an equal-scheme machine; use the rising
  scheme or accept the matching penalty.
- Mixing units: keep everything SI (kg/s, m/s, kg/m^3, K, Pa); a
  density in kg/L or a flow in lb/s breaks the annulus area.
- Sizing the annulus with the inlet density at every station: the
  area must shrink as density grows, or the axial velocity falls and
  the rear stages stall.

## Behavior contract (gate 3)

The design and matching relations are exercised by the gate 3
contract test: scripts/test_multi_stage_compressor.py against
scripts/multi_stage_compressor.py (stdlib unittest, offline). Run:
python3 scripts/test_multi_stage_compressor.py

## Compliance

- Standards referenced, not reproduced: FAR-33 is US government work
  (public domain) and covers engine type certification, not stage
  matching methods; the pressure ratio, reheat factor, annulus, and
  work distribution relations are common turbomachinery methodology,
  summary-only 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 →