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

Q6005 Passive Chip Procurement

ASecurity

Evaluate the purchase of a bare passive chip element under ECSS-Q-ST-60-05C clause 8.2: resolve the order line to a chip resistor, capacitor or inductor, merge the type-specific ordering data set with the baseline every bare chip carries, name what the line failed to declare, check the termination metallization against the attachment method the assembly will use, form the applied-to-rated stress ratio against the derating limit that type carries, confirm one production lot per delivery, and r...

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 q6005-passive-chip-procurement --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q6005 Passive Chip Procurement?

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

Security grade badge for Q6005 Passive Chip Procurement
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q6005-passive-chip-procurement/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q6005-passive-chip-procurement)

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

Download with Pro
Files
SKILL.md
---
name: q6005-passive-chip-procurement
description: "Evaluate the purchase of a bare passive chip element under ECSS-Q-ST-60-05C clause 8.2: resolve the order line to a chip resistor, capacitor or inductor, merge the type-specific ordering data set with the baseline every bare chip carries, name what the line failed to declare, check the termination metallization against the attachment method the assembly will use, form the applied-to-rated stress ratio against the derating limit that type carries, confirm one production lot per delivery, and return release, hold or reject with the governing reason. Use when an order line for bare chip resistors, capacitors or inductors is graded before release. Trigger: ecss, q-st-60-05c, passive-chip-element-procurement, chip-element-ordering-data-items, chip-termination-attach-compatibility, passive-chip-derating-ratio, single-lot-delivery-traceability."
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-05-hybrid-procurement-scope, q6005-passive-chip-procurement, passive-chip-element-procurement, chip-element-ordering-data-items, chip-termination-attach-compatibility, passive-chip-derating-ratio, single-lot-delivery-traceability]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Hybrid Procurement — Passive Chip Elements (space-systems/ecss/q6005-passive-chip-procurement)

Use when the task is the purchase of ECSS-Q-ST-60-05C clause 8.2 — the
buying rules that attach to resistors, capacitors and inductors supplied as
bare, unencapsulated chips for hybrid assembly, where what the order line
has to say changes with the element type and the chip arrives with no
package to hide behind.

## Domain quick reference

- A bare chip is bought on paper, not on a part number. The package that
  would otherwise carry a marking, a lead finish and a body is absent, so
  every property the assembly depends on has to appear as a declared
  ordering data item or it is simply not known when the chip arrives.
- The data set is two layers. One layer is carried by every bare passive
  chip whatever it does: the manufacturer part identification, the
  procurement specification it is bought against, the lot identification,
  the termination metallization, and the quality level. The second layer is
  the element's own — a resistor owes its resistive film system, tolerance
  and trim method; a capacitor owes its dielectric category, tolerance and
  a destructive physical analysis; an inductor owes its core material,
  tolerance and self-resonant frequency.
- Termination metallization is not a preference, it is half of a
  metallurgical pair. Gold terminations dissolve into tin-bearing solder
  and leave an embrittled joint; a silver-bearing termination is not a
  gold-wire bonding surface; a tin finish is a solder termination and not
  a bonding one. The finish alone is not a finding and neither is the
  attachment method alone — the pair is.
- The derating limit travels with the element type, not with the order.
  Power in a chip resistor, voltage on a chip capacitor and current through
  a chip inductor are each graded as a fraction of the rated quantity, and
  a chip that would be comfortable as one type can be over-stressed as
  another at the same declared numbers.
- One delivery, one production lot. A split delivery is not a paperwork
  irritation: it breaks the link between the lot data supplied and the
  elements in the tray, and nothing downstream of that link can be relied
  on afterwards.
- The disposition is three-valued. Undeclared data is recoverable — the
  supplier can answer — so it holds the line. A metallurgical conflict or
  a broken lot link is not recoverable from the same delivery, so it
  rejects it.

## Workflow

1. Resolve the element type on the order line to a chip resistor, chip
   capacitor or chip inductor, accepting the common short forms; refuse a
   type this clause does not cover rather than grading it on the baseline
   alone.
2. Build the required ordering data set as the union of the baseline items
   and the items the resolved type adds, then name every required item the
   order line did not declare.
3. Take the declared termination metallization together with the
   attachment method the assembly will use and decide whether the pair is
   taken as delivered or needs a barrier or another finish.
4. Form the applied-to-rated stress ratio and compare it with the derating
   limit of the resolved type, absorbing representation error at the limit
   with a named tolerance rather than by loosening the limit.
5. Confirm the delivered quantity carries exactly one distinct lot
   identifier; no identifier and several identifiers are different
   findings and both break traceability.
6. Combine the four checks into a disposition — release, hold or reject —
   and report the finding that governs it, then roll several order lines
   up so the worst line governs the order.

## Pitfalls

- Grading a bare chip on the baseline data set alone. The baseline is what
  every passive chip owes, not what any of them owes in full; a capacitor
  line that never declared its dielectric category is incomplete however
  tidy the baseline looks.
- Reading the termination finish on its own. Gold is an excellent bonding
  surface and a poor soldering one, so a finish is only a finding once the
  attachment method it will meet is known.
- Applying one derating fraction across the order. The fraction belongs to
  the element type, so a single figure applied to resistors, capacitors and
  inductors alike is simultaneously too tight on one and too loose on
  another.
- Accepting a delivery drawn from two lots because the total quantity is
  right. The count is not the point; the lot data no longer describes the
  elements in the tray, and every later lot-based decision inherits that.
- Rejecting an order line for undeclared data. An absent data item is a
  question for the supplier and holds the line; treating it as a rejection
  discards a lot that a reply would have released.
- Widening the derating limit so a chip sitting exactly on it passes. The
  equality is a representation question, handled by the tolerance inside
  the comparison; the limit stays as specified.

## Behavior contract (gate 3)

The element-type resolution, ordering data completeness, termination and
attachment pairing, derating ratio comparison, single-lot check, order line
disposition and order roll-up are exercised by the gate 3 contract test:
scripts/test_q6005_passive_chip_procurement.py against
scripts/q6005_passive_chip_procurement_logic.py (stdlib unittest, offline).
Run:
python3 scripts/test_q6005_passive_chip_procurement.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 →