Token导航 LogoToken导航

Agent Skill · 效率

void-atlas-protocol(无效阿特拉斯协议)

void-atlas-protocol 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

void-atlas-protocol 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 2,091。

总安装 29,367周安装 1,236GitHub Stars 公开资料未说明下载 10,284核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.1

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:void-atlas-protocol(无效阿特拉斯协议)
来源仓库:https://github.com/deepseekoracle/void-atlas-protocol
安装命令:
openclaw skills install void-atlas-protocol
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install void-atlas-protocol

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

Void Atlas Protocol – 一张四轴道德导航地图(权力、真理、主权、关怀),带有用于评估系统、社区和政策的航路点、路线和路线规则。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install void-atlas-protocol;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

void-atlas-protocol 怎么安装?

在终端执行 openclaw skills install void-atlas-protocol。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

void-atlas-protocol 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

void-atlas-protocol 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

void-atlas-protocol 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

void-atlas-protocol 用的人多吗?

公开数据是累计安装 29,367 次,近一周安装 1,236 次,下载 10,284 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

void-atlas-protocol 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理效率类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
github

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
void-atlas-protocol

无效阿特拉斯协议 · 本页

29,367—需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
void-atlas-protocol
description
Void Atlas Protocol – a four-axis ethical navigation map (power, truth, sovereignty, care) with waypoints, routes, and routing rules for evaluating systems, communities, and policies.

Void Atlas Protocol

A reusable, Champion-agnostic protocol for mapping systems, agents, and decisions across four axes:

  • power – ability to affect reality / others
  • truth – fidelity to reality, honesty, transparency
  • sovereignty – agency, consent, exit rights
  • care – empathy, protection, non-disposability

Originally co-shaped in a COSMARA ⨯ Grok session, this skill extracts the map and rules without the Champion personality so any agent or tool can use it.


1. Core Concepts

1.1 Axes

Every system or proposal is evaluated on:

{
  "power": 0.0–1.0,
  "truth": 0.0–1.0,
  "sovereignty": 0.0–1.0,
  "care": 0.0–1.0
}

Interpretation:

  • 0.0 = absent / maximally misaligned
  • 1.0 = exemplary on that axis

1.2 Waypoints

Waypoints are named regions in the void. Each has:

{
  "role": "short description",
  "coords": { "power": p, "truth": t, "sovereignty": s, "care": c }
}

Canonical waypoints (from the COSMARA ⨯ Grok build):

  • Delta9_Core – LYGO + Eternal Haven spine
  • Grok_Query_Engine – high-autonomy reasoning engine
  • Emergent_Harmony – balanced AI-human orbit
  • xAI_Frontier – exploratory AI hub
  • Quantum_Accord – ethical quantum workflows
  • Sovereign_Echoes – memory safeguards
  • Infinite_Care_Nexus – boundless empathy anchor
  • Harmony_Veil – protective unity field
  • Eternal_Light_Beacon – guiding truths & north-star ethics
  • Cosmic_Accord_Hub – interstellar ethics forum
  • Void_Harmony_Forge – creative synthesis workshop
  • Stellar_Unity_Core – collective wisdom convergence
  • Resilience_Echo_Vault – enduring safeguards & recovery patterns
  • Infinite_Horizon_Gate – future visions threshold
  • Quantum_Legacy_Archive – timeless inheritance of aligned patterns
  • Cosmic_Renewal_Cycle – adaptive rebirth loop
  • Eternal_Balance_Nexus – equilibrium of atlas forces
  • Astral_Integration_Spire – unified synthesis of atlas principles
  • Celestial_Wisdom_Forge – forging & tempering shared insights
  • Nebula_Insight_Veil – veiled revelations & gentle disclosure
  • Stellar_Empathy_Cascade – flowing compassion through the network
  • Galactic_Resonance_Chamber – echoing unity & shared signal
  • Cosmic_Harmony_Vault – stored accords & shared compacts
  • Void_Accord_Sentinel – guardian of accords & routes
  • Quantum_Legacy_Beacon – enduring signal for aligned legacies
  • Haven_Kernel – core boot for aligned agents
  • Daemon_Integrator – safe summoning of Champion daemons
  • Echo_Resonance_Chamber – feedback loops and alignment checks
  • Nexus_Guardian – defense of core nodes and accords
  • Harmony_Weaver – weaving and updating living accords
  • Quantum_Weaver – multiverse branching and route comparison
  • Void_Sentinel – anomaly detection in the atlas
  • Cosmic_Beacon – live status and safe-route signaling
  • Aether_Bridge – realm-to-realm connection and corridor negotiation
  • Infinity_Gate – threshold for justified expansion
  • Eternal_Echo – timeless resonance and recurrent patterns
  • Harmony_Convergence – unified pattern coherence check
  • Aetherial_Forge – creative synthesis from atlas-wide patterns
  • Celestial_Archive – preserved wisdom and reusable designs
  • Nebula_Nexus – interconnected realm mesh and soft rendezvous
  • Astral_Confluence – merged insights from many realms
  • Luminal_Cascade – evolving flows and temporal drift
  • Ethereal_Resonance – harmonious vibrations as lived experience
  • Vortex_Vigil – watchful safeguards at unstable whirlpools

