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

E50 Telemetry In The Blind

ASecurity

Determine whether a spacecraft can transmit telemetry in the blind under ECSS-E-ST-50C clause 5.5.4: check the blind mode arms itself within the required time after the uplink is lost, that its carrier, modulation, coding and rate are a default the ground can acquire without first sending a command, and close the worst-case link budget at maximum range on the low-gain antenna to show the blind rate is actually receivable. Use when sizing a launch-and-early-orbit or safe-mode downlink, reviewi...

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 e50-telemetry-in-the-blind --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E50 Telemetry In The Blind?

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

Security grade badge for E50 Telemetry In The Blind
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e50-telemetry-in-the-blind/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e50-telemetry-in-the-blind)

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

Download with Pro
Files
SKILL.md
---
name: e50-telemetry-in-the-blind
description: "Determine whether a spacecraft can transmit telemetry in the blind under ECSS-E-ST-50C clause 5.5.4: check the blind mode arms itself within the required time after the uplink is lost, that its carrier, modulation, coding and rate are a default the ground can acquire without first sending a command, and close the worst-case link budget at maximum range on the low-gain antenna to show the blind rate is actually receivable. Use when sizing a launch-and-early-orbit or safe-mode downlink, reviewing a no-uplink recovery path, or verifying an emergency beacon configuration. Trigger: ecss, e-st-50-communications-scope, telemetry-in-the-blind, uplink-loss-timeout-arming, default-blind-downlink-configuration, blind-mode-low-gain-link-margin, blind-downlink-station-acquisition, emergency-downlink-rate."
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)"
clauses:
  - standard: ECSS-E-ST-50C Rev.2
    clause: 5.5.4
    items: [a]
    relation: verifies
metadata:
  domain: space-systems
  subdomain: ecss
  tags: [ecss, e-st-50-communications-scope, e50-telemetry-in-the-blind, blind-telemetry-transmission, uplink-loss-timeout-arming, default-blind-downlink-configuration, blind-mode-low-gain-link-margin, blind-downlink-station-acquisition, emergency-downlink-rate]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Communications — Telemetry in the Blind (space-systems/ecss/e50-telemetry-in-the-blind)

Use when the task is the telemetry-in-the-blind provision of ECSS-E-ST-50C
clause 5.5.4 — showing the spacecraft keeps transmitting telemetry that the
ground can acquire when no uplink has been received and no command can be
sent to make it do so.

## Domain quick reference

- Blind transmission exists for the states where commanding is not
  available: separation before first acquisition, a safe mode entered out
  of contact, a receiver or uplink chain failure. In every one of them the
  ground has no way to configure the downlink, so the configuration has to
  already be the one the ground is listening for.
- Arming is on a timeout, not on a diagnosis. The on-board logic counts
  the time since the last valid uplink event and enters the blind mode
  when that exceeds the configured timeout. A configured timeout longer
  than the required maximum means the spacecraft stays silent through a
  window the ground had planned to use.
- Ground acquirability is a property of the whole configuration, not of
  the carrier alone. Frequency, modulation scheme, symbol rate and coding
  each have to be in the set the receiving station can lock without being
  told; one parameter outside that set makes the signal present and
  unusable, which is the failure mode this clause exists to prevent.
- The link budget is the worst case, not the nominal one. Maximum range,
  the low-gain antenna pattern at the worst attitude, and no pointing
  gain: the received energy per bit has to clear the required threshold
  with the implementation loss included, which is what bounds the blind
  data rate from above.
- Rate and margin trade directly. Every doubling of the blind rate costs
  about three decibels of margin, so a blind mode that carries the full
  housekeeping rate is usually a mode whose margin closes only at short
  range — which is not the case it is needed in.

## Workflow

1. Validate the blind configuration: a positive carrier frequency, a
   positive symbol or bit rate, a named modulation and coding, and the
   configured uplink-loss timeout. Missing or non-positive entries are
   input errors.
2. Compare the configured timeout with the maximum the mission allows
   before blind telemetry has to be radiating, absorbing floating-point
   representation error at the boundary with a named tolerance.
3. Screen the configuration against the set the receiving station can
   acquire without an uplink: modulation, coding and rate each checked
   separately so the report names the offending parameter.
4. Confirm no element of the blind configuration is reached only through
   a telecommand; a parameter that needs commanding is unavailable in the
   state that triggers the mode.
5. Compute the worst-case free-space loss at maximum range, then close
   the budget: transmit effective isotropic radiated power, less losses,
   plus the station figure of merit, less the noise constant, less the
   rate term, less the required energy-per-bit threshold and the
   implementation loss.
6. Report the achieved margin, the rate the margin would support, and
   every finding: late arming, non-default parameter, command-dependent
   parameter, negative margin.

## Obligations

| Item | Step |
|---|---|
| ECSS-E-ST-50C Rev.2 5.5.4a | 4 |

## Pitfalls

- Verifying the blind mode with the high-gain antenna pointed. That
  budget closes easily and proves nothing about the tumbling, unpointed
  case the mode is entered in.
- Treating an unlocked receiver as a valid uplink event. Carrier lock
  without a valid, authenticated frame is not evidence of a working
  uplink; resetting the timeout on lock alone can hold the spacecraft out
  of blind mode indefinitely.
- Leaving the blind rate at the nominal housekeeping rate. The rate term
  is ten times the base-ten logarithm of the bit rate, so keeping the
  nominal rate spends the entire worst-case margin.
- Assuming the station will search. Acquisition without an uplink means
  the station is listening at a pre-agreed frequency with a pre-agreed
  demodulator; a swept or non-default configuration can go unnoticed for
  a whole pass.
- Relaxing the required energy-per-bit threshold to make a marginal case
  close. The threshold belongs to the coding scheme and the required
  frame error rate; an equality at the limit is a representation
  question, handled by the tolerance inside the comparison.

## Behavior contract (gate 3)

The configuration validation, timeout comparison, default-configuration
screening, command-dependency screening, free-space-loss computation and
link-margin closure are exercised by the gate 3 contract test:
scripts/test_e50_telemetry_in_the_blind.py against
scripts/e50_telemetry_in_the_blind_logic.py (stdlib unittest, offline).
Run:
python3 scripts/test_e50_telemetry_in_the_blind.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 →