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

Q7031 Surface Verification

ASecurity

Assess whether a prepared substrate is genuinely fit to receive its first coat under ECSS-Q-ST-70-31C: read the water-break observation only when it was held long enough to be evidence, compare non-volatile residue and particulate obscuration against their limits, grade the abrasion profile against a two-sided roughness window that fails both too smooth and too rough, compute the substrate dew-point margin and coating-area humidity, and separate a surface failure that means preparing again fr...

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 q7031-surface-verification --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q7031 Surface Verification?

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

Security grade badge for Q7031 Surface Verification
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q7031-surface-verification/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q7031-surface-verification)

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

Download with Pro
Files
SKILL.md
---
name: q7031-surface-verification
description: "Assess whether a prepared substrate is genuinely fit to receive its first coat under ECSS-Q-ST-70-31C: read the water-break observation only when it was held long enough to be evidence, compare non-volatile residue and particulate obscuration against their limits, grade the abrasion profile against a two-sided roughness window that fails both too smooth and too rough, compute the substrate dew-point margin and coating-area humidity, and separate a surface failure that means preparing again from a room failure that means waiting. Use when a prepared surface is about to be coated. Trigger: ecss, q-st-70-31c, paint-surface-readiness, water-break-cleanliness-test, paint-surface-roughness-window, paint-dew-point-margin, paint-coating-area-humidity."
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-31c-paint-application, q-st-70-31c, q7031-surface-verification, paint-surface-readiness, water-break-cleanliness-test, paint-surface-roughness-window, paint-dew-point-margin, paint-coating-area-humidity]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Paints — Prepared Surface Verification (space-systems/ecss/q7031-surface-verification)

Use when the task is the verification made on a prepared surface under
ECSS-Q-ST-70-31C, in the minutes before the first coat: whether the surface is
clean, whether its profile is inside the window the paint system needs, and
whether the substrate and the air around it are dry enough to coat at all.

## Domain quick reference

- The water-break test is an observation with a dwell attached. A film watched
  for a few seconds has not had time to retract over a contaminated patch, so a
  short-dwell observation is refused as evidence rather than recorded as a
  pass. Passing it means an unbroken film, not the absence of a noted break.
- Cleanliness has two independent axes. A film-forming residue and a
  particulate load fail in different ways and are measured differently, so a
  surface can be visually spotless and still carry residue that destroys
  adhesion.
- The roughness requirement is two-sided, and the lower bound is the one that
  gets forgotten. Too smooth starves the mechanical key the primer needs; too
  rough leaves peaks the film cannot cover, and thin film over a peak is where
  corrosion starts. Both are failures of the same requirement.
- Dryness is a margin, not a temperature. A substrate sitting near the dew
  point condenses an invisible water layer as soon as evaporating solvent cools
  it further, which is why the substrate temperature is compared against the
  dew point rather than against a fixed number.
- Humidity in the coating area and the substrate margin are separate checks.
  One can be inside its limit while the other is not, and they fail for
  different reasons.
- A surface finding and an environmental finding call for different actions.
  The surface has to be prepared again; the room only has to be waited out, and
  conflating the two either wastes a preparation or coats into a bad room.

## Workflow

1. Validate the water-break dwell and take the observation only if it stands as
   evidence.
2. Compare non-volatile residue and particulate obscuration against their
   limits, or against the per-item limits when the drawing sets them.
3. Look up the roughness window for the paint system, or take the per-item
   override, and grade the measured profile as in-window, too-smooth or
   too-rough.
4. Compute the dew-point margin from the substrate temperature and the measured
   dew point, and compare it against the minimum.
5. Compare the coating-area relative humidity against its ceiling.
6. Group the findings into surface and environment, and close on re-prepare,
   conditions-hold or ready-to-coat, with a surface finding outranking an
   environmental one.

## Pitfalls

- Recording a water-break result without its dwell. The number of seconds is
  what makes the observation mean anything, and a pass without it is an opinion.
- Grading roughness against an upper bound only. A polished surface passes that
  test and then fails adhesion, which is precisely the case the lower bound
  exists to catch.
- Comparing the substrate temperature against an air temperature limit. The
  quantity that governs condensation is the margin above the dew point, and a
  warm room with damp air can still be a condensing surface.
- Treating a humid room as a preparation failure. The surface is fine; the
  conditions are not, and preparing it again neither dries the air nor makes
  the item any readier.
- Widening a limit so an exactly-at-limit reading passes. Equality at the limit
  is a representation question handled by the tolerance inside the comparison;
  the limits stay where the drawing set them.

## Behavior contract (gate 3)

The water-break dwell validation, residue and obscuration comparisons, the
two-sided roughness window, the dew-point margin, the humidity ceiling and the
surface-versus-environment disposition are exercised by the gate 3 contract
test: scripts/test_q7031_surface_verification.py against
scripts/q7031_surface_verification_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_q7031_surface_verification.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 →