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 1 Incoming Inspection

ASecurity

Use when a delivery has to become a receipt disposition. Determine whether a received delivery of a highest-assurance commercial part goes into bonded store or into quarantine under ECSS-Q-ST-60-13C clause 4.3.7: reconcile part number, date code and quantity against the purchase order, size the external visual sample from the received quantity by an exact integer square-root plan, judge the defects against the accept number, read the bag seal, the humidity indicator card and the elapsed floor...

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 q6013-class-1-incoming-inspection --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q6013 Class 1 Incoming Inspection?

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

Security grade badge for Q6013 Class 1 Incoming Inspection
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q6013-class-1-incoming-inspection/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q6013-class-1-incoming-inspection)

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

Download with Pro
Files
SKILL.md
---
name: q6013-class-1-incoming-inspection
description: "Use when a delivery has to become a receipt disposition. Determine whether a received delivery of a highest-assurance commercial part goes into bonded store or into quarantine under ECSS-Q-ST-60-13C clause 4.3.7: reconcile part number, date code and quantity against the purchase order, size the external visual sample from the received quantity by an exact integer square-root plan, judge the defects against the accept number, read the bag seal, the humidity indicator card and the elapsed floor-life exposure of the declared moisture sensitivity level, then name every reason a delivery is held. Trigger: ecss, q-st-60-13c-clause-4-3-7, commercial-eee-incoming-inspection, purchase-order-reconciliation, incoming-visual-sample-size, dry-pack-humidity-indicator, msl-floor-life-exposure, receipt-quarantine-disposition."
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-scope, q6013-class-1-incoming-inspection, commercial-eee-incoming-inspection, purchase-order-reconciliation, incoming-visual-sample-size, dry-pack-humidity-indicator, msl-floor-life-exposure, receipt-quarantine-disposition]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Commercial EEE Parts -- Incoming Inspection on Receipt (space-systems/ecss/q6013-class-1-incoming-inspection)

Use when the task is the clause 4.3.7 receiving inspection of
ECSS-Q-ST-60-13C: a delivery of commercial parts of the highest
assurance category has arrived, and the question is whether it is
released into bonded store or quarantined at the dock.

## Domain quick reference

- Incoming inspection is the first check the receiving organisation
  performs itself rather than reads about. Everything before it -- the
  lot acceptance tests, the source buy-off -- was carried out by or at
  the supplier, so this is where an independent look at the actual boxes
  first happens.
- Reconciliation is three separate comparisons, not one. The part number
  catches a substitution, the date code catches a lot swap and the
  quantity catches a short or over shipment; a delivery can be correct
  on two of them and wrong on the third.
- The external visual sample has to be reproducible. A square-root plan
  computed in integer arithmetic gives the same sample for the same
  received quantity on every machine that runs it, raised to a declared
  floor for small lots, limited by a declared cap for large ones, and
  never larger than the lot itself.
- Dry-pack integrity is three readings that answer one question. The bag
  seal says whether the barrier held, the humidity indicator card says
  what the inside of the bag saw, and the elapsed factory-floor exposure
  against the floor life of the declared moisture sensitivity level says
  how much of the allowance the parts have already spent. Level 1 needs
  none of it; level 6 has no floor life at all.
- The documents travel with the parts or they are a finding. A
  certificate of conformity promised to follow by email is not a
  certificate of conformity on receipt, and the lot is held until it
  arrives.
- A held delivery gets every reason at once. The dock returns one
  disposition, and a supplier who is told about the seal but not about
  the missing screening data ships the same gap again.

## Workflow

1. Reconcile the part number, the date code and the quantity separately
   against the purchase order, keeping shortfall and overage as distinct
   numbers rather than a signed difference.
2. Size the external visual sample from the received quantity with the
   exact integer square-root plan, applying the declared floor and cap
   and clamping to the lot.
3. Judge the visual defects found against the sample's accept number;
   accept-on-zero is the default, and a higher accept number is declared
   rather than assumed.
4. Read the moisture barrier: seal intact or not, humidity indicator
   against its limit with an exact reading on the limit admissible, and
   exposure against the floor life of the declared level.
5. List the required delivery documents absent or marked not-received.
6. Release to bonded store only when nothing was found; otherwise
   quarantine and report every finding together with the sample size,
   the humidity margin and the floor-life hours remaining.

## Pitfalls

- Reconciling on the part number alone. The right part in the wrong date
  code is a different lot with different test evidence behind it, and
  the date-code traceability of a commercial part is the whole reason
  the highest assurance category tracks it.
- Sizing the visual sample from the ordered quantity. The sample is
  drawn from what actually arrived, so a short delivery is inspected as
  the smaller lot it is.
- Computing the sample with a floating-point square root. A lot size
  that is an exact square can round either way across platforms; integer
  arithmetic makes the sample reproducible and auditable.
- Reading the humidity card without the exposure clock. A card still
  inside its limit on a lot that has already spent its floor life is a
  pass on one question and silence on another.
- Quarantining on the first finding and stopping. The receiving report
  is the supplier's feedback loop; a partial list produces a partial
  correction and the same delivery again.

## Behavior contract (gate 3)

The purchase-order reconciliation, integer square-root sample sizing,
visual accept-number verdict, humidity and floor-life readings, document
check and the overall release-or-quarantine disposition are exercised by
the gate 3 contract test:
scripts/test_q6013_class_1_incoming_inspection.py against
scripts/q6013_class_1_incoming_inspection_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_q6013_class_1_incoming_inspection.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 →