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

Q60 Class 3 Stock Relifing

ASecurity

Determine which time-expired Class 3 EEE stock lots can have their storage validity restored under clause 6.3.10 of ECSS-Q-ST-60C: read the date code to fix the manufacture point, measure elapsed storage against the period the lot was issued, compute the decaying period each further relife cycle earns, trim that grant to the total life left from manufacture, assemble the evidence the package seal and moisture level owe, separate absent evidence from failed evidence, and spend a limited relife...

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 q60-class-3-stock-relifing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q60 Class 3 Stock Relifing?

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

Security grade badge for Q60 Class 3 Stock Relifing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q60-class-3-stock-relifing/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q60-class-3-stock-relifing)

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

Download with Pro
Files
SKILL.md
---
name: q60-class-3-stock-relifing
description: "Determine which time-expired Class 3 EEE stock lots can have their storage validity restored under clause 6.3.10 of ECSS-Q-ST-60C: read the date code to fix the manufacture point, measure elapsed storage against the period the lot was issued, compute the decaying period each further relife cycle earns, trim that grant to the total life left from manufacture, assemble the evidence the package seal and moisture level owe, separate absent evidence from failed evidence, and spend a limited relife test capacity where it releases the most build demand. Use when an expired store has to become a relife campaign rather than a scrap list. Trigger: ecss, q-st-60c-clause-6-3-10, q60-c3-expired-stock-relife-campaign, q60-c3-relife-cycle-decay-grant, q60-c3-total-life-headroom-cap, q60-c3-owed-relife-evidence-set, q60-c3-relife-capacity-allocation."
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-60c-eee-components-scope, q-st-60c-clause-6-3-10, q60-class-3-stock-relifing, q60-c3-expired-stock-relife-campaign, q60-c3-relife-cycle-decay-grant, q60-c3-total-life-headroom-cap, q60-c3-owed-relife-evidence-set, q60-c3-relife-capacity-allocation]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS EEE Components — Class 3 Expired Stock Relifing (space-systems/ecss/q60-class-3-stock-relifing)

Use when the task is clause 6.3.10 of ECSS-Q-ST-60C: Class 3 parts were bought,
accepted and put away, the build slipped, and the storage period those lots were
issued has run out. The leaf turns a shelf of expired lots into a campaign —
which lots earn a renewed period, what each owes before it gets one, which are
finished, and which of the survivors the available test capacity should reach.

## Domain quick reference

- Relifing renews the evidence behind a lot, not the parts. Nothing about the
  parts changed on the day the period lapsed; what lapsed is the currency of the
  acceptance evidence, and restoring validity means taking that evidence again.
- The date code is the anchor, not the receipt. The receipt says when the lot
  reached this store; the date code says when the part was made, and the total
  life a part is entitled to runs from the second. A lot that changed hands
  twice can be inside its storage period and out of its life at the same time.
- A renewed period is smaller than the one before it. Treating each relife as a
  fresh full period is how a lot gets kept alive indefinitely on paper, so the
  grant decays with every cycle already spent and stops when the allowance is.
- Two ceilings apply and the lower one wins. The cycle-decay grant is what the
  operation earns; the life headroom from the date code is what the part has
  left. Granting the first without trimming it to the second relifes a lot past
  the total life it was ever entitled to.
- The evidence owed depends on how the lot was actually packaged. A sealed dry
  pack owes the base set; an opened one on a moisture-sensitive part reopens the
  bake; an uncontrolled bag reopens electrical re-verification as well, because
  nothing about the store is known.
- Absent evidence and failed evidence are different answers. Absent means the
  work has not been done and the grant is conditional on doing it; failed means
  the work was done and the lot did not pass, which is a disposition.
- A failed solderability sample is recoverable and the rest are not. Surfaces
  can be re-tinned and re-screened; a leaking package or a part that no longer
  meets its electrical limits at ambient has no route back.
- Capacity is the real constraint on a stock of any size. Ordering the campaign
  by lot size spends the whole capacity on the biggest lot; ordering it by the
  build demand each test slot releases spends it where the programme feels it.

## Workflow

1. Validate every stored lot record and reject a stock that names one lot twice.
2. Read each date code to a manufacture week and take the life headroom left
   against the total life the part is entitled to.
3. Compare elapsed storage with the issued period, treating a lot sitting
   exactly on its period as still inside it and leaving it alone.
4. Compute the decaying grant the next cycle earns, then trim it to the headroom.
5. Assemble the owed evidence from the package seal, the moisture level and
   whether the package is hermetic, and split the records into absent and failed.
6. Decide a disposition per lot, letting a failure outrank a shortfall and a
   spent allowance outrank a clean evidence file.
7. Order the workable lots by demand released per test slot, spend the capacity
   down that order, and report what the campaign covers and what it defers.

## Pitfalls

- Relifing from the receipt date. The storage period starts at acceptance but
  the total life starts at manufacture, and a lot bought from stock elsewhere
  can have most of its life already gone before it arrived.
- Granting a full fresh period every cycle. The arithmetic looks generous and
  the lot never dies; the standard's intent is that each renewal buys less.
- Ignoring the life headroom because the grant looked modest. The trim is what
  stops a third relife from carrying a part past the life it ever had.
- Reading an owed test with no record as a pass. An empty row is the commonest
  cause of a lot going back to stores with evidence nobody actually took.
- Sending a failed solderability sample to scrap. It is the one failure with a
  route back, and scrapping it throws away parts that a re-tin would recover.
- Treating an uncontrolled bag as an opened dry pack. The bag reopens electrical
  re-verification too, because nothing about where it sat is known.
- Ordering the campaign by lot size. The largest lot is frequently the one with
  the least demand behind it, and it will eat a whole test capacity unnoticed.

## Behavior contract (gate 3)

The date-code parsing, life-headroom arithmetic, storage-period comparison,
cycle-decay grant, headroom trim, owed-evidence assembly, absent-versus-failed
split, per-lot disposition, priority ordering and capacity allocation are
exercised by the gate 3 contract test:
scripts/test_q60_class_3_stock_relifing.py against
scripts/q60_class_3_stock_relifing_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_q60_class_3_stock_relifing.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 →