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

E31 High Temperature Range Tps Requirements

ASecurity

Evaluate a thermal-protection item running above four hundred and seventy kelvin against the high-temperature design constraints of ECSS-E-ST-31 clause 4.2.2 and its thermal-protection annex: compare the uncertainty-inflated peak against the material maximum use temperature, spend the recession allowance over the exposure and check what thickness is left, carry the remaining thickness into a bondline temperature the substrate can survive, and walk the surface optical properties out over the r...

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

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 e31-high-temperature-range-tps-requirements --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E31 High Temperature Range Tps Requirements?

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

Security grade badge for E31 High Temperature Range Tps Requirements
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e31-high-temperature-range-tps-requirements/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e31-high-temperature-range-tps-requirements)

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

Download with Pro
Files
SKILL.md
---
name: e31-high-temperature-range-tps-requirements
description: "Evaluate a thermal-protection item running above four hundred and seventy kelvin against the high-temperature design constraints of ECSS-E-ST-31 clause 4.2.2 and its thermal-protection annex: compare the uncertainty-inflated peak against the material maximum use temperature, spend the recession allowance over the exposure and check what thickness is left, carry the remaining thickness into a bondline temperature the substrate can survive, and walk the surface optical properties out over the reuse cycles they are qualified for. Use when an ablator, tile or hot structure has been grouped into the high-temperature range and its sizing has to be defended. Trigger: ecss, e-st-31, high-temperature-tcs-design, thermal-protection-item-sizing, tps-recession-allowance, tps-bondline-temperature, tps-reuse-cycle-degradation, tps-maximum-use-temperature."
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-31-thermal-control-scope, e31-high-temperature-range-tps-requirements, high-temperature-tcs-design, thermal-protection-item-sizing, tps-recession-allowance, tps-bondline-temperature, tps-reuse-cycle-degradation]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Thermal Control — High-Temperature Range and Thermal Protection (space-systems/ecss/e31-high-temperature-range-tps-requirements)

Use when the task is the clause 4.2.2 step of ECSS-E-ST-31 and its
thermal-protection annex: an item has been placed in the high-temperature
range, and the engineering requirements on the protection it carries — how
much of it survives the exposure, what the structure behind it sees, and how
many times it can do that — have to be worked out.

## Domain quick reference

- The number the material is compared against is the inflated peak, not the
  predicted one. A prediction and its uncertainty both belong on the hot side
  before the maximum use temperature is consulted, and the maximum use
  temperature itself is a property of the material and its environment, not a
  single catalogue figure to be reused across atmospheres.
- Thermal protection is consumed. An ablator recedes over the exposure, and
  the thickness that matters afterwards is what is left, not what was
  installed. The sizing question is whether the residual thickness still
  meets its requirement once the recession has been spent.
- The residual thickness is also what insulates. Recession and bondline
  temperature are therefore not two independent checks: the thickness the
  bondline sees is the end-of-exposure thickness, and computing the bondline
  on the installed thickness understates it in exactly the case that matters.
- The bondline, not the surface, is usually the limiting item. Adhesives and
  composite substrates fail hundreds of kelvin below the surface material, so
  a protection item that comfortably survives its own peak can still debond.
- Reuse degrades the surface. Emissivity falls and catalycity rises with
  cycles, and a surface qualified for a number of cycles has a declared
  end-of-life optical property that the last flight has to close on, not the
  beginning-of-life value the first analysis used.
- Falling emissivity is a feedback, not a bookkeeping entry. A surface that
  radiates less runs hotter, which is why the end-of-life property is carried
  into the peak check rather than reported next to it.

## Workflow

1. Validate the item and admit only a peak that actually reaches into the
   high-temperature range. An item below the boundary belongs to the
   conventional rules and is refused here rather than graded by the wrong
   rule set.
2. Inflate the predicted peak by its uncertainty and compare with the
   material maximum use temperature, recording the margin.
3. Spend the recession: multiply the recession rate by the exposure duration,
   subtract from the installed thickness, and compare the residual with the
   required minimum residual thickness.
4. Refuse a recession that consumes the whole item — a negative residual is
   not a thin item, it is a burn-through, and it is reported as one.
5. Compute the bondline temperature from the residual thickness, the heat
   flux and the through-thickness conductivity, and compare it with the
   substrate limit.
6. Walk the surface emissivity out over the required cycles at the declared
   degradation per cycle, and compare the end-of-life value with its floor.
7. Compare the required cycles with the qualified cycles, and treat a
   shortfall as a finding in its own right rather than as a consequence of
   the emissivity walk.
8. Report a per-constraint verdict with the margins, so one failing check
   does not hide the state of the others.

## Pitfalls

- Comparing the raw predicted peak with the maximum use temperature. The
  uncertainty belongs on the prediction first, and on the hot side it is the
  whole margin for a marginal item.
- Computing the bondline on the installed thickness. The insulating layer is
  thinner at the end of the exposure, which is the same moment the flux has
  been integrated the longest.
- Declaring a protection item adequate on its surface margin alone. The
  adhesive limit is the one that is usually hit, and it is hundreds of kelvin
  lower.
- Carrying beginning-of-life emissivity into a reuse case. A degraded surface
  radiates less and runs hotter, so the last qualified flight, not the first,
  is the sizing case.
- Reading a negative residual thickness as a very thin item. It is a
  burn-through, and arithmetic that continues past it produces a bondline
  temperature with no physical meaning.
- Treating the maximum use temperature as environment independent. The same
  material has different usable limits in an oxidising and an inert
  atmosphere, and the wrong figure invalidates the whole chain.

## Behavior contract (gate 3)

The high-temperature admission check, uncertainty-inflated peak comparison,
recession allowance and residual thickness, burn-through refusal, bondline
temperature from the residual thickness, emissivity walk over the reuse
cycles and the per-constraint verdict are exercised by the gate 3 contract
test: scripts/test_e31_high_temperature_range_tps_requirements.py against
scripts/e31_high_temperature_range_tps_requirements_logic.py (stdlib
unittest, offline). Run:
python3 scripts/test_e31_high_temperature_range_tps_requirements.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 →