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 Buy Off Source Inspection

ASecurity

Use when a session held at the supplier has to become a ship-or-hold decision with a quantity attached. Determine whether a witnessed source buy-off releases a Class 1 EEE lot under ECSS-Q-ST-60C clause 4.3.6: count the whole days of advance notice the procuring entity was given, decide from who was actually in the room whether the session was witnessed, waived under a referenced waiver or simply unwitnessed, check that the activities it sits on top of completed no later than the session itse...

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 q60-class-1-buy-off-source-inspection --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q60 Class 1 Buy Off Source Inspection?

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

Security grade badge for Q60 Class 1 Buy Off Source Inspection
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q60-class-1-buy-off-source-inspection/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q60-class-1-buy-off-source-inspection)

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

Download with Pro
Files
SKILL.md
---
name: q60-class-1-buy-off-source-inspection
description: "Use when a session held at the supplier has to become a ship-or-hold decision with a quantity attached. Determine whether a witnessed source buy-off releases a Class 1 EEE lot under ECSS-Q-ST-60C clause 4.3.6: count the whole days of advance notice the procuring entity was given, decide from who was actually in the room whether the session was witnessed, waived under a referenced waiver or simply unwitnessed, check that the activities it sits on top of completed no later than the session itself, and cap the release at the pieces actually presented so unseen pieces stay at the manufacturer. Trigger: ecss, q-st-60c-clause-4-3-6, class-1-source-buy-off, buy-off-witness-attendance, witnessing-waiver-reference, buy-off-notice-period, presented-quantity-release-cap."
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-class-1-scope, q60-class-1-buy-off-source-inspection, class-1-source-buy-off, buy-off-witness-attendance, witnessing-waiver-reference, buy-off-notice-period, presented-quantity-release-cap]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Class 1 EEE Parts -- Witnessed Source Buy-Off (space-systems/ecss/q60-class-1-buy-off-source-inspection)

Use when the task is the clause 4.3.6 buy-off of ECSS-Q-ST-60C: a Class 1 lot
is finished at the manufacturer, a final acceptance session has been held in
front of a witness, and the question is whether the parts leave the premises
and how many of them do.

## Domain quick reference

- A buy-off is a session, not a signature. It has a date, a room, an
  attendance list and a quantity in front of the witness, and each of those
  four can fail independently of the others.
- Notice is what makes attendance possible. The call is counted in whole days
  from the day it was issued to the day of the session; a session called at
  short notice is not witnessed by a representative who could not get there.
- Witnessing is a question about roles, not headcount. A room full of the
  manufacturer's own quality staff is an unwitnessed session. A written waiver
  carrying its own reference and reason converts that into an admissible
  release; a waiver with no reference does not exist for this purpose.
- The buy-off sits on top of the activities that produced its evidence. One
  finishing after the session is out of sequence whatever the session found,
  because the evidence was not there on the day.
- The release is bounded by what was presented. Pieces the witness never saw
  are withheld rather than carried by the ones that were seen, so a short
  presentation gives a partial release and names the withheld balance.

## Workflow

1. Count the notice given from the call day to the session day and compare it
   with the notice period the contract asks for, refusing a session dated
   before its own call.
2. Read the attendance list for a role entitled to witness on behalf of the
   procuring entity, matching the role without regard to letter case.
3. Where nobody entitled attended, look for a waiver and demand both its
   reference and its reason before admitting it; otherwise the session stands
   unwitnessed.
4. Test every prerequisite activity for completion no later than the session
   day, and treat a required activity absent from the record as a finding of
   its own rather than a silent pass.
5. Cap the requested release at the presented quantity and report the withheld
   balance as a number, not as a note.
6. Release only when the session was admissible, in sequence, properly called
   and carrying no open major nonconformance; otherwise hold at the
   manufacturer and name every gate that failed.

## Pitfalls

- Treating attendance as witnessing. The manufacturer's own staff being in the
  room is the normal case and is not what the clause asks for.
- Admitting an unreferenced waiver. A waiver without a reference cannot be
  traced back to who granted it or why, so it cannot carry a release.
- Reporting only the first failing gate. Short notice, an out-of-sequence
  prerequisite and an open major nonconformance are three separate problems
  and the supplier needs all three, not the earliest one.
- Releasing the offered quantity because the session went well. The release
  follows the pieces presented; the balance stays where it is.
- Accepting a prerequisite that completed the week after the session. The
  session cannot have accepted evidence that did not yet exist.

## Behavior contract (gate 3)

The notice counting, witness and waiver states, prerequisite sequencing,
presented-quantity cap and the ship-or-hold disposition are exercised by the
gate 3 contract test:
scripts/test_q60_class_1_buy_off_source_inspection.py against
scripts/q60_class_1_buy_off_source_inspection_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_q60_class_1_buy_off_source_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 →