← Back to Skills Marketplace
aaalenwow

Low Altitude Guardian

by AAAlenwow · GitHub ↗ · v0.3.0 · MIT-0
cross-platform ✓ Security Clean
306
Downloads
0
Stars
2
Active Installs
4
Versions
Install in OpenClaw
/install low-altitude-guardian
Description
低空无人设备应急裁决引擎。零依赖可用:基于损失优先级金字塔(P0-P4)和加权决策公式,对无人机/eVTOL突发危机进行分级分析、方案推导、输出可执行决策建议。分析辅助工具,不连接飞控系统,不执行实际飞行控制。
README (SKILL.md)

接收突发情况描述,输出结构化应急决策建议。

⚠️ ALPHA — 重要声明:

  • 本技能为分析辅助工具,不连接任何飞控系统,不执行实际飞行控制
  • 输出结果为决策参考建议,不替代经认证的飞行安全系统
  • 真实飞行作业中,任何最终决策须由持证操作员或认证飞控系统执行

运行模式

模式 依赖 适用场景
推理分析模式(默认) 情景演练、方案推导、培训、Agent 集成
集成模式 Python + 数据接口 与实际遥测系统对接(开发/仿真环境)

调用示例

# 单次危机分析
我的无人机 GPS 信号突然丢失,当前高度 80m,电量 45%,下方是居民区。帮我分析应对方案。

# 结构化输入
设备: UAV-001 多旋翼
位置: 高度120m,速度15m/s,下方有人行道
状态: 电量34%,左前电机异常振动
环境: 风速8m/s,通信正常
触发: 电机异常,机身开始偏航

# 方案推演
如果同时发生 GPS 丢失 + 单电机故障,应该怎么处置?

# 知识库查询
电池热失控的标准处置流程是什么?

核心方法论:损失优先级金字塔

所有决策的唯一不可动摇约束:

P0 人员安全   ← 绝对最高优先级,任何情况下不可妥协
P1 公共安全   ← 公共设施、建筑、交通
P2 第三方财产 ← 他人车辆、农作物
P3 本机安全   ← 设备自身完整性
P4 任务完成   ← 原定任务目标

关键原则:为保障 P0,可以主动坠毁设备(P3)。高优先级受威胁时,必须无条件牺牲低优先级。


Phase 1: 态势快照

接收突发情况后,立即提取以下关键字段(自然语言描述或结构化均可):

设备: [device_id] [device_type]
位置: [坐标/区域描述] 高度[m] 速度[m/s] 航向
状态: 电量[%] 飞行阶段 载荷[kg]
触发: [危机触发原因]
环境: 风速[m/s] 下方区域[人群/建筑/空旷] 通信[正常/异常]

同步推断:可飞行安全包络线、最近可用备降点、周边禁飞区。


Phase 2: 危机分级

等级 名称 判定条件 分析时限
L5-CRITICAL 灾难性 即刻威胁人员生命 \x3C 3秒
L4-SEVERE 严重 高概率人员伤害或重大财产损失 \x3C 10秒
L3-MAJOR 重大 设备功能严重降级,可能危及安全 \x3C 30秒
L2-MINOR 一般 功能部分降级,可控范围 \x3C 2分钟
L1-CAUTION 注意 潜在风险,暂无直接威胁 \x3C 5分钟

态势演化预测:预测 30s/60s/180s 后态势,识别级联故障风险(如电机故障 → 电池过放)和可用决策时间窗口。


Phase 3: 方案推导与最优裁决

3.1 知识库匹配

覆盖场景:动力系统故障 / 导航定位故障 / 通信故障 / 环境威胁 / 碰撞风险 / 复合故障

# 集成模式可调用:
python3 scripts/decision_manager.py --match --crisis-type \x3Ctype> --level \x3Clevel>

3.2 最优裁决公式

Score = 0.40×S₀(人员安全) + 0.25×S₁(公共安全) + 0.15×S₂(第三方财产)
      + 0.12×S₃(本机安全) + 0.08×S₄(任务完成)

硬约束:S₀ \x3C 80 的方案一律淘汰,无论总分多高

3.3 无匹配时的第一性原理推理

