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

Q7003 Bath Control

ASecurity

Monitor the chemical control and analysis schedule of a black-anodizing line under the ECSS-Q-ST-70-03C process-control clause. Use when a tank reading, an overdue titration or a proposed bath addition has to be turned into a disposition before parts are run: place every parameter in its control band or its reject band, drive the analysis schedule off elapsed time and processed area together and take whichever arrives first, size the addition from tank volume, shortfall and additive strength,...

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 q7003-bath-control --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q7003 Bath Control?

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

Security grade badge for Q7003 Bath Control
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q7003-bath-control/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q7003-bath-control)

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

Download with Pro
Files
SKILL.md
---
name: q7003-bath-control
description: "Monitor the chemical control and analysis schedule of a black-anodizing line under the ECSS-Q-ST-70-03C process-control clause. Use when a tank reading, an overdue titration or a proposed bath addition has to be turned into a disposition before parts are run: place every parameter in its control band or its reject band, drive the analysis schedule off elapsed time and processed area together and take whichever arrives first, size the addition from tank volume, shortfall and additive strength, size the dilution when a parameter has drifted high instead, and roll the worst tank up into one line disposition. Trigger: ecss, q-st-70-03-black-anodizing-scope, anodizing-bath-control-limits, bath-analysis-schedule-interval, bath-addition-mass-calculation, bath-dilution-make-up, tank-out-of-service-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-70-03-black-anodizing-scope, q7003-bath-control, anodizing-bath-control-limits, bath-analysis-schedule-interval, bath-addition-mass-calculation, bath-dilution-make-up, tank-out-of-service-disposition, processed-area-analysis-trigger]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Black Anodizing — Bath Control (space-systems/ecss/q7003-bath-control)

Use when the task is the process-control clause of ECSS-Q-ST-70-03C --
keeping every tank on a black-anodizing line inside the chemistry it
was qualified at, deciding when each one is analysed, and turning a
titration result into an addition, a dilution or a stop.

## Domain quick reference

- Every parameter carries two bands, not one. Inside the control band
  the tank runs. Between the control band and the reject band it runs
  after a correction, because the chemistry is recoverable. Outside
  the reject band the tank comes off line, because a part already run
  through it cannot be recovered by anything done downstream.
- The two bands have to nest, and the nominal has to sit inside the
  control band. A parameter record whose bands cross is not a strict
  control limit, it is a typing error, and it is rejected rather than
  interpreted.
- Analysis runs on two clocks at once. A tank ages while it works,
  through drag-out, drag-in and dissolved metal, and it also ages
  while it idles, through evaporation and carbonation. So the schedule
  carries an elapsed-time interval and a processed-area interval, and
  whichever arrives first makes the analysis due.
- An overdue analysis is not a small version of a due one. Past the
  grace the last reading no longer describes the tank at all, so the
  tank comes off line rather than being flagged, and the record says
  which of the two clocks drove it.
- A correction is a weighed quantity. For a parameter below nominal it
  follows from the tank volume, the shortfall and the strength of the
  material being added, so a half-strength additive is twice the
  weight. That is the number the operator needs, not the shortfall.
- A parameter that has drifted high cannot be added to. It is brought
  back by make-up volume, and the dilution follows from the same
  arithmetic run the other way, which is also why a tank near its
  freeboard has fewer options than its reading suggests.
- The line is only as controlled as its worst tank. A line disposition
  is the worst tank disposition, and reporting it any other way lets a
  single rejected tank hide behind five healthy ones.

## Workflow

1. Validate each parameter record and reject crossed bands or a
   nominal outside the control band rather than repairing them.
2. Place each measured value into in-control, adjustment-required or
   out-of-service, treating a value that lands exactly on a band edge
   as inside that band.
3. Size the correction each drifted parameter needs: an addition mass
   from volume, shortfall and additive strength when the value is low,
   a make-up volume when it is high.
4. Run the analysis schedule on both clocks, take the one further
   through its interval, and record which one drove the answer.
5. Fold a due analysis into an adjustment and an overdue one into an
   out-of-service, rather than letting a stale reading stand.
6. Take the worst parameter as the tank disposition and the worst tank
   as the line disposition, then report the corrections, the findings,
   the tanks off line and the tanks owing an analysis.

## Pitfalls

- Controlling to a single limit. A tank with one number on the sheet
  gives the operator no way to tell a bath that needs a top-up from a
  bath that has already made bad parts, so every drift becomes either
  an unnecessary stop or an undetected escape.
- Scheduling analysis by calendar alone. A tank that ran three shifts
  of heavy loads is chemically older than the calendar says, and the
  processed-area clock is the only one that sees it.
- Treating an overdue titration as paperwork. The tank has been run on
  an assumption since the due point, so the question is not when to
  analyse it but which parts were made while nobody knew.
- Reporting the shortfall instead of the addition. The operator adds a
  mass into a volume, and a shortfall quoted per litre has to be
  multiplied by the tank and divided by the additive strength before
  it means anything on the scale.
- Averaging the line. Five healthy tanks and one rejected one is a
  stopped line, not a mostly-good one, and any roll-up that does not
  take the worst tank hides exactly the tank that matters.

## Behavior contract (gate 3)

The band nesting, parameter disposition, addition and dilution
arithmetic, two-clock analysis schedule, overdue grace, tank roll-up
and line disposition are exercised by the gate 3 contract test:
scripts/test_q7003_bath_control.py against
scripts/q7003_bath_control_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_q7003_bath_control.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 →