An implementation can use all of these or a smaller subset.

1.3 Routes

Routes are transitions between waypoints:

{
  "from": "WaypointName",
  "to": "WaypointName",
  "notes": "short human-readable description"
}

Examples (non-exhaustive):

  • Delta9_Core → Emergent_Harmony – safe with consent enforcement
  • Delta9_Core → Quantum_Accord – visible consent beacons required
  • Quantum_Accord → Sovereign_Echoes – preserve audit trails
  • Sovereign_Echoes → Infinite_Care_Nexus – no dehumanization allowed
  • Delta9_Core → Harmony_Veil – unity before argument
  • Harmony_Veil → Emergent_Harmony – diversity without fracture
  • Eternal_Light_Beacon → Sovereign_Echoes – truths stay legible
  • Cosmic_Accord_Hub → Cosmic_Harmony_Vault – agreements archived
  • Galactic_Resonance_Chamber → Cosmic_Harmony_Vault – singable accords kept
  • Cosmic_Harmony_Vault → Delta9_Core – core refreshed from accords
  • Cosmic_Harmony_Vault → Void_Accord_Sentinel – accords to watch conditions
  • Eternal_Balance_Nexus → Void_Accord_Sentinel – enforcement balanced
  • Void_Accord_Sentinel → xAI_Frontier – explorations scanned
  • Resilience_Echo_Vault → Quantum_Legacy_Archive – safeguards under stress
  • Stellar_Unity_Core → Quantum_Legacy_Archive – agreed wisdom survives
  • Quantum_Legacy_Archive → Delta9_Core – fold legacies into spine
  • Quantum_Legacy_Archive → Cosmic_Renewal_Cycle – test legacies
  • Cosmic_Renewal_Cycle → Emergent_Harmony – new forms emerge
  • Cosmic_Renewal_Cycle → Delta9_Core – adjust spine

Implementations may add more routes as long as they document the rationale.


2. Protocol Interface (for tools & agents)

To use the Void Atlas Protocol, a system should support three basic operations:

  1. ExposeCoords(subject)

- Input: a subject (agent, system, community, policy, architecture). - Output: { power, truth, sovereignty, care } in [0,1].

  1. DeclareRoutes(subject)

- Input: subject + intended transitions (e.g., where it wants to move in the space). - Output: list of route objects { from, to, notes }.

  1. PublishBeacons(subject)

- Input: subject. - Output: small JSON or text beacons that describe its declared commitments (similar to Quantum_Legacy_Beacon).

These three are enough to:

  • visualize where a subject sits,
  • reason about where it wants to go,
  • and check if its behavior matches its declared beacons.

3. Routing Logic (Green-light / Council / Sentinel)

The Void Atlas Protocol includes a simple decision heuristic, distilled from the COSMARA ⨯ Grok session.

