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

Q7040 Post Braze Treatments

ASecurity

Derive the post-braze treatment a brazement owes and decide whether it may leave the cleaning bay. Use when a part has come out of the braze cycle and the cleaning route has to be set from the process rather than from how the joint looks: build the ordered operation list from the flux family and the parent alloy, add a chemical step only where the residue is a corrosive halide, hold the removal to the window before the residue vitrifies, evidence the removal through final-rinse conductivity a...

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 q7040-post-braze-treatments --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q7040 Post Braze Treatments?

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

Security grade badge for Q7040 Post Braze Treatments
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q7040-post-braze-treatments/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q7040-post-braze-treatments)

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

Download with Pro
Files
SKILL.md
---
name: q7040-post-braze-treatments
description: "Derive the post-braze treatment a brazement owes and decide whether it may leave the cleaning bay. Use when a part has come out of the braze cycle and the cleaning route has to be set from the process rather than from how the joint looks: build the ordered operation list from the flux family and the parent alloy, add a chemical step only where the residue is a corrosive halide, hold the removal to the window before the residue vitrifies, evidence the removal through final-rinse conductivity against the feed water, and require passivation only on the steel that carries a chromium-oxide film. Trigger: ecss, q-st-70-40-brazing, braze-flux-residue-removal, braze-final-rinse-conductivity, braze-stainless-passivation, braze-residue-removal-window, post-braze-cleaning-sequence."
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-40-brazing, q7040-post-braze-treatments, braze-flux-residue-removal, braze-final-rinse-conductivity, braze-stainless-passivation, post-braze-cleaning-sequence]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Brazing — Post-Braze Treatments (space-systems/ecss/q7040-post-braze-treatments)

Use when the task is the post-braze clause of ECSS-Q-ST-70-40: setting
the cleaning, residue-removal and passivation sequence a brazement owes
after it leaves the heat, and deciding whether that sequence actually
closed.

## Domain quick reference

- What a part owes afterwards is set by what was used to make the filler
  flow, not by how the joint looks. A clean joint out of a fluxed
  process still carries residue.
- A vacuum or clean inert-gas furnace cycle is flux-free. It leaves
  nothing to remove, and adding a chemical cleaning step to it
  introduces a corrosion risk instead of removing one.
- A vacuum cycle recorded together with a flux is not a conservative
  entry; it is two records contradicting each other, and it is resolved
  before the part moves.
- Borax and boric residues are glassy and hygroscopic. The halide
  families — fluoride and chloride bearing — are actively corrosive and
  keep attacking the parent metal for as long as they are on the part,
  so they take a mechanical and a chemical step, not a rinse alone.
- Removal has a deadline. The residue is soluble while it is warm and
  hydrated; once it cools and dries it vitrifies, and the hot-water
  quench that would have lifted it no longer will. The tighter the
  corrosivity, the shorter the window.
- Removal is evidenced, not asserted. The evidence is the conductivity
  of the final rinse measured against the conductivity of the feed
  water: a rinse leaving the part much more conductive than it arrived
  is still carrying ionic residue, whatever the part looks like.
- Passivation restores the chromium-oxide film that the braze thermal
  cycle and the cleaning both degrade on an austenitic stainless steel.
  It is meaningless on aluminium, titanium, copper and nickel alloys,
  and specifying it there is a process error.
- Passivation runs after the residue has gone. Passivating over a
  residue seals it under the restored film.

## Workflow

1. Read the process and the flux family off the braze record and refuse
   the pair that cannot coexist.
2. Build the ordered operation list: controlled cool, then residue
   removal where a residue exists, with the mechanical and chemical
   steps added only for a corrosive halide, then the final rinse and its
   conductivity verification, then passivation where the alloy carries a
   film, then drying and the visual check.
3. Compare the operations actually recorded against that list and report
   the gaps in the order they were owed, so the recovery runs in
   sequence rather than in the order somebody noticed them.
4. Check the hours from the end of the braze to the start of removal
   against the window for the flux family, absorbing representation
   error at the boundary with a named tolerance.
5. Evaluate the final rinse as a ratio against the feed conductivity
   rather than as an absolute number, so a facility on harder water is
   not graded against somebody else's supply.
6. Release the part only when no operation is missing, the removal was
   inside its window and the rinse evidences a clean surface. Report
   every finding, not only the first.

## Pitfalls

- Grading the cleaning on appearance. A vitrified halide film is
  transparent and the part looks finished; the conductivity reading is
  what sees it.
- Adding a chemical cleaning step to a vacuum-brazed part because the
  route looks thorough. There is no residue to attack, so the chemistry
  attacks the parent metal instead.
- Measuring the final rinse without measuring the feed. The absolute
  number carries the facility's water in it and says nothing about what
  came off the part.
- Passivating before the residue is off. The film goes down over the
  residue and the corrosion continues underneath it.
- Letting a part sit over a shift change before removal because the
  paperwork allows the operation in any order. The window runs from the
  end of the braze, not from the start of the shift that will do it.
- Widening the rinse allowance to pass an exact-equality reading. The
  equality is a representation question, handled by the tolerance inside
  the comparison; the allowance stays as specified.

## Behavior contract (gate 3)

The flux-family residue and corrosivity split, the removal window, the
passivation applicability rule, the ordered operation list with its
process and flux contradiction check, the ordered gap list, the
ratio-based final-rinse assessment with its boundary tolerance and the
release verdict are exercised by the gate 3 contract test:
scripts/test_q7040_post_braze_treatments.py against
scripts/q7040_post_braze_treatments_logic.py (stdlib unittest, offline).
Run:
python3 scripts/test_q7040_post_braze_treatments.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 →