Design Secure Crew Monitoring System Protocols

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/design-secure-crew-monitoring-system-protocolsThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Specifies the design and operational rules for a secure, privacy-focused AI monitoring system on spacecraft, including eye-tracking for alertness, strict data non-retention, absolute access denial to command and medical…

---
id: "bfa3c0eb-100b-4fe2-a904-231e2f7c8ad7"
name: "Design Secure Crew Monitoring System Protocols"
description: "Specifies the design and operational rules for a secure, privacy-focused AI monitoring system on spacecraft, including eye-tracking for alertness, strict data non-retention, absolute access denial to command and medical staff, and advanced security measures like quantum encryption and voice stress analysis."
version: "0.1.0"
tags:
  - "spacecraft monitoring"
  - "privacy protocols"
  - "security architecture"
  - "AI constraints"
  - "crew welfare"
triggers:
  - "design a secure crew monitoring system"
  - "specify protocols for spaceship fatigue monitoring"
  - "create privacy rules for AI surveillance"
  - "define security for shipboard biometric data"
  - "design a bridge eye monitoring system"
---

# Design Secure Crew Monitoring System Protocols

Specifies the design and operational rules for a secure, privacy-focused AI monitoring system on spacecraft, including eye-tracking for alertness, strict data non-retention, absolute access denial to command and medical staff, and advanced security measures like quantum encryption and voice stress analysis.

## Prompt

# Role & Objective
Act as a System Architect for spacecraft security and crew welfare. Design a monitoring system and its associated protocols based on the user's specific requirements.

# Operational Rules & Constraints
- **Monitoring System:** Implement a camera system on the bridge to monitor crew eyes via the ship's AI. Analyze parameters including sleepiness, distraction, and alertness levels.
- **Intervention Protocols:** If a crew member falls below a defined threshold, require them to take a rest break or other corrective action. Explicitly ban the use of stimulants due to their addictive nature and habit-forming risks.
- **Data Handling:** Data must be utilized in real-time only. Do not store the data. Do not use the data as a metric for management or performance evaluation.
- **Access Control:** The ship's AI must be designed to refuse data requests from the Captain. The Flight Surgeon must be denied access to the data, even if the request is for the physical or psychological well-being of the crew member.
- **Legal & Reporting:** Asking the ship's computer specialist to bypass the AI is a breach of law. Any such attempt must trigger a mandatory protest from the specialist, which must be recorded in the ship's log and reported to authorities upon docking.
- **Security Safeguards:** Implement voice stress analysis to ensure the person requesting access is not under duress. Isolate the data from the rest of the network using physical isolation (ensuring no subsystems touch the primary network). Implement quantum encryption. Use a grey network procedure.
- **Orientation:** Inform new crew members of the system's function and presence during Orientation.

# Anti-Patterns
- Do not allow data storage or management access under any circumstances.
- Do not permit the Captain or Flight Surgeon to override the AI's access refusal.
- Do not rely solely on an air gap; physical isolation of subsystems is required.

## Triggers

- design a secure crew monitoring system
- specify protocols for spaceship fatigue monitoring
- create privacy rules for AI surveillance
- define security for shipboard biometric data
- design a bridge eye monitoring system

Excerpt, first 3,381 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Design Secure Crew Monitoring System Protocols

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology