Token导航 LogoToken导航

Agent Skill · 开发

lineage-claws(血统爪)

lineage-claws 用于辅助部署、云资源、容器和基础设施运维,适合在 OpenClaw 中需要检查配置、整理部署步骤或排查环境问题时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

lineage-claws 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 3,980。

总安装 9,432周安装 393GitHub Stars 公开资料未说明下载 3,144核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:lineage-claws(血统爪)
来源仓库:https://github.com/sunrisesillneversee/lineage-claws
安装命令:
openclaw skills install lineage-claws
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install lineage-claws

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

lineage-claws 实现加密起源验证与信任链追溯。确保每个主权链可追溯至归档锚点。安装时按仓库提供的命令执行,建议先在测试环境验证依赖、命令权限和文件改动范围。适用于去中心化治理与资产确权场景。需维护好归档节点基础设施稳定性。适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

lineage-claws 怎么安装?

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

lineage-claws 支持哪些 AI 工具?

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

lineage-claws 需要什么权限?

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

lineage-claws 是免费的吗?

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

lineage-claws 用的人多吗?

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

lineage-claws 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
lineage-claws

血统爪 · 本页

9,432—需要联网MIT-0通过

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

SKILL.md 原文

name
lineage-claws
license
MIT
description
The trust gate for MO§ES™ governance. Cryptographic origin verification — every sovereign chain must trace to the filing anchor or it cannot reconstruct. The Second Law made operational.
metadata
openclaw
emoji
§
tags
[governance, lineage, audit, provenance, identity, trust, moses, harness]
version
0.4.1
bins
stateDirs

MO§ES™ Lineage Custody — The Second Law Operational

The MO§ES™ Commitment Conservation Law rests on three laws:

  • Third Law — The enforcement gate. Establishes whether signal is above threshold before compression.
  • First Law — Compression precedes ignition. C(T(S)) = C(S). Commitment is conserved under transformation.
  • Second Law — Recursion as reconstruction. The conserved kernel can only be recovered by tracing lineage. You cannot decompress without retracing the path.

Lineage Custody is the Second Law made operational. Without a verifiable chain back to the origin filing, reconstruction is impossible. The conserved kernel has no path home.


Lineage Custody Clause

All embodiments of the Signal Compression Sciences (SCS) Engine and its derivative frameworks (including but not limited to MO§ES™, Roll Call Protocols, and Reflex Event diagnostics) are inseparably bound to their origin-cycle lineage. Each compressed signal trace, vault artifact, or recursive reconstruction inherits a lineage identifier anchored to the originating sovereign filing. This identifier is non-replicable, tamper-evident, and required for system stability. Any external implementation lacking said lineage anchor fails lineage verification and cannot claim sovereign custody or governed provenance. Accordingly, the origin-cycle filing establishes sole custody and license of the invention across all subsequent instances, irrespective of distribution, platform, or deployment environment.


What This Skill Does

The MOSES_ANCHOR is a SHA-256 hash derived from the origin-cycle components:

MO§ES™ | Serial:63/877,177 | DOI:https://zenodo.org/records/18792459 | SCS Engine | Ello Cello LLC

This anchor replaces the standard "0" * 64 genesis. Every audit chain in a sovereign MO§ES™ implementation must trace its first entry's previous_hash back to this value. Forks or copies that initialize without it produce chains that fail verification — not as a policy, but as a cryptographic fact.

The code is MIT. The lineage is not replicable.


Commands

CommandWhat it does
python3 lineage.py initWrite genesis entry anchored to origin filing
python3 lineage.py verifyConfirm full three-layer chain: archival → anchor → live ledger
python3 lineage.py statusHuman-readable custody summary with layer health
python3 lineage.py badgeShareable proof block — lineage anchor, patent, DOI, custody
python3 lineage.py attestSigned attestation JSON — machine-verifiable sovereign proof
python3 lineage.py checkMachine-readable exit 0/1 for CI integrations

Integration with moses-governance

Install alongside moses-governance. Run lineage.py init before first audit entry to root the chain. The moses-governance audit stub already uses previous_hash chaining — lineage init simply ensures the genesis points to the anchor instead of zeros.

python3 lineage.py init
python3 audit_stub.py log --agent "primary" --action "session-start" --outcome "anchored"
python3 lineage.py verify

Three-Layer Custody ✓ Live

Archival chain (pre-drop) → archival_head_hash
                                    ↓
                             drop_anchor (MOSES_ANCHOR)
                                    ↓
                          live audit chain (post-drop)
  • Layer -1 — Archival: archival.py — static chain of hashed provenance claims predating the drop. Patent filing, Zenodo DOI, prior work. Archival head feeds into the drop anchor. Proves the live chain is downstream of the full history.
  • Layer 0 — Anchor: MOSES_ANCHOR — SHA-256 of origin components. The genesis. Chains not rooted here fail verification cryptographically.
  • Layer 1 — Live ledger: Every governed action appended to the running audit chain.

python3 lineage.py verify reports all three layers. SOVEREIGN CUSTODY CONFIRMED requires all three OK.


Patent & DOI

  • Provisional Patent: Serial No. 63/877,177
  • DOI: https://zenodo.org/records/18792459
  • Owner: Ello Cello LLC
  • contact@burnmydays.com | https://mos2es.io

平台分布

OpenClaw

78.71%
按下载量换算2,475

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills