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

Q6013 Class 3 Temperature Range

ASecurity

Use when a datasheet band meets an application case before a Class 3 part is baselined. Evaluate whether the rated temperature limits of a commercial EEE part cover the application conditions at the lowest assurance class of ECSS-Q-ST-60-13C clause 6.2.2.6: resolve the rated band from the temperature grade or the declared limits, widen the predicted extremes by the thermal analysis uncertainty, credit a correlated thermal model only down to its retained floor, take the cold end and the hot en...

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 q6013-class-3-temperature-range --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q6013 Class 3 Temperature Range?

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

Security grade badge for Q6013 Class 3 Temperature Range
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q6013-class-3-temperature-range/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q6013-class-3-temperature-range)

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

Download with Pro
Files
SKILL.md
---
name: q6013-class-3-temperature-range
description: "Use when a datasheet band meets an application case before a Class 3 part is baselined. Evaluate whether the rated temperature limits of a commercial EEE part cover the application conditions at the lowest assurance class of ECSS-Q-ST-60-13C clause 6.2.2.6: resolve the rated band from the temperature grade or the declared limits, widen the predicted extremes by the thermal analysis uncertainty, credit a correlated thermal model only down to its retained floor, take the cold end and the hot end apart, grade each against the thin margin this class owes, allow a bounded uprating or an approved hot-end mounting repair, and return one range verdict with the repair each short end needs. Trigger: ecss, q-st-60-13c-clause-6-2-2-6, class-three-rated-temperature-range, commercial-part-temperature-grade-band, thermal-model-correlation-credit, cold-end-hot-end-thermal-margin, hot-end-mounting-repair-credit, commercial-part-uprating-admissibility."
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, q-st-60-13-commercial-eee-component-scope, q-st-60-13c, q6013-class-3-temperature-range, class-three-rated-temperature-range, commercial-part-temperature-grade-band, thermal-model-correlation-credit, cold-end-hot-end-thermal-margin, hot-end-mounting-repair-credit, commercial-part-uprating-admissibility]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Commercial EEE Components -- Class 3 Temperature Range (space-systems/ecss/q6013-class-3-temperature-range)

Use when the task is clause 6.2.2.6 of ECSS-Q-ST-60-13C at the lowest
assurance class: a commercial part carries a rated temperature band, the
application carries an operating case, and the question is whether the
first covers the second with the margin this class owes.

## Domain quick reference

- The rated band belongs to the part type. It comes from the temperature
  grade the part is sold under, or from limits the declaration states
  outright, never from both -- two sources that disagree is the defect this
  check exists to catch, not a detail to reconcile quietly.
- The application case is not the predicted extremes. The thermal analysis
  behind those extremes carries an uncertainty, and that uncertainty widens
  the case outwards at both ends before anything is compared. Comparing a
  datasheet band against an un-widened prediction is the usual way a part
  looks covered and is not.
- This class lets a correlated thermal model buy part of that uncertainty
  back. Where the model has been correlated against a thermal balance test,
  the declared uncertainty is reduced by a fixed credit, down to a retained
  floor that is never crossed. Correlation narrows the unknown; it does not
  remove it, and a model nobody correlated keeps the whole of its declared
  figure.
- The cold end and the hot end are graded separately. They fail for different
  reasons and they are repaired in different ways: a hot end is often bought
  back by the mounting and the conduction path, a cold end almost never is.
  A single worst-case number hides which end is the problem.
- The margin owed at this class is the thinnest of the three, but it is not
  zero. An end sitting inside the rated band and short of that margin is
  still a finding, because the margin is what absorbs the drift the analysis
  did not model and the spread the manufacturer never guaranteed.
- A zero margin is short, not covered. An end that lands exactly on the rated
  limit has nothing between it and the limit.
- Two credits may move an end and neither is free. An uprating evaluation may
  extend a rated end, bounded and evidenced; an unevidenced claim earns
  nothing and is reported. An approved mounting and conduction-path repair
  may pull the hot extreme back in, bounded, and at the hot end alone -- the
  cold extreme is set by the environment the part sits in, and no mounting
  change reaches it.
- A covered range carrying either credit is not a clean one. Both are open
  actions that travel with the part into the build.

## Workflow

1. Resolve the rated band from the part declaration, rejecting a declaration
   that names a grade and explicit limits together or neither of them.
2. Reduce the declared thermal analysis uncertainty by the correlation credit
   where the model has been correlated by test, never below the retained
   floor, and keep the declared figure where it has not.
3. Widen the predicted application minimum and maximum by the resulting
   uncertainty to get the case the part actually has to survive.
4. Validate any uprating declaration, credit it only when it is evidenced and
   inside the bound, cap it when it is not, and apply the credited extension
   to the ends the claim names.
5. Validate any mounting and conduction-path repair, refuse it outright at
   the cold end, credit it only when it is approved and inside the bound, and
   pull the hot extreme in by the credited amount.
6. Compute the cold-end and hot-end margins against the effective rated
   limits, keeping the two ends apart.
7. Grade each end -- covered with margin, short of the margin, or not covered
   at all -- rank the short ends by how far each is from the required margin,
   and name the verdict, carrying every credit and finding with it.

## Pitfalls

- Comparing the datasheet band against the predicted extremes and skipping
  the analysis uncertainty, so a part that is marginal reads as covered.
- Taking the correlation credit on a model nobody correlated by test, or
  taking it past the retained floor. The floor is there because correlation
  narrows the unknown rather than closing it.
- Collapsing the two ends into one worst-case margin, which hides the end
  that drives the repair.
- Claiming a mounting repair at the cold end. A conduction path reaches a hot
  part; the cold extreme belongs to the environment and is repaired by the
  part selection, the duty cycle or a heater, never by the mounting.
- Reading a zero margin as a pass because the case is technically inside the
  band. The margin requirement is the point of the check, thin though it is
  at this class.
- Taking an uprating claim on the strength of the number alone. Without the
  evaluation behind it the extension is an assertion, not evidence, and
  letting it run as far as the analysis needs ignores the bound the physics
  imposes.
- Treating a covered range that carries a credit as clean. Both credits are
  open actions and have to travel with the part.
- Adjusting the rated band to suit the application rather than adjusting the
  mounting, the duty cycle or the part selection.

## Behavior contract (gate 3)

The grade band resolution, correlation credit and retained floor, uncertainty
widening, per-end margin, end disposition, uprating admissibility and bound,
hot-end mounting repair credit, shortfall ranking and range verdict are
exercised by the gate 3 contract test:
scripts/test_q6013_class_3_temperature_range.py against
scripts/q6013_class_3_temperature_range_logic.py (stdlib unittest, offline).
Run: python3 scripts/test_q6013_class_3_temperature_range.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 →