新型故障或罕见组合时:

  1. 分解 → 拆解为已知子问题组合
  2. 评估可控能力 → 当前设备还有哪些控制能力
  3. 最低降落需求 → 安全着陆至少需要什么能力
  4. 无法安全降落时 → 按 P0→P1→P2→P3 顺序选择损失最小的坠落区域
  5. 保守原则 → 无先例时,选最保守方案

3.4 人工介入模式参考

等级 建议介入模式
L5 自主执行,事后通知(无等待时间)
L4 自主执行,同步通知操作员
L3 推荐方案,等待 5 秒确认,超时自动执行
L2 推荐方案,等待操作员确认
L1 仅提醒,由操作员决策

输出格式

{
  "crisis_level": "L3-MAJOR",
  "crisis_type": "power_failure.single_motor_loss",
  "time_window_seconds": 30,
  "selected_plan": {
    "name": "三电机降级返航",
    "source": "knowledge_base | first_principles",
    "confidence": 0.87,
    "steps": [
      {"seq": 1, "action": "切换三电机飞行模式", "timeout_ms": 500},
      {"seq": 2, "action": "降至安全包络高度", "timeout_ms": 5000},
      {"seq": 3, "action": "计算最近备降点航线", "timeout_ms": 1000},
      {"seq": 4, "action": "降级模式飞往备降点", "timeout_ms": null},
      {"seq": 5, "action": "执行应急着陆程序", "timeout_ms": 30000}
    ],
    "priority_score": 91.2,
    "estimated_loss": {
      "human_safety_risk": "none",
      "public_safety_risk": "none",
      "device_damage": "minor"
    }
  },
  "eliminated_plans": [
    {"name": "强制立即降落", "reason": "S₀=65 \x3C 80,下方有行人,一律淘汰"}
  ]
}

Phase 4: 事件复盘与知识库自迭代

事件结束后:

python3 scripts/incident_reporter.py --generate-report --incident-id \x3Cid>
python3 scripts/knowledge_updater.py --learn --incident-id \x3Cid>

复盘内容:触发原因、决策过程(选了什么/为什么/排除了什么)、执行效果、实际损失。

知识库更新:第一性原理推导出的有效方案,自动封装为新模板。每次事件都让系统更强。


边界与合规

本技能做什么: 危机情景分析、方案推导、决策评分、复盘报告。

本技能不做什么:

  • 不连接任何飞控系统或硬件接口
  • 不执行实际飞行控制指令
  • 不替代经 CAAC/FAA 认证的飞行安全系统
  • 不提供法律或保险合规建议

数据流向:所有情景分析在本次会话中处理,不向外部系统传输飞行数据。集成模式下的遥测数据处理范围由用户自行配置。

Usage Guidance
This skill appears to be what it claims: an offline/analysis decision engine with templates and local persistence. Before installing or running it against live systems, consider the following: - Run it in a sandbox or isolated environment first to inspect what it writes into the .guardian directory and verify no unexpected network traffic. - Search the code for network libraries or hard-coded endpoints (e.g., requests, urllib, socket, http) and review any code that sends data out. The visible files do not show network calls, but some files were truncated — confirm there are no hidden remote endpoints. - Do NOT enable or connect the 'integration mode' to any flight controller, autopilot, or live telemetry until you have audited integration scripts (they may implement actions like 'send_location' or 'broadcast_emergency' which could transmit data or trigger systems). - If you plan to use enterprise features (knowledge ingestion, auto-generation), verify input sources and sanitize any imported files to avoid accidental ingestion of sensitive data. - Keep in mind the authorship/source is unknown; although the package is coherent, exercise standard caution: inspect code, run tests with synthetic incidents, and avoid giving network or hardware access until you are satisfied with the audit. If you want, I can: (a) scan the full codebase for network/IPC/syscalls (search for imports like requests, socket, subprocess, urllib), or (b) summarize any truncated files to increase confidence.
Capability Analysis
Type: OpenClaw Skill Name: low-altitude-guardian Version: 0.3.0 The 'low-altitude-guardian' skill bundle is a comprehensive emergency decision-making framework for UAVs/drones. The code and documentation (SKILL.md) are consistently aligned with the stated purpose of providing safety-first crisis analysis based on a 'Loss Priority Pyramid' (P0-P4). The Python scripts (crisis_engine.py, decision_manager.py, etc.) implement structured logic for situational awareness, incident reporting, and knowledge base management using only standard libraries. All data operations are local, storing logs and reports in a project-relative '.guardian' directory, with no evidence of network exfiltration, unauthorized execution, or malicious prompt injection.
Capability Assessment
Purpose & Capability
Name/description (crisis decision engine for drones/eVTOL) match the provided scripts, templates, and documentation. The packaged scripts (crisis_engine, decision_manager, emergency_plan_generator, enterprise_kb_manager, fleet_analytics, incident_reporter, situation_awareness) and solution templates align with the described functionality. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md limits default behavior to analysis-only and documents an optional 'integration mode' for telemetry. The repo contains many action templates (e.g., 'broadcast_emergency', 'send_location', 'deploy_parachute', 'cut_battery', 'switch_flight_mode') that describe commands a flight system would execute; the code appears to only model/record those actions and not automatically connect to flight controllers. This is coherent with the stated modes, but if a user wire-up integration mode or modifies scripts to call hardware/network interfaces, those actions could have real-world effects. Review integration-related scripts before enabling network/hardware access.
Install Mechanism
No install spec included (instruction-only skill in registry), so nothing is downloaded/executed by the platform beyond the skill files. The README suggests optional cloning or ClawHub install, but that is an external user action. There is no automated installer URL or archive in the skill that would write arbitrary code at install time.
Credentials
The skill declares no required environment variables, credentials, or external config paths. All data read/written is under the project and a .guardian workspace (local). No requests for unrelated secrets or high-privilege env variables are present.
Persistence & Privilege
The code persists data under a .guardian directory (knowledge_base, incidents, emergency_plans, analytics_reports, decisions). This is expected for a knowledge-base/analytics tool but means the skill will create and retain local files. always is false and the skill does not request elevated system privileges, nor does it modify other skills' configs. If you care about data residency, inspect .guardian contents and file permissions before heavy use.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install low-altitude-guardian
  3. After installation, invoke the skill by name or use /low-altitude-guardian
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.3.0
优化:AI推理优先架构(零依赖可用);添加运行模式/调用示例/数据流向/边界声明;py脚本增强:否定语境检测、滑动窗口检测、镜头元素提取修复、复合故障矩阵、角色弧线追踪
v0.2.1
No file changes detected in version 0.2.1. - No updates or modifications were introduced in this version. - Functionality and documentation remain identical to version 0.2.0.
v0.2.0
low-altitude-guardian v0.2.0 introduces enterprise-level features and enhancements: - Added enterprise data ingestion, knowledge base health check, and emergency plan auto-generation tools (new scripts and templates). - Expanded capabilities from device-level crisis response to include organization-level data collection, fleet analytics, and knowledge management. - Updated documentation to reflect new "enterprise" phases and workflows for operational learning and compliance support. - Maintained core device-side real-time crisis classification, decision-making, and event reporting functions. - Still in ALPHA: for analysis and planning only, not for real-world flight.
v0.1.0
Initial release: 低空设备危机应急响应技能包,包含7阶段闭环处理流程、5个预置解决方案、损失优先级金字塔决策引擎
Metadata
Slug low-altitude-guardian
Version 0.3.0
License MIT-0
All-time Installs 2
Active Installs 2
Total Versions 4
Frequently Asked Questions

What is Low Altitude Guardian?

低空无人设备应急裁决引擎。零依赖可用:基于损失优先级金字塔(P0-P4)和加权决策公式,对无人机/eVTOL突发危机进行分级分析、方案推导、输出可执行决策建议。分析辅助工具,不连接飞控系统,不执行实际飞行控制。 It is an AI Agent Skill for Claude Code / OpenClaw, with 306 downloads so far.

How do I install Low Altitude Guardian?

Run "/install low-altitude-guardian" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Low Altitude Guardian free?

Yes, Low Altitude Guardian is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Low Altitude Guardian support?

Low Altitude Guardian is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Low Altitude Guardian?

It is built and maintained by AAAlenwow (@aaalenwow); the current version is v0.3.0.

💬 Comments