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

E1012 Tid Assessment

ASecurity

"Use when calculate total ionising dose (TID) damage for spacecraft

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

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 e1012-tid-assessment --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E1012 Tid Assessment?

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

Security grade badge for E1012 Tid Assessment
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e1012-tid-assessment/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e1012-tid-assessment)

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

Download with Pro
Files
SKILL.md
---
name: e1012-tid-assessment
description: "Use when calculate total ionising dose (TID) damage for spacecraft
  electronic components under ECSS-E-ST-10-12C §7.5: derive the applicable radiation
  damage parameters for each component category (§7.5.1), compute the accumulated
  ionising dose from orbit-specific dose rates and mission duration using an aluminium
  shielding model (§7.5.2), apply the required design margin, and compare each
  component's dose requirement against its TID limit to produce a compliant or
  non-compliant finding. Trigger: ecss, e-st-10-12c, e-st-10-system-scope,
  tid, total-ionising-dose, radiation-damage, dose-calculation, shielding, rha,
  component-assessment."
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-10-12c, e-st-10-system-scope, tid, total-ionising-dose, radiation-damage, dose-calculation, shielding, rha, component-assessment]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Space Environment — TID Assessment (space-systems/ecss/e1012-tid-assessment)

Use when the task is to calculate total ionising dose (TID) damage for
electronic components under ECSS-E-ST-10-12C §7.5 — deriving radiation
damage parameters (§7.5.1), computing the accumulated ionising dose with
shielding and margin (§7.5.2), and recording a pass/fail finding per component.

## Domain quick reference

- §7.5.1 establishes the radiation damage parameters: each component is
  grouped into a category (standard, rad-tolerant, rad-hard, rad-hardened)
  defined by its maximum TID tolerance in rad(Si). The category is the
  anchor for the dose limit comparison and is derived from the component
  manufacturer's radiation characterisation data, not assumed.
- §7.5.2 defines the ionising dose calculation: the environment model
  provides an orbit- and shielding-dependent dose rate (krad/year behind
  a specified aluminium sphere equivalent). Accumulated TID equals the dose
  rate multiplied by the mission duration; a design margin (typically 2×)
  is then applied to obtain the radiation design requirement for each
  location. The margin accounts for uncertainties in the environment model,
  shielding geometry, and dose enhancement effects.
- The assessment finds a component non-compliant when its dose design
  requirement (TID × margin) exceeds its category limit. A component is
  not automatically compliant simply because no limit was recorded — a
  missing limit is itself a finding requiring resolution before the
  assessment closes.

## Workflow

1. Identify the mission orbit and nominal aluminium shielding thickness
   at each component location. Confirm that a dose rate is available for
   that orbit–shielding pair from the environment analysis; reject
   undefined combinations before proceeding.
2. Derive the radiation damage parameters for each component: assign it
   to a category (standard / rad-tolerant / rad-hard / rad-hardened) from
   its characterisation data and record the associated TID limit in rad(Si).
   Flag any component without a characterised limit as needing resolution.
3. Compute the accumulated TID at each location: multiply the dose rate
   (krad/year) by the mission duration (years) and convert to rad.
4. Apply the design margin to the computed TID to obtain the radiation
   design requirement for each component location.
5. Compare each component's design requirement against its category TID
   limit. Record a compliant or non-compliant finding; do not carry
   forward a component with a missing limit as compliant.
6. Collect all findings per component location; the location is not TID
   compliant until every component at that location produces a compliant
   finding and no limit gaps remain.

## Pitfalls

- Applying the dose rate directly as the TID without multiplying by
  mission duration — the rate is per year, not the total accumulated dose.
- Omitting the design margin before comparing against the limit — comparing
  raw TID to the limit understates the requirement and can produce a false
  pass when the environment and geometry uncertainties are unaccounted for.
- Treating a missing TID limit as equivalent to an unlimited tolerance —
  absence of characterisation data is a gap in the damage parameter set,
  not a licence to proceed.
- Using aluminium shielding thickness as a direct proxy for dose without
  confirming the orbit–shielding lookup is valid — an interpolated or
  extrapolated dose rate outside the environment table's range propagates
  unquantified error into every downstream comparison.

## Behavior contract (gate 3)

The damage-parameter grouping, TID computation, margin application, and
pass/fail assessment logic is exercised by the gate 3 contract test:
scripts/test_e1012_tid_assessment.py against
scripts/e1012_tid_assessment_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1012_tid_assessment.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 →