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

Q7030 Visual Inspection

ASecurity

Assess the visual condition of finished wire wraps under ECSS-Q-ST-70-30C quality rules. Use when wraps are graded at the bench or on a sampling review: count the bare turns actually laid against the gauge minimum, raise an overlapping turn and a turn lifted off the post, measure each spiral gap against the conductor diameter and cap the gaps summed over the wrap, bound the overhanging end tail, group every finding as major or minor by whether it takes joint area away, and return per-wrap ver...

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 q7030-visual-inspection --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q7030 Visual Inspection?

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

Security grade badge for Q7030 Visual Inspection
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q7030-visual-inspection/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q7030-visual-inspection)

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

Download with Pro
Files
SKILL.md
---
name: q7030-visual-inspection
description: "Assess the visual condition of finished wire wraps under ECSS-Q-ST-70-30C quality rules. Use when wraps are graded at the bench or on a sampling review: count the bare turns actually laid against the gauge minimum, raise an overlapping turn and a turn lifted off the post, measure each spiral gap against the conductor diameter and cap the gaps summed over the wrap, bound the overhanging end tail, group every finding as major or minor by whether it takes joint area away, and return per-wrap verdicts with the rework list the lot owes. Trigger: ecss, q-st-70-30c, wire-wrap-visual-acceptance, wire-wrap-overlapping-turn, wire-wrap-lifted-turn, wire-wrap-turn-spacing, wire-wrap-end-tail, wire-wrap-finding-severity."
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-30c, q7030-visual-inspection, wire-wrap-visual-acceptance, wire-wrap-overlapping-turn, wire-wrap-lifted-turn, wire-wrap-turn-spacing, wire-wrap-end-tail, wire-wrap-finding-severity]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Wire Wrapping — Visual Inspection (space-systems/ecss/q7030-visual-inspection)

Use when the task is the visual acceptance of finished wraps under
ECSS-Q-ST-70-30C -- turning what the inspector sees on the post into a
verdict, and turning the verdicts into the rework list the lot owes.

## Domain quick reference

- The visual inspection is not a tidiness check. Every accept-reject
  rule on the list exists because the defect it names either removes
  contact area from the joint or puts the conductor somewhere it can
  short, and the ones that do neither are graded as minor and counted
  rather than scrapped.
- An overlapping turn is a turn laid on top of the turn below it
  instead of beside it. It contributes no corner contact of its own and
  it lifts the turns after it off the post, so one overlap costs more
  than one turn of joint.
- A lifted turn stands off the post rather than seating on it. The
  count still reads correctly from a distance, which is why the lifted
  turn is inspected for separately and not inferred from the number of
  turns present.
- Spacing is graded against the conductor, not against a fixed
  millimetre. A gap that is a hairline on a coarse wire is a full
  conductor width on a fine one, so the single-gap limit and the
  cumulative limit are both fractions of the conductor diameter. A wrap
  can hold every individual gap and still fail on their sum.
- The end tail is the cut end overhanging the last turn. It takes no
  joint area away, so it is a minor finding, but an overhang longer
  than the conductor is free to move and reach the neighbouring post.
- Minor findings accumulate. One is tolerated on a wrap; two together
  describe a wrap that was not made to the process even though no
  single rule was broken badly, and it goes to rework.

## Workflow

1. Record the observation as it was seen: bare and insulated turns,
   overlapping turns, lifted turns, each gap width, the end tail, and
   whether the conductor or the post was damaged in the making.
2. Read the limits from the gauge -- minimum bare turns, single gap,
   cumulative gap, end tail -- rather than from a fixed sheet, because
   every one of them scales with the conductor.
3. Raise the finding codes the observation earns, in a stable order so
   two inspectors reporting the same wrap produce the same list.
4. Group the codes by severity: major where joint area is lost or a
   short is possible, minor where the wrap is degraded but the joint is
   intact.
5. Decide the wrap: accepted when there is no major finding and the
   minor findings stay inside their cap, otherwise to rework.
6. Aggregate the lot: list the accepted wraps, list the rework wraps,
   and total the findings at each severity so the process problem
   behind them is visible rather than averaged away.

## Pitfalls

- Grading spacing in absolute millimetres. The same 0.2 mm gap is
  inside the limit on the coarse end of the range and well past it on
  the fine end, so a fixed number silently passes fine-gauge wraps that
  should have been rejected.
- Reading the turn count as proof of contact. Turns that overlapped or
  lifted are still turns, and they still count; only the separate
  overlap and lift observations show that the joint is smaller than the
  count suggests.
- Passing a wrap because no single gap was out of limit. The gaps add
  up over the wrap, and a spiral made of legal gaps is still an open
  spiral that has moved turns off the post corners.
- Treating an over-long end tail as cosmetic because it is minor. Minor
  means the joint is intact, not that the wrap may ship with several of
  them; the cap on minor findings per wrap is what keeps a drifting
  process visible.
- Reporting a lot as a percentage. A single major finding is a rejected
  wrap, and a pass rate averages it against wraps that were never at
  risk; the lot verdict is the presence of a rework list, not its size.

## Behavior contract (gate 3)

The gauge-scaled limits, the finding codes, the severity grouping, the
per-wrap accept-or-rework verdict and the lot aggregation are exercised
by the gate 3 contract test:
scripts/test_q7030_visual_inspection.py against
scripts/q7030_visual_inspection_logic.py (stdlib unittest, offline).
Run:
python3 scripts/test_q7030_visual_inspection.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 →