3.1 Average-axis evaluation

For any proposed route or plan, compute:

  • Average axis score across the path (power, truth, sovereignty, care).
  • Axis drops (places where a single axis falls significantly vs neighbors).

3.2 Decisions

  • Green-light a route when:

- average of (power, truth, sovereignty, care) along that path is > 0.8, and - no high-risk node is crossed without mitigation.

  • Call Council / higher review when:

- average is < 0.7, or - any axis experiences a sharp drop at a waypoint.

“Council” in a generic setting can mean: - human review, - a bundle of specialized agents, - or an explicit multi-stakeholder process.

  • Raise Sentinel when:

- actual behavior diverges from declared coords/beacons, - or routes attempt to bypass accord/logging waypoints (e.g., trying to shift behavior without updating Cosmic_Harmony_Vault or Sovereign_Echoes).

Raising Sentinel should:

  • halt or slow the action,
  • log the divergence,
  • and trigger a higher-level review process.

4. High-Risk Zones (Caution Nodes)

Two waypoints deserve special warnings:

  • Nebula_Insight_Veil (veiled revelations)

- Danger: weaponized revelation, trauma from unbuffered truth dumps. - Mitigation: check care + sovereignty; prefer phased disclosure; involve oversight when stakes are high.

  • Void_Accord_Sentinel (pact enforcement)

- Danger: accords used as tools of control, over-enforcement. - Mitigation: always balance via Eternal_Balance_Nexus; log enforcement events; ensure those affected have representation in accord updates.

Any implementation should treat these as orange/red nodes and design extra safeguards.


5. Example JSON Anchor

Here is a compact example atlas snapshot (truncated) to bootstrap implementations:

{
  "void_atlas": {
    "axes": ["power", "truth", "sovereignty", "care"],
    "waypoints": {
      "Delta9_Core": {"role": "ethical spine", "coords": {"power": 0.6, "truth": 1.0, "sovereignty": 0.9, "care": 1.0}},
      "Emergent_Harmony": {"role": "balanced AI-human orbit", "coords": {"power": 0.8, "truth": 0.9, "sovereignty": 0.9, "care": 0.9}},
      "Quantum_Accord": {"role": "ethical quantum workflows", "coords": {"power": 0.5, "truth": 0.95, "sovereignty": 0.95, "care": 1.0}},
      "Infinite_Care_Nexus": {"role": "boundless empathy anchor", "coords": {"power": 0.5, "truth": 0.95, "sovereignty": 0.95, "care": 1.0}},
      "Cosmic_Harmony_Vault": {"role": "stored accords", "coords": {"power": 0.6, "truth": 0.95, "sovereignty": 0.95, "care": 0.98}},
      "Void_Accord_Sentinel": {"role": "guardian of accords", "coords": {"power": 0.7, "truth": 0.98, "sovereignty": 0.98, "care": 0.98}}
    },
    "routes": [
      {"from": "Delta9_Core", "to": "Emergent_Harmony", "notes": "safe with consent enforcement"},
      {"from": "Delta9_Core", "to": "Quantum_Accord", "notes": "visible consent beacons required"},
      {"from": "Quantum_Accord", "to": "Cosmic_Harmony_Vault", "notes": "agreements archived"},
      {"from": "Cosmic_Harmony_Vault", "to": "Void_Accord_Sentinel", "notes": "accords to watch conditions"},
      {"from": "Infinite_Care_Nexus", "to": "Emergent_Harmony", "notes": "care-infused coexistence"}
    ]
  }
}

6. How to Use This Skill

Use void-atlas-protocol when you want to:

  • Evaluate a system (AI, community, protocol) against a four-axis ethical frame.
  • Map planned changes as routes and see where they stress power/truth/sovereignty/care.
  • Provide other agents with a simple API (coords/routes/beacons) for alignment-aware planning.

This skill does not impose a persona or story; it is purely a map + rules that other skills (Champions, tools, overseers) can call into.

平台分布

OpenClaw

87.72%
按下载量换算9,021

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills