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

Q7001 Launch Site Control

ASecurity

Plan the cleanliness controls that carry a spacecraft through a launch campaign without spending the budget it arrived with. Use when arrival, unpacking, integration, propellant loading, encapsulation, transfer and pad stay each have a duration, an environment and a protection state, and the fairing has to be verified before it closes. Accumulates particulate and molecular pickup stage by stage, credits a container, cover or purge only for what it blocks, refuses a loading stage run without v...

2 stars
0 votes
0 copies
0 views
Added 9/27/2026
ai-agentspython

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 q7001-launch-site-control --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q7001 Launch Site Control?

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

Security grade badge for Q7001 Launch Site Control
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q7001-launch-site-control/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q7001-launch-site-control)

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

Download with Pro
Files
SKILL.md
---
name: q7001-launch-site-control
description: "Plan the cleanliness controls that carry a spacecraft through a launch campaign without spending the budget it arrived with. Use when arrival, unpacking, integration, propellant loading, encapsulation, transfer and pad stay each have a duration, an environment and a protection state, and the fairing has to be verified before it closes. Accumulates particulate and molecular pickup stage by stage, credits a container, cover or purge only for what it blocks, refuses a loading stage run without vapour protection, refuses a purge credit with no purge connected, and reports the budget left at lift-off with the stage that consumed most of it. Trigger: ecss, q-st-70-01, launch-campaign-cleanliness, fairing-cleanliness-verification, propellant-loading-vapour-protection, launch-site-purge-credit, transport-container-protection, pad-stay-contamination-budget."
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-01-cleanliness-contamination-control, q7001-launch-site-control, launch-campaign-cleanliness, fairing-cleanliness-verification, propellant-loading-vapour-protection, launch-site-purge-credit, transport-container-protection, pad-stay-contamination-budget]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Contamination Control — Launch Site (space-systems/ecss/q7001-launch-site-control)

Use when the task is preserving cleanliness at the launch site under
ECSS-Q-ST-70-01 — from the container arriving at the processing hall to the
vehicle standing on the pad. This leaf covers the ground campaign; the in-orbit
leaf takes over after separation.

## Domain quick reference

- The launch campaign is where the cleanliness budget is most often spent and
  least often measured. The article is at its most exposed, the environments
  are the worst it has seen since manufacture, and the stages are long.
- Encapsulation is a one-way door. Once the fairing closes, nothing inside can
  be inspected, sampled or re-cleaned, so a verification before it closes is
  the last opportunity that exists; closing on an unverified article is not a
  risk to be tracked, it is a finding.
- Propellant loading is a molecular source, not just a hazardous operation. The
  vapour reaches surfaces the liquid never touches, and a deposit laid down at
  the pad is not removable there, so the article is protected against vapour or
  the operation is re-planned.
- A purge credit belongs to a connected purge. An encapsulated volume with the
  purge line off is a closed box slowly equalising with the hall, and claiming
  the purged transmission for it understates the pickup by nearly an order of
  magnitude.
- Protection states rank, and the ranking is the plan. A transport container
  beats a bag, a purged fairing beats an unpurged one, and a pad stay is
  survivable only because the fairing is closed and flowing.
- The article's arrival state is the campaign's opening balance. A budget that
  starts at zero at the gate credits the campaign with cleanliness the shipping
  already spent.

## Workflow

1. Validate each stage: a known activity, a known environment, a non-negative
   duration and a known protection state.
2. Validate the sequence: no activity twice, and no activity ahead of one that
   physically precedes it — an encapsulation before integration is an input
   error, not an aggressive schedule.
3. Compute the particulate pickup of each stage from the environment rate, the
   duration and the protection transmission.
4. Compute the molecular pickup the same way, adding the propellant vapour
   source during loading and reducing it where vapour protection is declared.
5. Apply the campaign rules: verified fairing before encapsulation, vapour
   protection during loading, a connected purge behind any purge credit.
6. Accumulate both totals from the arrival balance, and compare them with the
   budgets through a named tolerance so an exactly-consumed budget still
   closes.
7. Report the totals, margins, the dominant stage and every blocking finding.

## Pitfalls

- Verifying the fairing after encapsulation. The measurement has to happen
  while the surface is still reachable; afterwards the only options are opening
  it again or launching on an assumption.
- Treating propellant loading as a safety operation with no contamination
  content. The vapour deposits on everything with a view of the volume, and the
  article is usually at its most exposed at that point in the flow.
- Claiming the purged-fairing transmission for a fairing whose purge is not
  connected. The credit is the largest in the table, and it is the easiest to
  take by habit.
- Budgeting the pad stay as though the fairing were open, or the transfer as
  though it were closed. The protection state, not the environment, is what
  makes a long pad stay affordable.
- Starting the campaign budget at zero. Transport is a stage like any other,
  and the article that arrives has already spent part of the allocation.
- Reading an exactly-consumed budget as a breach. The comparison carries a
  named tolerance, because a sum of stage contributions can land on the budget
  a bit either side of it.

## Behavior contract (gate 3)

The environment and protection tables, stage and sequence validation, the
per-stage particulate and molecular contributions, the propellant-vapour
source, the fairing-verification, vapour-protection and purge-credit rules, the
campaign accumulation and the lift-off margins are exercised by the gate 3
contract test: scripts/test_q7001_launch_site_control.py against
scripts/q7001_launch_site_control_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_q7001_launch_site_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 →