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 1 Constructional Analysis

ASecurity

Use when cross-section and internal-inspection results decide whether a part's construction is acceptable. Evaluate a constructional analysis carried out on Class 1 evaluation samples under ECSS-Q-ST-60C clause 4.2.3.3: size the sample set from the part family and the declared diffusion and assembly lots, check that the cross-sectioned samples actually span the lots and date codes they claim to speak for, grade every internal inspection step and treat a skipped mandatory one as incomplete rat...

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

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-1-constructional-analysis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q60 Class 1 Constructional Analysis?

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

Security grade badge for Q60 Class 1 Constructional Analysis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q60-class-1-constructional-analysis/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q60-class-1-constructional-analysis)

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

Download with Pro
Files
SKILL.md
---
name: q60-class-1-constructional-analysis
description: "Use when cross-section and internal-inspection results decide whether a part's construction is acceptable. Evaluate a constructional analysis carried out on Class 1 evaluation samples under ECSS-Q-ST-60C clause 4.2.3.3: size the sample set from the part family and the declared diffusion and assembly lots, check that the cross-sectioned samples actually span the lots and date codes they claim to speak for, grade every internal inspection step and treat a skipped mandatory one as incomplete rather than merely weaker, group each observed anomaly by what it touches and how widely it appears, and return the conformance index with one verdict. Trigger: ecss, q-st-60c, class-1-constructional-analysis, evaluation-sample-representativeness, evaluation-metallographic-cross-section, class-1-internal-visual-inspection, construction-anomaly-severity, class-1-construction-verdict."
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-eee-scope, q-st-60c, q60-class-1-constructional-analysis, evaluation-sample-representativeness, evaluation-metallographic-cross-section, class-1-internal-visual-inspection, construction-anomaly-severity, class-1-construction-verdict]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS EEE Components — Class 1 Constructional Analysis (space-systems/ecss/q60-class-1-constructional-analysis)

Use when the task is clause 4.2.3.3 of ECSS-Q-ST-60C: the cross-sectioning and
internal inspection of representative samples inside a Class 1 evaluation —
the part of the campaign that looks at how the device is actually built rather
than at how it performs.

## Domain quick reference

- The analysis is destructive, so the sample set is the whole argument. Every
  sample consumed is a sample nobody can re-inspect, and a conclusion drawn
  from a set that never covered a declared lot is a conclusion about the
  samples rather than about the part.
- Sample size comes from two directions at once: a floor for the part family,
  and one sample for each declared diffusion lot and each declared assembly
  lot. The larger of the two governs, so a family floor of two does not cover
  five diffusion lots.
- Representativeness is a separate question from count. A set can be the right
  size and still leave a declared date code unrepresented, and the analysis
  then has nothing to say about the material shipped under it.
- Four steps are what the analysis exists for: the internal visual inspection,
  the metallographic cross-section, the die-attach examination and the
  interconnect examination. Skipping one makes the analysis incomplete, not
  merely weaker, because no other step answers the question it answers.
- An anomaly is grouped by what it touches and how widely it appears, never by
  how bad it looked down the microscope. Construction outside what the
  manufacturer declared is critical on a single sample. An interconnect
  integrity anomaly is critical once it spans the set and major below that.
  Workmanship on a minority of samples is minor.
- The conformance index ranks what is outstanding. A critical anomaly or a
  missing mandatory step decides the outcome on its own, at any index.

## Workflow

1. Name the part family and collect the declared diffusion lots, assembly lots
   and date codes the analysis is meant to speak for.
2. Validate the sample set: a sample identifier appears once, and each sample
   names the diffusion lot, assembly lot and date code it came from.
3. Compute the required sample count from the family floor and the declared
   lots, and compare it with the set actually sectioned.
4. Test coverage separately, naming every declared lot and date code no sample
   represents. Each one is a separate gap in the argument.
5. Grade every inspection step against the full step set, so a step nobody
   mentioned is graded as not performed, and mark the mandatory ones missing.
6. Group each observed anomaly into its severity category from the
   construction it touches and the share of samples it appears on, absorbing
   the lot-wide comparison with a named tolerance.
7. Take the weighted credit over the total weight as the conformance index and
   name the verdict — incomplete while the set or the mandatory steps are
   short, not acceptable on a critical anomaly or a low index, acceptable with
   open actions when findings remain, acceptable only when none do.

## Pitfalls

- Meeting the family floor and calling the set representative. Two samples out
  of five diffusion lots is the right count for the wrong question.
- Sectioning several samples from the convenient lot because they were the
  ones on the shelf. The set has to span the declared material, and a set
  drawn from one lot says nothing about the others.
- Grading an anomaly by how alarming the photograph is. Severity comes from
  what the anomaly touches and how far it spreads; a faint feature present on
  every sample is a construction feature, and a dramatic one on a single
  sample may be handling.
- Reading a construction that differs from the manufacturer's declaration as a
  minor documentation issue. It means the delivered article is not the article
  described, which is the failure the analysis exists to catch.
- Letting a high conformance index carry an analysis that never ran the
  cross-section. The index averages; the mandatory steps do not.
- Treating a date code gap as covered because the diffusion lot was sampled.
  They are separate declarations and each is reported on its own.
- Re-using an earlier analysis on a part that has since changed assembly site
  or lot. The construction is exactly what moves when the line moves.

## Behavior contract (gate 3)

The sample sizing, coverage test, inspection-step grading, mandatory-step
rule, anomaly severity grouping, conformance index and analysis verdict are
exercised by the gate 3 contract test:
scripts/test_q60_class_1_constructional_analysis.py against
scripts/q60_class_1_constructional_analysis_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_q60_class_1_constructional_analysis.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 →