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 3 Preferred Sources

ASecurity

Use when a Class 3 buy has more than one offer and the preferred-source order has to be shown. Determine which commercial manufacturer or distributor a Class 3 procurement should buy a part from under ECSS-Q-ST-60-13C clause 6.2.2.3: score each candidate source on its supply tier, the chain of traceability back to the maker, its quality-system evidence, date-code age, single-lot delivery and counterfeit screening, order them, and state the conditions a non-preferred source has to meet. Trigge...

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-3-preferred-sources --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q6013 Class 3 Preferred Sources?

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

Security grade badge for Q6013 Class 3 Preferred Sources
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q6013-class-3-preferred-sources/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q6013-class-3-preferred-sources)

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

Download with Pro
Files
SKILL.md
---
name: q6013-class-3-preferred-sources
description: "Use when a Class 3 buy has more than one offer and the preferred-source order has to be shown. Determine which commercial manufacturer or distributor a Class 3 procurement should buy a part from under ECSS-Q-ST-60-13C clause 6.2.2.3: score each candidate source on its supply tier, the chain of traceability back to the maker, its quality-system evidence, date-code age, single-lot delivery and counterfeit screening, order them, and state the conditions a non-preferred source has to meet. Trigger: ecss, q-st-60-13-commercial-eee-scope, class-3-preferred-source-order, franchised-distributor-preference, open-market-broker-last-resort, commercial-part-supply-chain-traceability, commercial-part-counterfeit-screening, commercial-part-date-code-age-limit."
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-3-preferred-sources, class-3-preferred-source-order, franchised-distributor-preference, open-market-broker-last-resort, commercial-part-supply-chain-traceability, commercial-part-counterfeit-screening, commercial-part-date-code-age-limit]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Commercial EEE — Class 3 Preferred Sources (space-systems/ecss/q6013-class-3-preferred-sources)

Use when the task is the sourcing preference of ECSS-Q-ST-60-13C
clause 6.2.2.3 -- choosing which of several offered commercial
manufacturers or distributors a Class 3 part is actually bought from,
and what a source further down the order still has to bring.

## Domain quick reference

- A Class 3 part carries the least assurance of any category, so most
  of the confidence a project has in it comes from where it was bought
  rather than from anything done to it afterwards. That is why the
  clause sets an order over sources at all.
- The order runs outwards from the maker: the maker itself, then a
  franchised distributor drawing stock from the maker, then a
  subcontractor building to the maker's flow, then an independent
  distributor, and last an open-market broker. Each step adds a
  handling link that can substitute, relabel or mix lots.
- Distance from the maker is not the whole answer, only the starting
  point. A franchised distributor with an unbroken chain, a certified
  quality system, a single lot and a young date code can beat a
  nearer source that brings none of those, and the scoring has to let
  it.
- Two conditions are a floor rather than a deduction. A source with no
  traceability at all cannot tie the delivered population to a line,
  and an open-market broker with no counterfeit screening is the
  textbook counterfeit route. Neither is admissible at any score.
- Date-code age matters because a commercial part was never stored for
  a space programme. Beyond the limit the project sets, solderability
  is the first thing to go, and the condition is a verification rather
  than a rejection.
- The buy has to show it worked down the order. The useful output is
  therefore the ordered list with the preferred source named, the
  margin over the runner-up, and the conditions each other offer
  carries -- not a single winner with no working shown.

## Workflow

1. Declare every offer: source tier, traceability chain, quality
   system, single-lot delivery, counterfeit screening, and date-code
   age. Reject an incompletely declared offer rather than scoring the
   gaps as zero silently.
2. Set the date-code age limit the project works to. It is a project
   parameter, not a constant, and it belongs in the record.
3. Score each offer in whole points -- a tier base plus the evidence it
   brings -- so the ordering is exact and reproducible rather than a
   float comparison between near-equal offers.
4. Apply the two floors before the ordering matters: no traceability,
   or open-market supply with no counterfeit screening, is not
   admissible whatever else the offer carries.
5. Order the offers by points, breaking a tie towards the tier nearer
   the maker and then by name, and take the highest-scoring admissible
   one as preferred.
6. Report the margin over the runner-up and the conditions every other
   offer would have to meet, so a later change of supply can be judged
   against the same scale.

## Pitfalls

- Buying on tier alone. The tier is the starting point, and a nearer
  source with no chain, no quality system and a five-year-old date
  code is worse than a franchised one that brings all three.
- Treating the counterfeit screen as a deduction on a broker offer. For
  open-market supply it is the floor: without it the offer is not in
  the comparison at all.
- Scoring a missing declaration as zero. A gap in the offer is an
  unanswered question about the supply chain, and folding it into the
  arithmetic hides it behind a number.
- Reporting only the winner. The clause asks for the order to be
  worked down, so the runner-up, the margin and the conditions are the
  evidence; the winning name alone is a conclusion with no working.
- Ordering by a normalized float. Two offers that differ by one point
  can compare equal after division, so the ordering is done on the
  whole-point total and the normalized value is reported, never used
  to decide.
- Comparing a date-code age with its limit by bare arithmetic. The age
  is a difference of two dates in months while the limit is a single
  declared number, so an age built to land exactly on the limit can sit
  a few units in the last place above it; the comparison absorbs that
  representation error while the limit stays untouched.

## Behavior contract (gate 3)

The candidate validation, the tier ordering, the whole-point scoring of
tier, traceability chain, quality system, single-lot delivery,
counterfeit screening and date-code age, the two admissibility floors,
the ordering with its tie break, and the preferred-source, runner-up
and margin reporting are exercised by the gate 3 contract test:
scripts/test_q6013_class_3_preferred_sources.py against
scripts/q6013_class_3_preferred_sources_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_q6013_class_3_preferred_sources.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 →